IDoc Mapping in SAP Integration Suite: IDoc Adapter, EDI_DC40 and ORDERS05/INVOIC02 to X12 and EDIFACT

Keep this: job aid

IDoc-to-EDI mapping cheat sheet

• Outbound: SM59 type G (host, 443, /cxf/<address>) → WE21 XML HTTP port (SOAP) → WE20 partner profile → output.
• Inbound: SRTIDOC (urn:sap-com:soap:runtime:application:idoc, GENERIC, /sap/bc/srt/idoc) → IDoc receiver, On-Premise via Cloud Connector, http + virtual host.
• Application/x-sap.idoc = one IDoc, Exactly-Once, keep SapMessageId stable; Text/XML = composite, no Exactly-Once.
• Headers: SapIDocType, SapIDocTransferId (sender DOCNUM), SapIDocDbId, SapIDocAssignMap (bulk).
• EDI_DC40 inbound: fill SNDPRT/SNDPRN exactly as WE20, MESTYP/IDOCTYP, RCVPRT LS + RCVPRN per tenant; DOCNUM by receiver.
• Status: 56 no partner profile · 51 application error · 53 posted · outbound 03 = passed to port only.
• Qualifiers are conditions: PARVW WE/AG ↔ N1 ST/BY; E1EDP19 QUALF 001 customer / 002 supplier material.
• TDS01 has two implied decimals (12,000.00 → 1200000); IT104/PO104 use a real decimal point.
• X12 limits: one GS per ISA, one ST per GS; split first; Number Range objects for ISA13 (field length 9).
• Partner data in the Partner Directory (alternative partners, parameters, pd: mapping refs); one regression pack per partner and message.