Evolution of SAP ERP Integration: Navigating Changes in IDOC Handling for Inbound Deliveries

Background: In the realm of SAP, clients frequently necessitate capturing custom fields (Z fields) on inbound deliveries that are not inherently part of the standard SAP Inbound delivery structure. In earlier versions like SAP ERP 5.0, consultants extended the IDOC structure (Basic IDOC Type: DESADV03) to capture Z fields, utilizing user exits like EXIT_SAPLV55K_004 to transmit Z field data from the IDOC structure to custom fields on inbound deliveries.

In SAP S/4 HANA, the traditional user exit EXIT_SAPLV55K_004 is not invoked with the Functional Module /SPE/IDOC_INPUT_DESADV1.

The crucial question arises: How can we efficiently transfer custom fields captured in the IDOC segment to inbound deliveries?

Answer: BADI: /SPE/INB_ID_HANDLING takes the place of user-exit EXIT_SAPLV55K_004.

The BADI encompasses methods like PARSING_IDOC for data capture and GN_DELIVERY_CREATE, which can be implemented to effectuate the data transfer.

Caution: Developers should exercise caution when considering the use of the inbound delivery BADI LE_SHP_DELIVERY_PROC for transferring data from IDOC’s Z fields to inbound delivery, as there is no inherent correlation between IDOC numbers and inbound deliveries. In scenarios where multiple IDOC(s) are processed simultaneously, BADI LE_SHP_DELIVERY_PROC may not function as expected.

Here is a sample code:









Meeting the prevalent need to transfer custom fields from IDOC to inbound delivery involves utilizing an appropriate Business Add-In (BADI) to seamlessly move data from IDOC custom fields to corresponding inbound delivery custom fields.

Was this article helpful?

Related Articles

Leave A Comment?

You must be logged in to post a comment.