Outputs > Waves > Waves 

This function is used to create, modify or delete a wave.

By creating a wave, you can regroup DOs with the same characteristics and launch them later on.

You can also use this function to process or only simulate the selected wave to be launched.
The wave contains an upgradeable status.

The DOs can be selected if they have the status 1-Pending 1st preparation or 2-Pending th preparation.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

When opening the function, only the waves that need to be processed are displayed in the selection panel. The screen also contains two sections that describe the characteristics of the selected wave.

To display the already processed waves (Status 5-Completed), press Selection, then All.

Creation of a wave

You need to create a wave whenever a DO needs to be sent for preparation.

Step 1. Click File > New, then assign the DOs to the wave. The operator needs to enter the DO no. in the Number column of the DO list section. They can also use a Memo code or the selection panel.

The selection panel contains a list of DOs to be prepared, displaying the DOs at status 1 or 2, regrouped by ascending date and time of provisional launch.

Step 2. Click Create to validate the action and create the wave. The selected DOs switch from status 1 or 2 to status 3-Selected for preparation.

Deleting a wave

You can delete a wave if its status is 1-Not validated.

Step 3. Click Delete to delete the wave. The DOs are unlinked from the wave and switched to their initial status (1 or 2). They become available for allocation to existing waves or waves to be created.

Modification of a wave

You can modify a wave by allocating or de-allocating DOs whenever the wave status is 1-Pending launch.

- To assign DOs to an existing wave, follow the same procedure as for the creation.

- To unlink DOs from an existing wave, go to the line to be de-allocated, use the Actions menu to delete the line. Then click Save.

Header

Presentation

The following information is displayed:

Number. This is the wave number.

Status. This is the wave status.

Flow merging. Flag specifying if the wave authorizes the merging of flows.

Launch date. Date and time of the wave launch.

Close

 

Fields

The following fields are present on this tab :

Numerical sequence assigned automatically by the system upon wave launching.

  • Merging of flows (field WAVFLC)

Used to select the DOs that are managed in flow total.

  • Auto launch (field AUTLNCFLG)

 

  • Launch date (field LNCDAT)

 

  • field LNCTIM

 

  • Status (field WAVSTA)

 

Close

 

Tab General

Presentation

This section displays the information calculated by the system during the wave creation:

Carrier. Carrier code and title.

Transport method. Transport method and title.

Round no. Round number of the DOs including in the wave.

The carrier, transport method and round no. are only entered if the wave is for a single carrier, transport method and round no.

Preparation / Request

No. of DOs. Number of DOs in the wave.

No. of lines. Number of lines in the wave.

No. of line shortages. Number of DO line shortages in the wave.

Weight. Total weight of the wave.

Volume. Total volume of the wave.

Movement no.

Reserve. Number of stock movements in the reserve locations.

Picking. Number of stock movements in the picking locations.

Replenishment. Number of stock movements of the replenishment type.

Transfer. Number of stock movements of the transfer type.

Cross-docking. Number of stock movements of the cross-docking type. Not available in this version.

Parcel no.

Dispatchable as is. Number of parcels dispatchable as is in the wave.

Constituted. Total number of parcels in the wave.

No. of POs

Reserve. Number of reserve POs in the wave.

Picking. Number of picking POs in the wave.

Mixed. Number of mixed POs in the wave.

No. of TOs. Number of TOs in the wave.

Close

 

Fields

The following fields are present on this tab :

Block number 1

Code used to identify a generic wave.

Code identifying the carrier. This code must be defined in the carrier table.

Usually, the transport mode corresponds to the notions of messaging, freight, express,... The transport mode is checked against the transport modes table.

Number assigned by the system and used to identify the round in a unique way within a site.

Preparation

  • DO no (field DLONBR)

 

  • field DLONBR2

 

  • Weight (field WEI)

 

  • field WEISYM

 

  • No. of lines (field DOLNBR)

 

  • field DOLNBR2

 

  • Volume (field VOL)

 

  • field VOLSYM

 

  • No. incompl. lines (field SSHNBR)

 

  • field SSHNBR2

 

Sort

Three-character code identifying the set of sort criteria applied to a wave or preparation area. This code is linked to a picking order from the wave or preparation area.


The Sort code can be entered from the following functions:

  • Generic wave
  • Wave
  • Preparation area
The Sort code displayed in a picking order can either come from the wave or from the related preparation area.

By default, the Sort code of the wave is the code of the associated generic wave.
The Sort code defined on a wave is automatically applied to all the picking orders originating from that wave.

Load

Activity whose load needs to be measured according to 1 to 3 units of measure.

  • Estimated load (field EXPLOD)

 

 

Directive missions

  • To block (field MSNLOK)

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.

SEEINFO This setup only concerns missions with a picking type (PKOMVT, PKOPRC and PKOSHP) and missions with a merging of flows transfer type (TRFMERG). All the other mission types will apply the setup of the missions.

  • Priority (field MSNPIO)

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).

SEEINFO This setup only concerns missions with a picking type (PKOMVT, PKOPRC and PKOSHP) and missions with a merging of flows transfer type (TRFMERG). All the other mission types will apply the setup of the missions.

