Consignment Order in SAP S/4HANA TM based upon Advanced Shipping Notifications
This blog post is a follow-up to my previous blog post, “Planning Transportation in SAP S/4HANA TM based upon Advanced Shipping Notification
In this blog post I try to show how the newly introduced document, “Consignment Order” fits into the overall procurement process.
Note: This blog post shares my personal insights based on my experience working with customers in Manufacturing and Retail industry and my insight into SAP solutions only. I have demonstrated the functionality in this blog post using system screen images with relevant data for ease of understanding for the readers. It should be noted that these screens and the data is from SAP’s internal test systems and has no relation to any external source
In the picture below, you can see how the new document “Consignment Order” is used in relation to the ASNs
Documents in S/4HANA
- Purchase Order / Contract / Scheduling Agreements etc can be used as the source of the Freight Units
Below you see a PO with two schedule lines
When the Purchasing Documents are integrated to SAP Transportation Management, it results into Freight Units (how many you generate is controlled via the FUBR setup)
2. ASN receipt into SAP TM as a Consignment Order is enabled via the TOR Generic service interface TransportationOrderGenericRequest_In.
More Information on the TOR Generic Interface can be found below
Consignment Order (Order Type customization needs to be in place) is created once the message is processed successfully. Below I created 2 ASNs for the same PO that resulted into 2 Consignment Orders (8 EA and 2 EA respectively)
You can read more about this Consignment Order on the SAP Help
As I have mentioned in the previous blog post, special logic to handle the consumption of Freight Units is delivered. You can see how system consumes the available Freight Units with Consignment Order.
You can see that out of 10 initial FUs only 3 are remaining (FU ending with *84787 now has 8EA) and remaining FUs are not changed.
Below you see that once the Consignment Order for 2 EA is received the remain FUs are consumed. So what is left out of initial 10 FUs are only 2 FUs with 8EA and 2 EA quantities which are incoming via the 2 ASNs.
3. The LSP can also communicate the Truck Transport information (which ASNs are part of the Truck) in the form of Despatch Note which results into a Freight Order. This information is also received into SAP TM is enabled via the TOR Generic service interface TransportationOrderGenericRequest_In.
Below you see how the FRO links the Consignments.
To inform the warehouse about the incoming Truck, the Delivery Proposals can be initiated from the Freight Order, which would create the Inbound Deliveries and distribute them to the Warehouse.
Happy Reading !!!
Thank you Atul! Great article.
Thank you for sharing your work & vision 🙂
Very crisp explanation of entire process.
Thank you so much for penning it down so well!
Thanks for the post! This setup requires every suppliers to send EDI 856 message to TM. SAP also have another solution in this area to use ARIBA Supply chain collaboration to generate ASN (Portal where suppliers can specify the packaging and contents of shipment easily).
Is there any integration or process flow on how to use this ASN from ARIBA SCC and TM ?
Nicely Explained Atul
Thanks for the detailed explanation. I would like to ask a couple of questions about the inbound Freight Order creation via B2B interface TransportationOrderGenericRequest_In from carrier dispatch note.
Is it a standard field now in the interface to update ASNs which are being shipped together? Secondly, are the consignment orders directly linked to the FO created in such a way? Is there any standard logic within TM which does this assignment?
Thanks and Regards,