Freight Order Number on DELVRY06 or DELVRY07 (ASN 856) idoc

[prasad_bankar]

Hello SAP experts,

I'm working on S4Hana 2020 EDI interface development having TM integration and looking for a technical solution to capture Freight Order number (FO#) from Transportation Management to be sent on outbound DELVRY07 idoc from SAP to partner as an ASN from the delivery.

Standard basic type DELVRY06/07 idoc segments don't have any field for underlying Freight Order as there would be multiple freight orders. Ideally in ECC world we would send the SHPMNT05/06 which is not valid in S4-TM scenario as there is no Shipment document (VTTK) created as such. I assume we need to have custom segment for capturing FO# on DELVRY07 but would like to understand the flow and technical solution. I appreciate any pointers to this topic.

[TuncayKaraca]

Hi Prasad,

You defined the request very well. Yes, standard IDOC Type DELVRY07/06 needs to be extended with a custom segment on proper level of the standard segments. Then the custom segment / fields need to be populated with Freight Order numbers (FO#) in a user-exit coding of the outbound process.

Check the document How to Extend an Outbound IDoc

Thanks,
Tuncay

[prasad_bankar]

Hi Tuncay,

I really appreciate your help. Just wondering if we want to avoid custom idoc segment on DELVRY07 is there any other way like directly capturing the FO# and updating the delivery (VL02N) in some reference field which is also present on DELVRY07. As in S4HANA , TM (transportation management) is no longer on a separate instance we can use some other means like BAPI or something. I'm not sure as I heard from my developer that BAPIs don't work in TM as it's all BOBT. The flow of documents creation is SalesOrder->FreightUnit->FreightOrder->Delivery->Invoice.

[TuncayKaraca]

Hi Prasad,

If you want to avoid custom Idoc segment on DELVRY07 and if some related -unused- delivery fields and DELVRY07 segment are identified then these delivery fields can be populated with F0# in a user-exit / enhancement during VL01N/VL02N operation. Sometimes IDocs' Text segments (header or item level) are used for these kind of requirements since multiple texts can be added with using various Text Ids.