972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

ERP integration · SAP

SAP S/4HANA EDI and B2B integration

IDoc, API and EDI integration for SAP S/4HANA, plus S/4HANA implementation services.

  • Integration supported
  • Implementation services available
  • Cloud, on-premises or hybrid
Discuss your SAP S/4HANA integration ERP implementation services

Overview

Connecting SAP S/4HANA with your trading partners

SAP S/4HANA is SAP's current-generation ERP, available on premises, in private cloud and as public cloud editions. For B2B integration, S/4HANA continues to support IDocs, the long-standing SAP document format used for EDI, and adds a growing catalog of released APIs. The right approach depends on your edition, your existing IDoc landscape and SAP's clean core guidance for extensions.

In a typical EDI scenario, PRISM translates a customer's X12 or EDIFACT purchase order into an ORDERS IDoc that creates a sales order in S/4HANA. Deliveries and billing documents produce outbound IDocs that PRISM converts into ship notices and invoices for each partner. ECOM also implements S/4HANA, so partner integrations can be designed alongside the ERP rather than retrofitted after go-live.

Read the in-depth guideSAP EDI integration guide: IDocs, partner profiles and best practices

Methods

Integration approaches for SAP S/4HANA

IDocs and ALE

Standard message types such as ORDERS, ORDRSP, DESADV and INVOIC exchanged through partner profiles, ports and ALE configuration.

Released APIs

OData and SOAP APIs for sales orders, deliveries, billing and business partners, especially relevant for cloud editions.

SAP Integration Suite

SAP's integration platform can sit alongside PRISM when your SAP strategy calls for it.

BAPIs and RFC

Function-based interfaces used for specific on-premises scenarios and legacy integrations.

Document mapping

How EDI documents map to SAP S/4HANA

Typical mappings between common X12 documents and SAP S/4HANA business objects. Actual designs depend on your configuration and partners.

EDI documentSAP S/4HANA objectDirection
850 Purchase OrderSales order (ORDERS IDoc or API)Into SAP S/4HANA
855 Order AcknowledgmentOrder response (ORDRSP IDoc)From SAP S/4HANA
856 Advance Ship NoticeOutbound delivery (DESADV IDoc)From SAP S/4HANA
810 InvoiceBilling document (INVOIC IDoc)From SAP S/4HANA
820 Remittance AdviceIncoming payment advice (REMADV IDoc)Into SAP S/4HANA

Planning

Implementation considerations

  • Edition matters

    Public cloud editions favor released APIs, while private cloud and on-premises editions commonly continue with IDocs.

  • Migrating from ECC

    Existing ECC IDoc interfaces can often be carried forward, but partner profiles, output determination and custom code need review.

  • Master data alignment

    Customer material numbers, partner functions and units of measure must map cleanly between partners and S/4HANA.

  • Clean core

    Keeping custom logic in the integration layer rather than the ERP simplifies future S/4HANA upgrades.

Trading partners

Integration guides that pair with SAP S/4HANA

  • Amazon EDI integration
  • AT&T EDI integration
  • Bank of America EDI integration
  • C.H. Robinson EDI integration
  • Cardinal Health EDI integration
  • Caterpillar EDI integration
  • Cencora EDI integration
  • Citi EDI integration
  • Costco EDI integration
  • Dollar General EDI integration
  • FedEx EDI integration
  • Ford EDI integration
  • General Motors EDI integration
  • Honda EDI integration
  • Hub Group EDI integration
  • Intel EDI integration
  • J.B. Hunt EDI integration
  • John Deere EDI integration
  • JPMorgan Chase EDI integration
  • Kroger EDI integration
  • Lowe's EDI integration
  • McKesson EDI integration
  • Old Dominion Freight Line EDI integration
  • Ryder EDI integration
  • Schneider EDI integration
  • Starbucks EDI integration
  • Target EDI integration
  • The Home Depot EDI integration
  • Toyota EDI integration
  • UPS EDI integration
  • Verizon EDI integration
  • Walgreens EDI integration
  • Walmart EDI integration
  • Wells Fargo EDI integration
  • XPO EDI integration

SAP S/4HANA integration FAQs

Does SAP S/4HANA still use IDocs for EDI?

Yes, IDocs remain widely used with S/4HANA, particularly in on-premises and private cloud editions. Public cloud editions typically rely more on released APIs.

Can ECOM implement SAP S/4HANA?

Yes. ECOM provides SAP S/4HANA implementation services and designs trading partner integrations as part of the same program.

Can we reuse our ECC EDI interfaces in S/4HANA?

Often, partially. ECOM assesses existing IDoc interfaces, maps and partner profiles and plans what can be reused and what should be redesigned.

Keep exploring

Related

Solution

ERP Integration

Connect your ERP to trading partners through EDI, APIs, IDocs, files and connectors.

Service

ERP Implementation

ERP implementation for SAP, Oracle, Microsoft, NetSuite, Infor, Epicor, QAD and Sage, with B2B integration built in.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

ERP

SAP Business One

EDI and API integration for SAP Business One through the Service Layer and DI API, plus implementation services.

ERP

SAP ECC

IDoc-based EDI integration for SAP ECC and support for migrating partner interfaces to S/4HANA.

Integrating or implementing SAP S/4HANA?

Tell us about your ERP environment and trading partners. We will recommend an integration approach and delivery model.

Request a Demo Contact us