SAP ECC and Centra
Integration Agency & Consultants
Expansion into new global markets or wholesale channels eventually makes manual reconciliation between Centra and SAP ECC impossible. When retail volume scales, the flexibility of Centra product variants often clashes with SAP's rigid material masters, leading to unreliable inventory figures and financial drift.
A controlled data flow ensures SAP ECC remains the master for wholesale inventory and material records, while Centra owns front-end product enrichment and global order capture. This removes the manual workload from finance and operations by ensuring the catalogue remains consistent across every retail and wholesale channel.
Auditing legacy ERP and retail workflows
Cogent2 connects your SAP ECC and Centra systems efficiently, ensuring your ERP and Ecommerce platforms work in harmony. Our consulting services, particularly our system audit, are invaluable for identifying inefficiencies and integration gaps. This enables both our consultants and your team to take decisive action, ensuring your tech ecosystems, including SAP ECC and Centra, operate smoothly. By optimising your ERP and Ecommerce systems, we help you deliver an exceptional customer experience, maintaining operational efficiency and effectiveness.
Solution Design
Our design for SAP ECC and Centra prioritises financial integrity while maintaining Centra's speed for global retail. We typically define SAP ECC as the master of truth for core material data and wholesale records, while Centra manages front-end product enrichment and retail order capture. A primary design decision involves managing the trade-off between real-time inventory updates and SAP system stability. Higher frequency updates protect against overselling but increase the load on legacy ERP environments. We often prioritises order and inventory flows first, ensuring the core data mapping is stable before expanding to more complex scenarios. This ensures finance can rely on SAP for month-end reporting, while ecommerce teams use Centra for agile site merchandising and seasonal price management.
Sequencing data flows and variant mapping
In this architecture, SAP ECC remains the authoritative source for financial records and the material master, while Centra manages global retail price lists and storefront enrichment. Data flows are sequenced to protect the ERP, mapping retail orders into SAP for fulfilment and financial processing.
The integration maps Centra product variants and multi-currency pricing to SAP pricing structures, ensuring data is formatted for legacy material masters. Monitoring is embedded to detect discrepancies in order totals or inventory levels early. This prevents the inventory drift and reconciliation gaps common when global retail channels are not aligned with legacy ERP processing.
Orchestrating secure message delivery and scale
Cogent2 leverages iPaaS to integrate SAP ECC and Centra with ERP and eCommerce systems securely. iPaaS platforms, with ISO 27001 and SOC 2 compliance and above, ensure data security. Benefits include efficient SAP ECC and Centra integration, improved ERP and eCommerce operations, and enhanced data management. This approach supports secure, scalable, and reliable business processes, maintaining high security standards.
Surfacing reconciliation gaps and sync errors
Standard SAP logs often fail to surface the retail context needed to resolve synchronisation gaps. We provide visibility by flagging specific failure points, such as variant mapping errors or orders rejected due to missing data in the ERP. Visibility focuses on catching hidden issues, including currency rounding drift or tax mismatches, before they impact month-end reconciliation. By surfacing these exceptions early, teams can address data gaps at the source rather than searching through system logs for a missing order. This transparency keeps finance, operations, and ecommerce teams aligned on the same data.
Establishing cross-functional data ownership protocols
Adoption of the SAP ECC and Centra model requires clear ownership across finance, ecommerce, and warehouse operations. We hand over a documented operating model where finance manages core material data in SAP, while ecommerce teams own product enrichment and retail pricing in Centra. Training focuses on essential daily tasks, such as reconciling retail order volumes and monitoring for synchronisation errors. Teams learn to identify which system owns specific data exceptions and how to respond to alerts. All documentation is provided as an operational reference for the people running the business, ensuring teams can manage global inventory accuracy and order flow day to day.
Maintaining order integrity and financial logic
Post-launch support focuses on the operational stability of the data flow between SAP ECC and Centra. We monitor for specific exceptions, including inventory update failures or order processing delays, ensuring that retail expansion does not conflict with financial logic. Our role involves managing the integrity of material data, pricing, and orders as they move between systems. By identifying and resolving mapping errors early, we prevent operational drag and ensure that warehouse and finance teams can trust the data in SAP as the brand grows across different markets.
Common failures
Mismatched product and variant data
Operational impact: Centra's flexible product model clashes with SAP ECC’s rigid Material Master structure. Direct mapping causes new SKUs to be rejected by SAP or existing records to be updated with incorrect data, leading to a high rate of Sales Order IDoc processing failures. This requires daily manual intervention from merchandising and operations teams to align product records before any orders can be processed.
Prevention / Action: Implement a transformation layer to map Centra's product and variant attributes to the correct MATMAS IDoc structure for SAP's Material Master. SAP must be the exclusive source of truth for core material data like SKU. The integration logic must include robust exception handling to quarantine any failed product syncs and notify operators, preventing bad data from disrupting the order-to-cash process.
Inventory latency and overselling
Operational impact: Relying on batch-based IDoc processing from SAP ECC creates significant delays between a stock movement and the corresponding update in Centra. This latency leads directly to overselling, particularly during sales periods. The operational burden falls on customer service teams to manage cancelled orders and on fulfilment teams who cannot complete pick lists for sold-out SKUs.
Prevention / Action: Design the integration to use event-driven triggers for inventory updates where possible, rather than relying solely on scheduled batch files. For example, Goods Issue or Goods Receipt IDoc statuses in SAP can trigger immediate API calls to Centra. Align Centra's stock buffers with SAP's Available-to-Promise (ATP) calculation rules to create a reliable safety net that respects both systems' logic.
Complex pricing and currency reconciliation
Operational impact: Centra’s ability to manage multiple global markets, currencies, and price lists creates significant complexity when posting financial data to SAP. If Sales Order IDocs (ORDERS05) contain currency codes or pricing that does not map perfectly to SAP’s strict pricing conditions, they fail. This forces the finance team into manual, order-by-order reconciliation, delaying the order-to-cash cycle and disrupting the month-end close.
Prevention / Action: A strict mapping strategy must be defined for all pricing and currency fields before implementation. The integration must translate Centra's Market and Price List structure into an SAP-valid format before the IDoc is created. All transactions should be passed with clear currency codes, and any conversions handled systematically by the integration layer to ensure an auditable trail for the finance team.
Out-of-sequence fulfilment and dispatch updates
Operational impact: It is common for SAP ECC to generate DESADV (Despatch Advice) IDocs for an outbound delivery before the goods have physically left the warehouse. If this triggers a premature shipping notification in Centra, customers are misinformed and the CX team's workload increases. It also complicates the handling of partial shipments, as the Centra order status may not reflect the true state of a multi-part fulfilment.
Prevention / Action: The integration should be designed to process logistics IDocs in a specific sequence, holding a shipment confirmation until a corresponding Post Goods Issue (PGI) is confirmed in SAP. Sequence handling should be managed in an integration queue to ensure the final dispatch notification in Centra only contains confirmed tracking information. For partial shipments, the logic must be capable of updating individual line-item statuses on the Centra order.
Frequently asked questions
If we use both systems, which one is the master for inventory and product information?
SAP ECC remains the authoritative source for the material master and available-to-sell wholesale inventory. Centra pulls this data and acts as the master for enriched retail attributes, marketing descriptions, and global price execution. This separation prevents inventory sync conflicts between retail storefronts and wholesale processing.
Our SAP ECC instance is heavily customised. How do you ensure an integration will not break existing processes?
We prioritise stability by interacting with SAP ECC via established interfaces such as IDocs instead of direct database modifications. The integration logic is designed to handle Centra's API-driven workflows and transform them into the structured format SAP expects for sales orders. This buffers your core ERP, ensuring high-volume retail data from Centra is processed without disrupting legacy financial or logistics processes.
We have had issues with SKU formats between systems. How is this handled?
This is a common failure point that requires an explicit transformation rule. SAP ECC often uses material numbers with leading zeros (e.g. '000012345'), while Centra may treat '12345' as a distinct record. The integration commonly includes logic to pad or trim these IDs during the product sync to prevent inventory mismatches or orphaned orders.
We are expanding into new markets with Centra. How does the integration support global financial reconciliation?
The integration maps each Centra 'Market' to the corresponding company code and sales organisation in SAP ECC. When an order is created in Centra, the integration passes multi-currency data into the SAP record. This ensures that revenue and taxes are posted correctly for each legal entity, reducing the manual reconciliation debt for the finance team.
How do you prevent Centra's multi-currency price lists from causing errors in SAP?
The integration transforms Centra’s pricing data into the specific pricing conditions SAP requires. This ensures that retail prices are validated against SAP’s internal structures before the sales order is created, avoiding the order-to-cash failures that often occur when multi-currency logic differs between systems.