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

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.

Integration design

SAP S/4HANA: scope, flows, controls and tests

The scope below describes integration functions and controls that can be included in an ECOM project. Coverage is confirmed for your product version, licensed modules and business requirements. We explain ECOM’s specific connection path and deployment architecture during a live meeting.

Editions and versions we integrate

ECOM scopes SAP S/4HANA integration for the edition and release you run. Coverage, permitted actions and record availability are confirmed for your version, licensed modules and business requirements.

  • SAP S/4HANA Cloud, Private Edition
  • SAP S/4HANA AnyPremise
  • SAP S/4HANA Finance (formerly Simple Finance)
SAP S/4HANA editions and versions3 editions ECOM scopes integration for: SAP S/4HANA Cloud, Private Edition, SAP S/4HANA AnyPremise, SAP S/4HANA Finance (formerly Simple Finance).SAP S/4HANA editions and versionsScoped for the release you runSAP S/4HANA Cloud, PrivateEditionSAP S/4HANA AnyPremiseSAP S/4HANA Financeformerly Simple Finance© 2026 ECOM Specialist LLC. All rights reserved. Illustrative workflow; scope is agreed for each engagement.
SAP S/4HANA editions and versions3 editions ECOM scopes integration for: SAP S/4HANA Cloud, Private Edition, SAP S/4HANA AnyPremise, SAP S/4HANA Finance (formerly Simple Finance).SAP S/4HANA editions andversionsScoped for the release you runSAP S/4HANA Cloud, Private EditionSAP S/4HANA AnyPremiseSAP S/4HANA Financeformerly Simple Finance© 2026 ECOM Specialist LLC. All rights reserved.Illustrative workflow; scope is agreed for eachengagement.

Each edition is scoped on its own release, licensed modules and business requirements; coverage is confirmed for your environment.

Expand diagram Download SVG

The ERP environment we integrate around

SAP S/4HANA is an ERP application built on the SAP HANA database. This page covers S/4HANA business processes; SAP HANA itself is a database, not an ERP product.

The design identifies sales organization, distribution channel, division, company code, plant and storage location. These values determine transaction routing, record validity, ownership and the financial or operational context in which a document is processed.

Systems and ownership

System or participantIntegration responsibility
SAP S/4HANAMaintain the approved ERP records, business rules, stock and financial results within the agreed module scope.
Customer or supplier systemsSupply orders, revisions, forecasts, invoice details and partner reference numbers; receive agreed business responses.
Warehouse or fulfillment applicationOwn physical pick, pack, dispatch and receipt facts where separately deployed. Return actual quantities and shipment references.
ECOM integration servicesCoordinate agreed document exchanges, business data mapping, validation and processing visibility across the defined systems.
Who owns what in a SAP S/4HANA integrationFour boxes showing the responsibilities of SAP S/4HANA, customer or supplier systems, a warehouse or fulfillment application, and ECOM integration services.Who owns what in a SAP S/4HANA integrationSystems and responsibilitiesSAP S/4HANAERPMaintain the approved ERP records, business rules, stock andfinancial results within the agreed module scope.Customer or supplier systemsPartnersSupply orders, revisions, forecasts, invoice details and partnerreference numbers; receive agreed business responses.Warehouse or fulfillment applicationFulfillmentOwn physical pick, pack, dispatch and receipt facts whereseparately deployed. Return actual quantities and shipmentreferences.ECOM integration servicesECOMCoordinate agreed document exchanges, business data mapping,validation and processing visibility across the defined systems.© 2026 ECOM Specialist LLC. All rights reserved. Illustrative workflow; scope is agreed for each engagement.
Who owns what in a SAP S/4HANA integrationFour boxes showing the responsibilities of SAP S/4HANA, customer or supplier systems, a warehouse or fulfillment application, and ECOM integration services.Who owns what in a SAPS/4HANA integrationSystems and responsibilitiesSAP S/4HANAERPMaintain the approved ERP records, businessrules, stock and financial results within theagreed module scope.Customer or supplier systemsPartnersSupply orders, revisions, forecasts, invoicedetails and partner reference numbers; receiveagreed business responses.Warehouse or fulfillment applicationFulfillmentOwn physical pick, pack, dispatch and receiptfacts where separately deployed. Returnactual quantities and shipment references.ECOM integration servicesECOMCoordinate agreed document exchanges,business data mapping, validation andprocessing visibility across the definedsystems.© 2026 ECOM Specialist LLC. All rights reserved.Illustrative workflow; scope is agreed for eachengagement.

