Cartonization planning is used to optimize the packing of shipping handling units (HUs) based on information from product master data and outbound delivery orders. Cartonization planning results in the creation of planned shipping handling units (PSHUs) that can be used as templates for creating shipping HUs during picking or packing.
Performing cartonization planning supports two primary goals:
Selection and combination of the right packaging materials to minimize empty space (which means reducing shipping costs) and the reduction of product damage during transportation due to fewer under-utilized HUs.
Make information available early in the execution process about shipping containers that may be used to optimize other processes.
A PSHU is an object similar to a shipping HU, describing a packaging material and the items that it contains. In contrast to a shipping HU, a PSHU does not physically exist in the warehouse and is only used to plan shipping HUs. You can create PSHUs manually or automatically in cartonization planning. You can create nested PSHUs for cartonization planning of deliveries where HUs are packed into larger HUs.
Automatic cartonization planning uses algorithms to create PSHUs. Algorithms are defined as implementations of the BAdI: Cartonization Planning Algorithm. The default implementation aims at minimizing the number of HUs. The default algorithm uses a heuristic approach, but the result is no optimization.
A manual cartonization planning or the changing of an automatically created cartonization plan is also possible.
Process Profile
The cartonization planning process profile defines the point when the planned shipping HUs are created, and the creation point when the planned shipping HUs are used to build shipping HUs.
Planned shipping HUs can be created automatically for outbound delivery orders, for waves, or during the warehouse order creation. Additionally, you can also repack, unpack, or delete PSHUs manually.
PSHUs can then be used as templates for the creation of the shipping HU during picking or during packaging in a work center, or using radio frequency (RF), depending on the process profile.
Algorithm Profile
The algorithm profile defines the way the system creates planned shipping HUs. An algorithm contains the properties that are used for cartonization planning.
Note
Split Delivery Item:
The quantity of an outbound delivery item can be split if it does not fit completely into one PSHU.
Dimension Check:
The cartonization planning checks the dimensions (length, weight, and height) of outbound delivery items against the packaging materials for the creation of the PSHUs.
Filling Level:
The maximum level (in percent) up to which the packing material should be filled.
Iteration Limit:
Controls how many iterations the algorithm carries out to find further approximations to a solution. This means that the iteration limit affects the runtime and the quality of the solution.
The algorithm profile is assigned to an algorithm sequence. This algorithm sequence lists the different algorithms to be used. The algorithm profile is determined using various fields, such as warehouse process type, activity area, and others. The fields to be used are set up in an access sequence. The determination table is maintained under Extended Warehouse Management → Settings → Determine CAP Algorithm Profiles.
Algorithms
The SAP standard algorithm SAP1 minimizes the number of HUs by checking the weight, the volume and optionally the dimensions (see the predefined properties in the previous list). This is the default implementation of the BAdI Cartonization Planning Algorithm.
Since SAP EWM 9.5, the algorithm SAP2, SAP SCM Basis Package Builder Algorithm, is available with the BAdI implementation /SCWM/EI_CAP_PB_TM. This is the same algorithm that SAP Transportation Management uses to create freight units. This algorithm does not replace the existing cartonization algorithm, but it provides more features. The package building algorithm works as follows:
The system first tries to create full pallets of a single product.
If a quantity remains, the system creates mixed pallets where each layer consists of a single product.
If the system cannot create layers of one product, it creates mixed layers.
The system takes into account the weight, height, and volume of the products.
The details are defined in the Package Building Profile. The SAP Note, 2581421 - Package Builder Feature Documentation including enhancement options, includes an extensive documentation which explains relevant aspects of the Package Builder.
A customer can define their own, optimized algorithm by their own implementation of the BAdI Cartonization Planning Algorithm.
Monitoring of PSHUs
You can monitor the created planned shipping handling units in the warehouse management monitor in the monitor node Planned Shipping Handling Unit. You have several selection criteria, for example:
Document, wave, or both
Partner
Shipment
Route
For each selected PSHU, the monitor displays the relevant header data. Additionally, the monitor displays the relevant data of delivery items packed into the selected PSHU. If a value is not unique, for example, different TUs are assigned, the monitor displays the value ***.
The SAP standard layout Planned Shipping HU Aggregation (0/PSHU_AGGR) displays the following:
Summary of the gross weight and volume per HU type and carrier
Summary of the overall gross weight and volume
Note
Deletion of PSHU
You can delete obsolete PSHUs using the transaction DELETE PLANNED SHIPPING HANDLING UNITS.
Using this transaction, you can only delete a PSHU if all of its related outbound delivery order items fulfill the selection criteria. If you want to delete a PSHU that contains delivery items that do not fulfill your selection criteria, you have to use the transaction CARTONIZATION PLANNING FOR OUTBOUND DELIVERY ORDERS or CARTONIZATION PLANNING FOR WAVES in execution mode Deletion of PSHUs. These transactions also offer further criteria to select PSHUs for deletion.
Note