Free tool for SAP S/4HANA (on-premise and private cloud)
SAP S/4HANA Integration and EDI Designer
Pick the business objects and the systems you need to connect, and get an SAP S/4HANA integration inventory that names the real interface for each flow: IDocs such as ORDERS05, DELVRY07 and INVOIC02, released OData APIs such as API_SALES_ORDER_SRV and API_BUSINESS_PARTNER, asynchronous SOAP services, business events or BAPIs. Switch to EDI mode to see how X12 850, 855, 856 and 810 (and the EDIFACT equivalents) map to IDoc segments, partner profiles and the SD or MM documents they create.
Business objects
Toggle what moves between systems. Presets add a typical set.
Targets, direction and frequency
Direction is seen from S/4HANA.
Nothing in scope yet
Integration inventory
S/4HANA offers three main integration surfaces: IDocs over ALE or EDI (partner profiles in WE20), released synchronous OData APIs and SOAP services published on the SAP Business Accelerator Hub, and business events for change notifications. Middleware is usually SAP Integration Suite (Cloud Integration) or an existing SAP Process Orchestration 7.5 system; any iPaaS that speaks OData, SOAP or IDoc can also connect.
Your inventory appears here
Exports include the inventory, rationale, field maps with your target names, selected EDI maps and risks. No sign-in needed.
How to use it
- 1
Pick the objects
Select the business objects in scope, such as business partners, products, sales orders and outbound deliveries.
- 2
Add the target systems
For each object choose the system on the other side, the direction seen from S/4HANA and how often it must move.
- 3
Read the inventory
Each row names the S/4HANA interface (IDoc message type, OData service, SOAP service or event), why it fits and what to watch for.
- 4
Check the field map
Open the starter map for an object, fill in the target field names and note the keys and required fields.
- 5
Export or save
Download the design as PDF, Excel, Word or CSV, save it to your account, or send it to an engineer for review.
S/4HANA interfaces in this tool
- IDocs over ALE asynchronous
- Asynchronous application documents (for example DEBMAS, MATMAS, ORDERS, DESADV, INVOIC) sent through a port and partner profile, triggered by output determination or change pointers. Proven for high volume, with status tracking in WE02 and reprocessing in BD87.
- IDocs for EDI (partner profiles and translator) asynchronous
- S/4HANA does not parse X12 or EDIFACT. A translator or SAP Integration Suite (Trading Partner Management) converts partner documents to IDocs and back; inbound IDocs post through process codes such as ORDE, outbound IDocs come from output types on the sales, delivery, billing or purchasing document.
- Released OData APIs (A2X) synchronous
- Synchronous REST services such as API_SALES_ORDER_SRV, API_BUSINESS_PARTNER and API_PRODUCT_SRV, activated in the SAP Gateway (/IWFND/MAINT_SERVICE). Business logic and authorizations run as in the Fiori apps; use them for lookups and for creates that need the document number back.
- SOAP services (A2A, asynchronous) asynchronous
- Released asynchronous web services for bulk or replication scenarios, for example Sales Order (A2A) OP_SALESORDERBULKREQUEST_IN, Journal Entry - Post (Asynchronous) and Business Partner replication. Configured in SOAMANAGER; fits middleware that queues and retries.
- BAPIs and RFC function modules synchronous
- Classic synchronous function calls over RFC, for example BAPI_SALESORDER_CREATEFROMDAT2, BAPI_PO_CREATE1, BAPI_ACC_DOCUMENT_POST and BAPI_GOODSMVT_CREATE, committed with BAPI_TRANSACTION_COMMIT. Still widely used on premises; prefer a released OData or SOAP API where one exists for clean core.
- Business events (Event Mesh) asynchronous
- S/4HANA publishes created, changed and deleted events for business objects (for example Sales Order Events, Business Partner Events, Outbound Delivery Events) to SAP Event Mesh or Advanced Event Mesh. Events carry mainly keys and a few attributes, so the consumer usually reads the full object by OData.
- CDS views and ODP extraction (read only) asynchronous
- Released CDS views such as I_SalesDocument, I_BillingDocument and I_JournalEntryItem, extracted through ODP to SAP BW, SAP Datasphere or a third-party tool. Never write to tables; direct database reads also depend on your HANA license (runtime or full use).
- SAP Integration Suite or SAP PO asynchronous
- Cloud Integration iFlows (or PI/PO interfaces) handle mapping, routing, retries and B2B. SAP PO 7.5 is the last PO release, so new builds normally target Integration Suite; check SAP's current maintenance dates before planning a migration.
Questions
Should I use IDocs or OData APIs for an S/4HANA integration?
IDocs are asynchronous, carry the full document and have mature monitoring and reprocessing (WE02, BD87), so they suit EDI, master data distribution and high-volume feeds. Released OData APIs are synchronous and return the document number immediately, so they suit lookups, price and availability checks and creates from a web or mobile app. Many landscapes use both: events or IDocs out, OData in.
Which IDoc types does S/4HANA use for EDI orders, ASNs and invoices?
Inbound customer orders use message type ORDERS with basic type ORDERS05 and process code ORDE (function module IDOC_INPUT_ORDERS). Order confirmations use ORDRSP, advance ship notices use DESADV with basic type DELVRY07, and invoices use INVOIC with basic type INVOIC02. Check the exact basic type and extension in WE20 for each partner.
Where do I find the S/4HANA OData APIs for on-premise?
The SAP Business Accelerator Hub (api.sap.com) lists the SAP S/4HANA on-premise APIs, for example API_SALES_ORDER_SRV, API_BUSINESS_PARTNER, API_PRODUCT_SRV and API_MATERIAL_STOCK_SRV, with their state. Some are marked deprecated, such as API_PURCHASEORDER_PROCESS_SRV (replaced by the OData V4 Purchase Order API) and the unversioned API_OUTBOUND_DELIVERY_SRV (use version 0002). Activate the service in /IWFND/MAINT_SERVICE before calling it.
Does S/4HANA translate X12 or EDIFACT itself?
No. S/4HANA works with IDocs. A translator or SAP Integration Suite converts X12 or EDIFACT into IDocs and back, manages envelopes and functional acknowledgments, and connects to the VAN or AS2. Integration Suite includes Trading Partner Management, and SAP publishes migration content for B2B interfaces moving from SAP PO.
Why does my inbound ORDERS IDoc fail with status 51?
The usual causes are a sales area that cannot be determined (maintain VOE2 or send E1EDK14 sales organization, distribution channel and division), a partner number that is not converted (VOE4), a customer material without a customer-material info record, or a missing schedule line segment E1EDP20. Process the IDoc in WE19 in foreground to see the exact field, fix the data and reprocess it in BD87.
How does output management affect EDI in S/4HANA?
S/4HANA introduces Output Control based on BRFplus and bgRFC, and the Conversion Guide notes that other existing frameworks can still be used depending on the application. In practice some documents run on Output Control and others on the condition technique (NAST, NACE). Check which framework each document type uses before you configure EDI output.
Can I read S/4HANA tables directly for reporting?
Prefer released CDS views (for example I_JournalEntryItem over ACDOCA) extracted through ODP, which keep the semantics and work across upgrades. Direct reads on HANA tables depend on your HANA license, bypass authorizations, and miss changes such as stock being derived from MATDOC and pricing results moving from KONV to PRCD_ELEMENTS. Never write to tables.
Is this different for SAP S/4HANA Cloud Private Edition?
The interfaces are the same as on premise (IDocs, OData, SOAP, BAPIs and events), because Private Edition runs the same software in a hosted landscape. What changes is connectivity: plan network routes, Cloud Connector or VPN, and who operates partner profiles and certificates with your hosting arrangement.