SAP S/4HANA keeps the approved records, business rules and results; partners supply and receive agreed business documents; a separate warehouse application owns physical facts where one is deployed; and ECOM coordinates document exchange, mapping, validation and visibility. A system of record is decided for each data group.

Expand diagram Download SVG

A system-of-record decision is made for each data group. For example, partner purchase order numbers can originate externally while ERP order numbers are assigned by the ERP. External instructions do not automatically authorize changes to item masters, tax settings, accounting periods or payment details.

Input channels can include EDI, PRISM-WebEDI, PRISM-SmartConvert documents and PRISM-WebConnect portal activity, each subject to the same agreed ERP validation and business controls.

ERP records in the proposed scope

  • Business partner and material
  • Sales order and item
  • Schedule line and confirmation
  • Outbound delivery and item
  • Goods issue status
  • Billing document and item
  • Purchase order and item
  • Supplier invoice

Record availability and permitted actions are checked against the installed environment; the list is a functional scope inventory rather than a claim that every record is enabled in every edition.

Transaction flows and processing rules

Direction is relative to SAP S/4HANA. Each flow is defined by its source, target business record, release condition and successful result. Creation, update, cancellation and enquiry are scoped separately.

SAP S/4HANA transaction flows7 business flows for SAP S/4HANA, each labelled as into the ERP, out of the ERP or both: Customer order, Order change or cancellation, Order response, Shipment and ASN, Invoice or credit, Supplier purchasing, Availability and status.SAP S/4HANA transaction flowsDirection is relative to the ERPCustomer orderInto ERPOrder change orcancellationInto ERPOrder responseOut of ERPShipment and ASNOut of ERP or coordinatedInvoice or creditOut of ERPSupplier purchasingBoth as scopedAvailability and statusOut of ERP where scoped© 2026 ECOM Specialist LLC. All rights reserved. Illustrative workflow; scope is agreed for each engagement.
SAP S/4HANA transaction flows7 business flows for SAP S/4HANA, each labelled as into the ERP, out of the ERP or both: Customer order, Order change or cancellation, Order response, Shipment and ASN, Invoice or credit, Supplier purchasing, Availability and status.SAP S/4HANA transaction flowsDirection is relative to the ERPCustomer orderInto ERPOrder change or cancellationInto ERPOrder responseOut of ERPShipment and ASNOut of ERP or coordinatedInvoice or creditOut of ERPSupplier purchasingBoth as scopedAvailability and statusOut of ERP where scoped© 2026 ECOM Specialist LLC. All rights reserved.Illustrative workflow; scope is agreed for eachengagement.

Each flow has a source, a target business record, a release condition and a successful result. Creation, update, cancellation and enquiry are scoped separately for SAP S/4HANA.

Expand diagram Download SVG

Business flowDirectionProcessing and completion rule
Customer orderInto ERPCreate the appropriate sales order with source PO, line references, customer, ship-to, item, quantity, unit and requested date.
Order change or cancellationInto ERPMatch the existing order and revision. Apply only permitted changes to open quantities; hold conflicts with shipped or invoiced activity.
Order responseOut of ERPReturn accepted or rejected lines, confirmed quantity and date, and ERP order reference. Transport receipt alone is not order acceptance.
Shipment and ASNOut of ERP or coordinatedUse actual released shipment facts, order-line references, quantities and packaging details. A planned pick does not establish shipment.
Invoice or creditOut of ERPUse the agreed released or posted billing record. Retain original order and shipment references, charges, allowances and tax treatment.
Supplier purchasingBoth as scopedPublish approved purchase orders and accept supplier confirmations, receipt information and invoices under the purchasing rules.
Availability and statusOut of ERP where scopedShare the agreed stock or available-to-promise measure and timestamp; distinguish on-hand stock from committed or unavailable stock.

