How SPS Commerce Fulfillment for SAP connects to SAP S/4HANA (also SAP ECC)
IDoc exchange with the SPS network
SAP outputs and receives IDocs such as ORDERS, ORDRSP, DESADV and INVOIC, which SPS translates to and from each retailer's EDI format. SPS says it runs this as a managed integration, including map maintenance. The exact IDoc types and transport (for example file, AS2 or SAP PI/PO) are agreed during onboarding.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Retailer | SAP | Purchase order (EDI 850 mapped to ORDERS IDoc) | Retailer sends the order |
| SAP | Retailer | PO acknowledgment (855) | Order confirmed in SAP |
| SAP | Retailer | Advance ship notice (856 from DESADV) | Post goods issue |
| SAP | Retailer | Invoice (810 from INVOIC) | Billing document released |
| Retailer | SAP | Remittance or status messages | Retailer payment or compliance cycle |
Setting it up
- 1Scope trading partnersList retailers, their required documents and any compliance scorecards.
- 2Agree IDoc types and transportConfirm with SPS which IDoc message types, partner profiles and connection method are used.
- 3Configure SAP partner profilesSet up logical systems, ports and partner profiles (WE20, WE21) for inbound and outbound.
- 4Map customer and material identifiersMaintain customer-material info records and retailer item numbers, GTINs and ship-to codes.
- 5Run test cycles per retailerRetailers often require certification test transactions before go-live.
- 6Set up monitoringUse WE02 and BD87 for IDoc status and decide who handles errors daily.
What usually breaks
- !Missing customer-material or GTIN data causes inbound ORDERS IDocs to error in WE02 at the item level.
- !ASN timing wrong: shipping notice sent before packing or HU data is complete triggers retailer chargebacks.
- !Unit of measure differences between retailer packs and SAP base units cause quantity errors.
- !Retailer spec changes land on the SPS side, but SAP-side fields that must supply the new data are not updated.
- !Duplicate POs from resent files if idempotency is not checked.
A private AI layer across both systems
IDoc error triage
An assistant reads failed IDocs in WE02 and the partner spec and says in plain language what data is missing, drafting a master data fix for approval.
Chargeback analysis
Link retailer compliance fines to the shipment and ASN data to find repeating causes.
Order status questions
Let customer service ask where a retailer PO is, answered from IDoc and delivery data.
When something else fits better
- Self-managed EDI through a VAN or SAP Integration Suite is an option if you have an EDI team and want control of maps.
- A broader B2B platform such as SEEBURGER or OpenText Trading Grid may fit if you also trade outside retail.
- For a handful of partners, SAP standard EDI with a simple translator may be cheaper.
Frequently asked questions
Does SPS Commerce work with SAP ECC as well as S/4HANA?
SPS lists solutions for SAP enterprise users on both S/4HANA and ECC. Because the exchange is IDoc-based, a move from ECC to S/4HANA usually leaves the retailer side unchanged, though partner profiles and some fields need retesting.
Who maintains the maps?
SPS positions this as a managed service that includes map maintenance, so retailer spec changes are handled on its side. You still own the SAP data quality that feeds those maps.
What documents are typical?
Orders, order acknowledgments, ship notices and invoices are the core set for retail fulfillment. Others, like inventory feeds, depend on the retailer program.
Pairing documented at www.spscommerce.com/eur/integrated-fulfillment/system-integrations/sap-solutions . SPS Commerce Fulfillment for SAP is a product of SPS Commerce; Netray is independent and not affiliated with either vendor.