Monday Knowledge Snippet (MKS) – 77 Maximum Stacking Factor for Package Building
Today’s blog describes the handling of the maximum stacking factor of materials during package building. After the move to the S4 it became obvious that some adjustments are required.
Background: The maximum stacking factor is used to define if a result pallet can have something stacked on top or not during SAP Transportation Management Load Planning. The pallet must be flat on top and the maximum stacking factor of the product (or in case of a mixed pallet ALL products) must be > 1.
So far the source of this maximum stacking factor was the material / product header information.
Stacking Factor on SCM Product header
This field is always available in the SCM product maintenance, but in the S4 material definition it is actually not meant to be used for products by default and therefor invisible.
Change: First of all – to stay compatible of course nothing changes when this field is maintained for the product. But in the future it is recommended to use the field maximum stacking factor available in the alternative unit of measure definitions.
Alternative Unit of Measure definitions in SCM Product
Alternative Unit of Measure definitions in S4 Material
In case the product header field is not defined, the PB will use the maximum stacking factor from the packaging entry (100 EA -> 1 PAL). The Base UoM to Base UoM entry (product to itself) will be used for the new PB feature ‘Detailed Package Building’ coming soon. The layer specific entry might be considered also when customers request this. As visible in the screenshots there will be a further improvement by providing a maximum top load going beyond a YES / NO logic. For this more info will follow.
Important to mention: Above logic only applies for not closed package materials (pallets). For closed package materials like cartons / boxes the material specific maximum stacking factor is applied (1:1 entry).
I hope with the adjustment the topic becomes clear and the PB processes this with a consistent logic.
This change is available for S4_1709 and TM 9.1 – 9.3 with note 2689122 (released), for S4_1809 with note 2680497 and for TM 9.4 and following with note 2622572.