This document describes what dispatch handling is and how it works.
Use dispatch handling to control the dispatch of all orders that result in a stock issue.
An order is released for picking, picked, packed, reported and shipped.
The following tables are updated in this process:
|MHPICH||Picking list header|
|MITPIC||Pickers per team|
|MITBAL||Item per warehouse|
|MPIGLD||Picking guideline data|
|DRCLFC||Calculated freight costs|
Dispatch handling controls the dispatch of all orders that result in a stock issue.
Dispatch handling includes the following steps:
The activities in the dispatch handling process are controlled by the dispatch policy, which among other things, determines these procedures:
The logistic identity during the dispatch flow is the delivery number. The delivery number is created or updated during order line entry.
'Shipment' is a number of delivery numbers connected to one shipment. If shipment is used, the dispatch flow (a number of delivery numbers) will be controlled by the shipment. This is known as transportation management and is described in the Transportation Management documentation.
The rules governing the following flow are controlled by the dispatch policy, which determines whether and how the included parts of the flow should be performed.
To pick a release, open 'Delivery. Open Toolbox' (MWS410).
In (MWS410), you can also allocate a release, specify a shipment assembly, control freight documents and carry out packaging steps.
Optional: To plan picking resources, start 'Picking List. Plan Pickers' (MWS415).
To print a picking list, open (MWS415).
You can also print a picking list from 'Picking List. Report' (MWS420).
Optional: Packing can be performed in (MWS420) or in 'Delivery. Connect Packages' (MWS423).
Depending on your settings, you can continue your picking reporting in (MWS420). For more details on reporting, see Wave Picking.
The delivery number is the unique identity of a delivery and is created or updated automatically when entering order lines in M3.
Several orders can be attached to the same delivery number, if the dispatch policy (MWS010) allows for this. When entering new order lines, M3 will reuse an existing delivery number provided that the delivery is:
If you have specified, in (MWS010), that a separate delivery number must be created for each order, M3 will reuse the existing delivery number, only if the order number is identical.
'Shipment' is a number of delivery numbers connected to one shipment. If shipment is used, this means that the dispatch flow (a number of delivery numbers) is controlled by the shipment. This is known as transportation management and is described in the Transportation Management documentation.
As the dispatch flow is controlled by the shipment, the functionality in 'Shipment. Open Toolbox' (DRS100) enables the same dispatch handling steps (described in the previous section) for multiple delivery numbers at the same time. Releases will also be controlled by the shipment (instead of individual delivery numbers).
Picking resource planning is an optional step in the dispatch flow, which includes these functions:
This is the purpose of picking list management:
This is a picking tool for large volumes.
A wave picking list is created by a combination of warehouse, stock zone, and warehouse equipment.
A wave picking list line has the same item number, location, and lot number.
To enable wave picking, a wave number must exist. This is created in 'Delivery. Open Toolbox' (MWS410) when you release deliveries for picking and have defined the settings on the P panel in (MWS410).
A picking line is defined as a record in MITALO that is equal to a picking line after being released for picking.
A wave line is defined as the cumulated quantity of several picking lines. A wave line is a combination of wave, item, location, and lot number.
The purpose of system-guided pick and pack is to guide the user through selected parts of the dispatch flow. This reduces the variability and makes it possible to create a dispatch flow suitable for reporting picking activities in a mobile picking scenario.
Packing is used for safe shipping and dividing of one or more items on an order into units, placing them into an appropriate container package, and marking and labeling the container or package with shipping destination data of the customer, as well as other required information such as, delivery documents.
Packaging actions are useful for various actions:
Packaging actions can be divided into two parts:
Simplified pack processing is intended for customers running M3 with a simple packing process where the most common scenario is that the delivery is packed in a package and the customers want to state the weight for the packages only. This type of processing can be used when more than one package is created. However, this will require more input during the packing routine.
Simplified pack processing also enables printing of CMR documents directly from the packing process (MWS423) and it enables the use of configurable number to be used to identify a CMR-document or a package label. The configurable number can be connected per route, route departure, customer, customer address, or delivering warehouse by using the transportation services.
Package-based picking is a process where the picking is performed based on picking of ready-packed packages or of individual items building a package during the picking process.
The customers that require the package-oriented picking process can be divided in two major groups:
Freight calculation can be performed upon request at any stage before issuing a delivery or shipment. When a delivery or shipment is issued, an automatic recalculation is performed. The calculation is performed according to the freight agreement and transportation service connected to the delivery or shipment and with the information known at the moment of the calculation. The calculation can be re-run whenever requested before the delivery is issued.
When the functionality of the delivery value check is activated for a customer order delivery, issue reporting is not allowed unless the delivery has passed the delivery value check or the delivery has been manually approved for issue reporting. The delivery value check is triggered either manually or automatically for a delivery. In both cases, all active picking lists must be moved to a dock location to enable the delivery value check. The automatic delivery value check is triggered, by the auto-start job in (MWS976), when the last active picking list suffix is moved to a dock location.
A prerequisite that must be fulfilled is that the free consolidation fields in the dispatch policy must contain a value for payer (OAPYNO). The reason for this is that only customer orders with the same payers are allowed when the delivery value check is activated.
A delivery value check is performed by the use of payers credit limit 2 reduced by the outstanding invoiced amount compared to the value of the actual delivery. The purpose of this is to meet the requirements for allowing issue reporting of deliveries of less values, while high value deliveries can be held.
The value of a current delivery is calculated according to same principle as is in use in M3 today for the calculation of a pro forma invoice. The value is calculated as the net price on the order line multiplied by the allocated quantity at the dock location. The calculated values are then totaled for all included lines in a delivery.
If the delivery value is higher than the result of credit limit 2 minus the outstanding invoiced amount for the payer, the delivery will fail the delivery value check and the issue reporting will not be allowed. If failed, the delivery value check may be manually re-run in cases where any amounts or quantities used in the calculation have been changed. A delivery can also be manually approved for issue reporting, if the delivery is considered as delivered regardless of the outcome of the delivery value check.
This status is stored in the MHDISH table and can be displayed in 'Delivery Toolbox. Open' (MWS410).
00-Not released for auto allocation.
01-Released for auto allocation. Picking lists could exist if blocking point=1 in the dispatch policy (MWS010).
02-Failed due to allocation control. The status will be reset to 01 when an order line is changed or when an allocation is performed.
03-Stopped due to credit check or customer stop. The status is reset to 01 when the customer order stop is changed (OIS120), or when the customer stop is changed in (CRS610). This status is only relevant for customer orders.
05-Allocation control passed, ready to be released for picking.
50-Picking list(s) created, delivery blocked from further additions.
70-Shipped from consignor.
This status is stored in the MHDISH table and can be displayed in (MWS410).
These are the valid alternatives:
00-Packing not used.
10-Packing not started.
20-Packing started but not completed.
This status is stored in the MHPICH table and can be displayed in 'Picking List. Plan Pickers' (MWS415) and 'Picking List. Report' (MWS420).
These are the valid alternatives:
30-Not ready for printing and reporting
40-Ready for reporting
50-All lines reported as moved to pack location
60-All lines reported as moved to dock location
70-All lines in transit, not received (only for distribution orders)
90-All lines reported as issued from inventory