Monday Knowledge Snippet (MKS) – 93 TM 9.6 – Exclusive Package for Customer
In blog MKS90 I described the new process available with SAP Transportation Management 9.6 – Consolidation Package Building (CPB) capable to create mixed packages containing multiple orders of different customers. With MKS91 I introduced the new business document to persist stable packaging information – the Package Unit. Today I would like to continue with the feature ‘Exclusive Package for Customer’. Being able to mixed anything is great, but not less important is to tell the system when NOT to consolidate.
Remember, now it is possible to steer in the Freight Unit Building rule if packaging information shall be persisted or not. So in scenarios where this can be decided this early, all good. But as soon as this is more dynamic (for example based on the ordered quantity), SAP TM offers options to manipulate the behavior of the CPB.
So imagine a scenario where customers can place multiple orders per day. Depending on the business partner requirement (customer always demands a separate pallet) or the ordered quantities, all items of all orders of such a customer shall be consolidated together, but not mixed with other customers. The transportation planner shall have the option to change the setting depending on the current plan situation to improve utilization and balance delivery efficiency. Keep in mind – when delivering the order to the customer it is of course easier to find all items when they are on the same pallet. But if this is done for too many customers, the truck utilization goes down and more tours are required.
So how to make this run?
First setting required is to only estimate the package quantity, but not persist the result. By setting the Package Building Profile, the PB is activated.
Freight Unit Building Rule activating Package Building
The Supply Chain Execution Package Builder (SCE PB) will now check the existing package building definitions and master data, and create package accordingly. In the package type assignment, there is the new option to mark a business partner as exclusive.
Package Type Assignment – Business Partner definitions
At this stage, there is anyway only a single business partner per Freight Unit. But the PB will return this setting back to the business document, where this info will be persisted and visible on document header level.
And here come the dynamics – when planning with this Freight Unit (or multiple of the same customer), the planner can adjust this setting. So either he can decide to make a specific Freight Unit exclusive for the customer – today this typically low order volume customer has placed a big order. Or he can switch the standard packaging definition off and force a multi customer consolidation.
Adjustment of exclusive package for customer indicator per Freight Unit
When then executing the ‘Build Packages’ function for the capacity document, the system will respect the current settings of all Freight Units and build the packages accordingly.
Of course it is a valid result that all Freight Units for the same exclusive package customer require multiple pallets.
An option to further improve the planning result is to create Package Units for all Freight Units of exclusive package customers. As they share the same locations, it is reasonable to assume they go together and the routing optimizer can handle them better as stable packaging. The option to create Package Units for Freight Units is available in the Freight Unit list.
Here is the link to the MKS overview page: https://blogs.sap.com/2013/05/21/monday-knowledge-snippet-series/
Here is the link to the LinkedIn discussion: https://www.linkedin.com/feed/update/urn:li:activity:6538734079334981632/
Here is the link to the Detailed Package Building overview MKS: https://blogs.sap.com/2019/02/04/monday-knowledge-snippet-mks-79-supply-chain-execution-package-builder-enhancements-detailed-package-building/
Very informative and useful article for beginners!
First of all thank you for all these MKS 😀
Our customer is really interested on doing only an estimation of packages count during FUBR. This option "Estimate Package Count Only" is available through notes in 1809 Embedded or only on 1909 version ?
Only 1909. Even though it is great to hear that customers are interested in this and want to have it as early as possible: This is the development of a whole release affecting many spots in TM! And the current release of S4 is already 2020!
Thank you for the answer 🙂
Bad for me, but I totally understand.
I just checked in my 1809 version by curiosity, and the option seems to be available.
Available but not working in 1809 ? Or only part of the functionality ?