Partner documents and business meaning

X12 examples include 850 orders, 860 order changes, 855 order acknowledgments, 856 shipment notices, 810 invoices and 820 payment or remittance advice. Relevant EDIFACT messages can be scoped for international partners. A 997 or 999 technical acknowledgment is tracked separately from business acceptance. Document selection follows the partner’s implementation guide, not the ERP product name.

Example: a SAP S/4HANA order-to-cash exchangeSequence between a trading partner, ECOM and SAP S/4HANA: the order is validated and created, an order response is returned, actual shipment facts produce the ship notice, and the billing document becomes the invoice.Example: a SAP S/4HANA order-to-cash exchangeFrom customer order to reconciled invoiceTrading partnerECOMSAP S/4HANAOrder or changeValidated orderOrder reference and holdsOrder responseActual shipment factsShip notice (ASN)Billing recordInvoice© 2026 ECOM Specialist LLC. All rights reserved. Illustrative workflow; scope is agreed for each engagement.
Example: a SAP S/4HANA order-to-cash exchangeSequence between a trading partner, ECOM and SAP S/4HANA: the order is validated and created, an order response is returned, actual shipment facts produce the ship notice, and the billing document becomes the invoice.Example: a SAP S/4HANAorder-to-cash exchangeFrom customer order to reconciled invoiceTradingpartnerECOMSAPS/4HANAOrder or changeValidated orderOrder reference and holdsOrder responseActual shipment factsShip notice (ASN)Billing recordInvoice© 2026 ECOM Specialist LLC. All rights reserved.Illustrative workflow; scope is agreed for eachengagement.

A US manufacturer receives orders from several retailers. ECOM can help align each retailer’s item references and shipping requirements with the manufacturer’s SAP sales and delivery processes.

Expand diagram Download SVG

Data mapping and validation

We define a mapping specification at header, line and related-document level. It records source meaning, target business field, transformation, required condition, default ownership and rejection behavior. Partner identifiers remain traceable after ERP identifiers are assigned.

Data groupERP fields or business attributesValidation rule
OrganizationSales Organization, Distribution Channel, Division, PlantValidate sales organization, distribution channel, division, company code, plant and storage location. Reject unknown or unauthorized combinations.
Trading partySold-to Party, Ship-to Party, PayerResolve partner identifiers to approved ERP accounts and locations. Do not match solely on a free-text name.
Product identityMaterial, Customer Material, Batch where usedMap buyer and supplier item aliases to the correct ERP product. Check variants, revisions and active status where relevant.
Quantity and unitOrder Quantity, Sales Unit, Schedule Line QuantityKeep each quantity distinct. Apply approved pack or unit conversion, precision and rounding rules; reject an unknown conversion.
DatesRequested Delivery Date, Confirmed Delivery DatePreserve meaning, time zone and date-only values. Reject invalid formats and identify stale revisions.
Price and moneyNet Price, Transaction Currency, Tax ClassificationDefine the authoritative price and tax calculation. Reconcile line extensions and document totals within approved tolerances.
ReferencesCustomer Reference, Sales Order Item, Delivery ItemUse stable line references across splits and updates. Retain original order, shipment, invoice and correction links.
ExtensionsCustomer-required delivery or billing attributesAgree field ownership, allowed values and length. Do not silently truncate values or discard unmapped required data.

Field labels above identify business attributes; exact technical names, availability and allowed write actions are verified for your release. They do not disclose ECOM’s connection method.

Identity and duplicate control

The business identity starts with customer purchase order + sales area + line + schedule reference. The final rule also distinguishes a new document, a retransmission and a legitimate revision. ERP-assigned IDs are recorded after successful creation. A retry reuses the same business identity instead of creating a second order or invoice.

Processing control and error recovery

Business state controls the next action

For SAP S/4HANA, the design evaluates sales order acceptance, schedule confirmation, delivery readiness, goods issue and billing release. A document is not considered complete simply because it arrived or passed a format check. Completion requires the intended ERP business result and its returned reference.

