ERP integration · SAP
SAP ECC EDI and B2B integration
IDoc-based EDI integration for SAP ECC and support for migrating partner interfaces to S/4HANA.
- Integration supported
- Implementation services available
- Cloud, on-premises or hybrid
Overview
Connecting SAP ECC with your trading partners
SAP ECC remains the backbone of many enterprises' order-to-cash and procure-to-pay processes, and its IDoc framework has supported EDI for decades. Most ECC EDI landscapes use standard message types such as ORDERS, DESADV and INVOIC, configured through partner profiles and output determination, with an EDI translator converting between IDocs and X12 or EDIFACT.
With SAP's announced end of mainstream maintenance for ECC, many organizations are planning a move to S/4HANA. ECOM supports ECC integrations today, including IBM Sterling and PRISM translators, and helps plan how partner interfaces will move to S/4HANA so trading partners are not disrupted during the transition.
Methods
Integration approaches for SAP ECC
IDocs and ALE
Standard and extended IDoc types exchanged through partner profiles, ports and ALE distribution models.
BAPIs and RFC
Function modules used for synchronous lookups and specific integration scenarios.
File-based interfaces
Flat-file interfaces used in some older or custom ECC integrations.
Document mapping
How EDI documents map to SAP ECC
Typical mappings between common X12 documents and SAP ECC business objects. Actual designs depend on your configuration and partners.
| EDI document | SAP ECC object | Direction |
|---|---|---|
| 850 Purchase Order | Sales order (ORDERS05 IDoc) | Into SAP ECC |
| 855 Order Acknowledgment | Order response (ORDRSP IDoc) | From SAP ECC |
| 856 Advance Ship Notice | Delivery (DELVRY or DESADV IDoc) | From SAP ECC |
| 810 Invoice | Billing document (INVOIC02 IDoc) | From SAP ECC |
Planning
Implementation considerations
Custom IDoc extensions
Many ECC systems use extended IDocs or custom segments that must be documented before migration.
Output determination
Outbound IDoc triggering relies on output conditions that need to be reviewed when processes change.
Migration planning
Partner interfaces should be inventoried and tested in parallel when moving to S/4HANA.
Trading partners
Integration guides that pair with SAP ECC
SAP ECC integration FAQs
Can ECOM support our existing SAP ECC EDI?
Yes. ECOM supports ECC IDoc integrations on PRISM and on IBM Sterling B2B Integrator, including map maintenance and partner onboarding.
What happens to our EDI when we move to S/4HANA?
Many IDoc interfaces carry forward with adjustments. ECOM inventories interfaces and plans what to reuse, adjust or redesign.
How long will SAP support ECC?
SAP has announced timelines for ECC mainstream and extended maintenance. Confirm the dates that apply to your release and contract with SAP.
Keep exploring
Related
Solution
ERP Integration
Connect your ERP to trading partners through EDI, APIs, IDocs, files and connectors.
Service
Migration and Modernization
Assessment, map conversion, partner cutover and decommissioning for platform migrations.
Service
ERP Implementation
ERP implementation for SAP, Oracle, Microsoft, NetSuite, Infor, Epicor, QAD and Sage, with B2B integration built in.
ERP
SAP Business One
EDI and API integration for SAP Business One through the Service Layer and DI API, plus implementation services.
ERP
SAP S/4HANA
IDoc, API and EDI integration for SAP S/4HANA, plus S/4HANA implementation services.
Integrating or implementing SAP ECC?
Tell us about your ERP environment and trading partners. We will recommend an integration approach and delivery model.