After being quiet for some time now spending my time on finalizing huge developments for SAP Transportation Management 9.6 and S4 1809, I would like to kick-off a chain of MKSs to rollout the new features.
Key message: The SAP TM Load Planning journey continues! Having started this with TM 9.1 introducing the Load Plan Optimizer to create legally compliant truck, trailer and container load plans (see MKS37), taking a major step forward with TM 9.3 coming out with the Package Builder (see MKS53), offering Load Consolidation as new automated planning option starting with TM 9.4 (see MKS65), and going into detail for truck planning with flexible split deck planning in TM 9.5, we proved that we are committed to this topic. Next to the main developments, especially in the area of package building many small features have been added as a reaction to requirements of the growing number of customers.
Listening carefully to customers, we realized that even with the already existing load planning features another major investment would be required to finally become competitive. Building mixed packages just based on layers and volume proved to be not sufficient and it became clear that the SCE Package Builder had to move closer to reality. Luckily, we found a fantastic front-runner customer wanting to go this path together with us, and plenty others to verify the direction the Package Builder was taking.
The whole development of TM 9.6 in this area had actually 3 key topics:
Detailed Package Building
Consolidation Package Building as new SAP Transportation Management process to create mixed customer packages / pallets (MKS90)
Package Unit as new SAP Transportation Management document (MKS91)
As soon as I have explained Detailed Package Building, I will add MKSs for the SAP TM specific topics.
So what does Detailed Package Building mean for us? Basically, it means that the SCE PB gets physically. So far driven by packaging rules (in short, but incomplete: 100 pieces make a full pallet, 10 pieces make a full layer, combine the rest using volume), it offers now a Package Builder Optimizer (PBO) determining exact positions for all items to be packaged. What sounds so easy, gets really complex when thinking about different product sets and constraints that might influence such a detailed load plan per package. So here comes a list of what the new PB(O) supports (see also MKS87😞