No of movements

  • Reserve (field RSVMVTNBR)

 

  • Picking (field PICMVTNBR)

 

  • Reorder (field RPNMVTNBR)

 

  • Transfer (field TRFMVTNBR)

 

  • Cross docking (field CDKMVTNBR)

 

No. of parcels

  • Dispatchable in state (field ISPNBR)

 

  • Constituted (field NSPNBR)

 

PO no

  • Reserve (field RSVPKONBR)

 

  • Picking (field PICPKONBR)

 

  • Mixed (field MPONBR)

 

  • TO nr (field RPNNBR)

 

No SU

  • Dispatchable in state (field ISPNBRSHP)

 

  • Constituted (field NSPNBRSHP)

 

Close

 

Tab DO list

Presentation

This section lists the DOs assigned to the wave with their main characteristics.

Close

 

Fields

The following fields are present on this tab :

Grid

Numerical sequence automatically assigned by the system upon validation of the DO header. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a Delivery Order.

  • Reference (field REF)

 

 

 

  • Planned launch (field EXPLNC)

 

  • Planned delivery (field EXPDLV)

 

  • Urgent (field URG)

 

  • Priority (field PIR)

 

  • Partial delivery (field PTLPIK)

 

 

  • Company name (field DLVNAM0)

 

  • Postal code (field DLVPOS)

 

  • Area (field DLVARE)

 

 

 

 

  • No. of lines (field DOLNBR)

 

  • field WEI

 

  • field VOL

 

  • Status (field DOHSTA)

 

Close

 

Action icon

Delivery Order

 

Close

 

Reports

By default, the following reports are associated with this function :

 CHARGES : Preparation load

 ETIQREA : Replenishment label

 LISTCOL : Customer packing document

 OP : Pick Order

 REAPPRO : Transfers / Replenish

 RUPTURE : Shortage status

This can be changed using a different setup.

Specific Buttons

This button is used to:
- restrict the list of DOs to be prepared according to a maximum cumulated load criterion for a given loading station and a given unit.
- restrict the list of DOs to be prepared according to a maximum cumulated load criterion for a given loading station and a given unit.

- display the load of each DO and each set of DOs from the list of DOs to be shipped for a given loading station and a given unit, provided that the Display list option is checked.
For each DO in the picking list and based on a given order (severity, planned preparation date and time, DO reference):
   * Calculating the DO load for the entered loading station and unit
   * Totalling the load with the loads of already processed DOs
   * If the load limit is exceeded, the DO is not selected and the next DOs are not taken into account.
   * Otherwise, the DO is selected and the next DO is processed.

An abbreviation is displayed at the right bottom side of the screen when load limits apply.

You can predefine specific parameter (station, unit, maximum load) for each user, using specific Memo codes for the load limit, knowing that:
- Memos are common to the Wave management and Round management
- The values of the STD Memo code are suggested by default.

Specific actions

Functions/Launch

Use this function to launch the wave preparation.

Functions/Simulation

Use this function to simulate the wave preparation launch.

Functions/Log

Use this function to view the log files that exist for this wave.

Drill Down/SU

Use this function to go to the SUs inquiry screen.

Drill Down/Parcels

Use this function to go to the parcels inquiry screen.

Drill Down/POs

Use this function to go to the POs inquiry screen.

Drill Down/Transactions

Use this function to go to the movements inquiry screen.

Drill Down/Transfers/Replenishment

Use this function to go to the transfers and replenishment orders inquiry screen.

Drill Down/DO line shortages

Use this function to go to the DO line shortages inquiry screen.

Drill Down/Overview

Separator used in the Function menu.

Functions

Use this function to launch the load calculation for the selected wave via the load analysis module.

The load analysis function is based on the activity code LA0 for a wave that has not been launched, on the activity code LA2 for a wave that has been launched.

The analysis applies to:
- The list of active DOs (status 3 to 8) for the wave.
If a SU is linked to several DOs from the wave, the load considered for each station corresponds to the average calculated loads for each pair (SU/DO).
- The list of replenishment movements in progress for the wave.
- The list of transfer movements in progress for the wave in flow merging.

Further to a load analysis request:
• a new analysis is created with the following characteristics:
- Flag to maintain = "no"
- Template (for info.):
   • the template associated to the triplet (function, current site, current depositor) for a single-depositor function
   ▪ By default, or for a multi-depositor function, the template associated to the triplet (function, current site, depositor set to "blank").
   ▪ By default, the template associated to the triplet (function, site set to "blank", depositor set to "blank")
   ▪ By default, the template is set to "blank".
• The calculation for the analysis is launched.
• The operator accesses the load display screens from which it can also access the information related to the analysis (description and flag "To be kept") and request the printing of the analysis results.

Functions/Wave load

If a SU is linked to several DOs from the wave, the load considered for each station corresponds to the average calculated loads for each pair (SU/DO).

You can create, calculate and access a load analysis for the list of the non-selected DOs (status <3).

The analysis considers any filter applied to the selection list using the Sort option or advanced selections.

Functions/To be prepared DO load

Functions/To be prepared DO load

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Modification impossible.

The progress status of the wave does not allow any modification.

Tables used

SEEREFERTTO Refer to documentation Implementation