Launching
From this screen, the user can:
- Address on issue one or several waves, i.e. request the system to determine stock objects to be issued, create picking orders, replenishment orders, transfer orders for the presentation of type 'flow merging of flows', parcels as well as the reports necessary for the preparation and the shipment.
- Simulate one or several wave launch(es) so as to detect the number of POs, parcels, transfer orders for the merging of flows and shortage DO lines.
The issue search algorithm is a complex one that uses numerous setups.
Prerequisite
Refer to documentation Implementation
Screen management
The screen is comprised of a simple grid displaying the waves of 'merging of flows' type or not to, be launched for preparation (wave with status 1-Pending launch or with status 4 - pending phase 2).
Entry screen
Presentation
For each wave to be launched on preparation, the number of DOs, the number of DO lines, the weight and volume of the wavve are displayed.
One or several waves can be selected with the mouse or via right-click of the mouse and by means of the options "Check all" or "Uncheck all".
The checkbox "Simulation" is used to switch from a wave launch mode (by default) to the simulation mode where all data are deleted further to the processing.
Upon wave launch, the following processes are carried out:
Without merging of flows and second merging of flow phase:
- Output movement generation
- Prepacking of output movements if DO in prepacking preparation mode
- Prepalletization of output movement if DO in prepalletization preparation
- Generation of picking orders
- Generation of temporary DNs if the output configuration requires a temporary DN.
Merging of flow first phase:
- Generation of transfer movements to splitting area.
The splitting area is defined from the sequencing method of the splitting stores for the stock object picking store.
Splitting stores can be reserved for small and/or large capacities (this depends on the issue configuration setup and on thresholds defined in the product issue method) or for container types (this depends on the issue configuration setup and on grouping codes defined in the container types table and in the splitting store)
Reports are only generated for processings (not for simulations):
- POs are generally printed with the laser-type printer set up on the preparation area and depending on the DO preparation method.
- The labels of a prepall. PO parcel labels are printed with printer no. 1 of the preparation area and based on the current depositor issue configuration setup and on the DO preparation method.
- The labels of a prepall. PO parcel are printed with printer no.1 of the preparation area if setup "Grouped labems" (issue configuration, tab Packing) is not ticked. It if is ticked, it is the printer no. 2 that is used (that for SU labels)
- SU labels are printed with printer no. 2 of the preparation area.
- replenishment orders and labels are printed based on the issue configuration setup,
- transfer orders of type merging of flows and transfer labels are printed based on the issue configuration setup
- temporary delivery notes as well as packing lists are printed with the laser-type printer set up on the preparation area depending on the DO preparation method and on the current depositor issue configuration,
- the preparation load document is printed based on the current depositor issue configuration as well as on the list of wave shortages.
In case of addressing problem, Warehousing displays an anomaly report describing, for each DO, the cause of the non addressing.
After correcting the cause, the addressing can be launched once more by launching additional POs (for DOs without packing management) or by the same option if the DO is completely in shortage and if the DO manages balances.
Close
Fields
The following fields are present on this tab :
| No help linked to this field. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| When launching a wave, this parameter is used to force the creation of associated missions with status '6-blocked', thus ignoring the mission setup at site level.
|
| This parameter is used, when launching a wave, to create the associated missions with the priority defined for the wave instead of the priority defined on the mission types (see mission parameters).
|
Block number 2
| Used to move from the actual mode (by default) to the simulation mode, where all the data are deleted further to the processing. |
| Used to display the log (progress) of the program at the end of the processing. |
Close
Action icon