Processing stageRequired evidence and next action
ReceivedAssign a correlation reference, retain the source identity and record receipt time. Check whether this is a duplicate or new revision.
ValidatedConfirm required fields, authorized organization, master data, quantities and business rules. Reject or hold a failed document before unintended posting.
SubmittedRecord the intended target action and processing attempt. Submission is an intermediate state, not evidence of ERP acceptance.
Accepted or heldCapture the ERP business record ID or a specific rejection or hold reason. Distinguish a business hold from an unavailable system.
Completed and reconciledConfirm the agreed milestone, expected line results and outbound response. Reconcile source identity to ERP and partner references.
How a document is processed for SAP S/4HANAFive processing stages: received, validated, submitted, accepted or held, and completed and reconciled, with held or rejected documents corrected and replayed under the original identity.How a document is processed for SAP S/4HANABusiness state controls the next action1ReceivedCorrelationreference, receipttime, duplicatecheck2ValidatedFields, organization,master data andquantities3SubmittedIntended action andattempt recorded4Accepted orheldERP record ID or aspecific hold reason5Completed andreconciledMilestoneconfirmed;referencesreconciledCorrect and replay with the same identity© 2026 ECOM Specialist LLC. All rights reserved. Illustrative workflow; scope is agreed for each engagement.
How a document is processed for SAP S/4HANAFive processing stages: received, validated, submitted, accepted or held, and completed and reconciled, with held or rejected documents corrected and replayed under the original identity.How a document is processedfor SAP S/4HANABusiness state controls the next action1ReceivedCorrelation reference, receipt time,duplicate check2ValidatedFields, organization, master data andquantities3SubmittedIntended action and attempt recorded4Accepted or heldERP record ID or a specific hold reason5Completed and reconciledMilestone confirmed; referencesreconciledCorrect and replay with the same identity© 2026 ECOM Specialist LLC. All rights reserved.Illustrative workflow; scope is agreed for eachengagement.

For SAP S/4HANA, the design evaluates sales order acceptance, schedule confirmation, delivery readiness, goods issue and billing release. A document is not considered complete simply because it arrived or passed a format check. Completion requires the intended ERP business result and its returned reference. Held or rejected documents are corrected and replayed with the same business identity, so a retry never creates a second order or invoice.

Expand diagram Download SVG

Changes and sequencing

Process a dependent change against the correct original record and current revision. If a change arrives before the order exists, retain it for controlled review or dependency handling. Define a cut-off state after which quantity, price or ship-to changes require an exception or formal correction. Posted financial history is corrected through the authorized business process.

Safe retry and uncertain results

Temporary availability failures can be retried under an agreed retry limit and escalation policy. Invalid items, closed periods and missing approvals need correction rather than blind retries. When a submission times out, first determine whether the ERP already created the record. An unknown result must not be converted immediately into a new create request.

For multi-step flows, retain completed steps and resume only the incomplete authorized action. An order created successfully must not be recreated because its acknowledgment failed. Recovery should retain original references, corrected values, attempt history and the responsible user or process.

Reconciliation and operational ownership

Reconcile document counts, line counts, quantities, monetary totals and business references at the agreed interval. Identify documents received without ERP results, shipments without required notices, invoices without partner delivery results and aging exceptions. Assign an owner and response target for each exception category. Set the interval and service targets from business deadlines and measured ERP capacity.

SAP S/4HANA-specific integration requirements

  1. Design requirement 1: Separate the customer requested date from confirmed schedule dates. One order item may have several date and quantity commitments; a changed schedule must not silently replace shipped quantities.

  2. Design requirement 2: Retain sold-to, ship-to, bill-to and payer roles. A ship-to address match alone must not choose the customer account or sales area.

  3. Design requirement 3: Check delivery and billing blocks independently. A valid order can still be held for fulfillment or billing, and those states need distinct business responses.

Example integration sequence

