Extend or map?

Sooner or later a trading partner asks for a value SAP does not send. Great Lakes Fleet Services wants Contoso Motor Co.'s core return agreement number on every alternator line of its 810 invoices, so its accounts payable can match the core deposit to the old alternator it will send back. Lakeside Components wants Contoso's Detroit dock number on every 850. Both requests sound alike. They need opposite answers, and this lesson is about telling them apart.

Three ways to supply a missing value

The dock number is the easy case. Plant 1710 Detroit has one receiving dock for Lakeside's trucks, so the value is a constant per plant. Process Orchestration already receives the plant in the ORDERS IDoc and can map plant 1710 to the dock number with a value mapping. No SAP change, no transport, no regression risk in SAP S/4HANA.

The core agreement number is the hard case. It lives in Contoso's own table ZCMC_CORE_AGR, the custom core return agreement object carried over by the conversion (about 2,600 agreements). Nothing in the billing document or in INVOIC02 carries it. Middleware could call back into SAP to look it up for every invoice line, but that turns an asynchronous interface into a chain of synchronous calls that fails whenever either side is slow. The clean answer is to put the value into the IDoc where it is created: an extension.

A clean-core lens

An IDoc extension is classic extensibility: customer segments in the Z namespace, assigned to an SAP basic type, filled by ABAP in a customer exit. SAP designed extensions to be upward compatible (basic types cannot lose segments, so your appended segments keep working), but the ABAP that fills them is custom code that must be maintained, tested and upgraded. Under SAP's clean core guidance, how an extension is classified depends on what that code uses: reading Contoso's own tables and SAP's documented interfaces keeps it on the safer side, while reading SAP internal tables or changing SAP objects pushes it toward the levels SAP discourages. Run the ATC clean core checks on the exit code like on any other custom code.

Questions to ask the partner first

Before choosing, ask the partner precisely what it needs and why. Which EDI segment and qualifier should carry the value, on which level (header or line)? Is it mandatory for every document or only some? What happens on their side when it is missing? Great Lakes' answers shaped the design: the core agreement reference goes into a reference segment in each 810 line loop, it is needed only for alternators sold with a core deposit, and invoices without it are still accepted. That last answer made the segment optional and kept every other invoice unaffected.

SAP S/4HANA Cloud Public Edition does not give you the classic IDoc development transactions; integration there runs through released APIs and communication arrangements. Everything in this course applies to SAP S/4HANA Cloud Private Edition and on-premise, where Contoso runs.