This blog post is a follow-up to my previous blog post, "Planning Transportation in SAP S/4HANA TM based upon Advanced Shipping Notification
https://blogs.sap.com/2021/01/09/planning-transportation-in-sap-s-4hana-tm-based-upon-advanced-shipp...
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
Process Flow
In the picture below, you can see how the new document "Consignment Order" is used in relation to the ASNs
Consignment Process Flow with Incoterms DDP
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
Purchase Order with 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)
Freight Units for PO
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
https://help.sap.com/viewer/733c8b37b3f546a1b08750e8aeabb887/2020.000/en-US/9740cb5147dd9d55e1000000...
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
https://help.sap.com/viewer/e3dc5400c1cc41d1bc0ae0e7fd9aa5a2/2020.000/en-US/908e8ab6945a47edb1ade56e...
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.
Consignment Order 1
Consignment order 1 Item Hierarchy
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.
FU consumption based on Consignment Order 1
Consignment Order 2
Consignment Order 2_Item Hierarchy
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.
FU consumption based on Consignment Order 2
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.
Freight Order with Consignements or ASNs
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.
Initiate Delivery
Freight Order with Linked Inbound Delivery
Happy Reading !!!