A US manufacturer receives orders from several retailers. ECOM can help align each retailer’s item references and shipping requirements with the manufacturer’s SAP sales and delivery processes.

  1. Receive the partner order or demand instruction and identify customer, item, organization and delivery requirements.
  2. Validate and create or update the agreed ERP record; retain the assigned order and line references.
  3. Produce a business response from accepted quantities, dates and any holds rather than from message receipt alone.
  4. Use actual fulfillment information to build the required shipment notice and preserve split-delivery references.
  5. Publish the agreed billing document and reconcile order, delivered quantity, invoiced quantity and open balance.

Security, testing and production rollout

Security and access requirements

Define access by business action and organizational scope. Separate permissions for reading masters, creating documents, changing open records, releasing transactions and viewing financial data. Use dedicated integration identities and approved credential management; avoid shared administrator access. Keep customer environments and partner configuration boundaries explicit.

Agree protection of data in transit and at rest, secret rotation, audit retention and masking of sensitive logs. Restrict test datasets and exception screens to authorized users. Changes to payment details or sensitive master data require separate business authorization; ordinary transaction processing must not silently update them.

Acceptance tests

Test conditionExpected evidence
Valid transactionOne intended ERP result with correct organization, party, lines, quantities, amounts and external references.
Replay and duplicateA replay does not create a second business record or duplicate a stock or financial movement.
Invalid master dataAn unknown item, location or account produces a clear exception and no unintended posting.
Partial transactionThe completed quantity and remaining quantity reconcile across the original and related records.
Revision conflictA stale or late revision does not overwrite newer or completed business activity.
Uncertain submissionA timeout after submission is resolved by checking the business outcome before another create action.
Volume and cut-offRepresentative peak volume meets agreed deadlines with measured backlog, processing duration and recovery behavior.
AuthorizationAn identity cannot access another company or perform an unapproved release, master-data change or finance action.

Controlled rollout

Approve the transaction list, mapping rules and success criteria first. Test representative partner documents in the agreed nonproduction environment, then complete partner certification where required. Reconcile opening references and queued documents before production cutover. Start with a defined partner or transaction set and monitor actual results before expanding coverage.

The rollout plan identifies who can pause processing, how queued work is retained, how already posted documents are corrected, and when operations resume. ERP upgrades, cloud releases, new partner requirements and mapping changes require impact review and regression tests for affected flows.

Initial synchronization and cutover data

Define the initial data population separately from ongoing transaction processing. Identify which active customers, suppliers, products, locations and reference values are required before the first live document. Include only the open orders, balances or historical references that the agreed business scope needs. Record source ownership, extraction time and the reconciliation totals for the opening population.

During cutover, distinguish transactions already processed in the previous environment from transactions waiting to be processed. Preserve original partner references and ERP identifiers for open documents. Establish how changes made during the cutover window are captured and reconciled. A historical document used for reference must not accidentally be replayed as a new stock or accounting transaction.

Processing frequency and capacity

Assign a frequency to each flow rather than one timing promise for the entire integration. Urgent order changes, periodic inventory availability, shipment notices and financial reconciliation have different deadlines. Agree the peak document rate, typical and largest line counts, permitted backlog, ERP maintenance windows and the oldest acceptable unprocessed transaction.

Measure acceptance time, business completion time and partner response time separately. Test the effect of an ERP outage and the rate at which accumulated work can safely resume. Publish operating targets only after representative testing; a successful small sample does not establish peak-volume capacity or a guaranteed near-real-time service level.

Trading partners

Integration guides that pair with SAP S/4HANA

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.

How quickly are transactions processed?

Timing is defined by business need, ERP capacity and partner deadlines. The design distinguishes event-driven business triggers, scheduled processing windows and bulk reconciliation requirements without promising an unmeasured latency.

What happens when the ERP rejects a transaction?

The operating design identifies the failed document, relevant fields, business reason and responsible owner. Correction and replay must preserve the original identity and prevent duplicate posting.

What will ECOM explain during the live meeting?

We review the actual connection path, hosting and deployment requirements, environment prerequisites and detailed technical responsibilities after understanding your ERP and scope.

Integrating or implementing SAP S/4HANA?

Bring your SAP S/4HANA version, installed modules, priority transactions, sample documents and known exceptions. ECOM will review the required systems integration, explain the specific integration path during a live meeting and define a practical implementation scope with your team.