Travel Sequence
This table is used to match the physical aisles constituting a store and the travel sequences used in pickings, replenishments and/or inventoty countings.
The configuration of this table makes it possible to optimize operator movements upon actual execution of the operations.
Depending on these 3 types of movements, the sortings of movements inside a logical entity may be different; when it is not entered, the sorting is carried out by store/address.
Prerequisite
Refer to documentation Implementation
Screen management
After selecting a store, the travel sequences are entered in an already filled-in grid.
Entry screen
Presentation
The store can be entered or selected: if they exist, the physical aisle are displayed.
The movement type defines the frame in whiche the travel sequences are used.
- Movements with th type 'picking': sorting of picking orders and of movements in a parcel.
- Movements with the type replenishment: sorting of replenishment lists.
- Movements with the type inventory: sorting of inventory counting.
Travel sequences
Aisle.The aisle is entered in relation to the address structure of the store and to the locations actually created.
Parity. This parameter indicates the parity linked to the aisle. This field can be accessed by the operator only if the addresses of the store have the type « comb ».
Odd: Odd rows in the aisle code.
Even: Even rows in the aisle code.
A row is even if the last character of the row is even; a character is even if its ASCII value is even. For numbers between 0 and 9, corresponding ASCII values go from 48 to 57. For letters from A to Z, corresponding ASCII values go from 65 to 90. The aisles with 0, 2, 4, ..., 8 or B, D, F or Z as last character are even.
Sequence. This field corresponds to the travel sequence, it enables movements to be sorted within a PO. Two types of travel are defined:
Mono face travel: each aisle must have a unique travel sequence (see diagramm).
Multi face travel: the aisles "picked" at the same time must have the same travel sequence.
Level / Row. This field defines the sequence type inside a travel sequence. Sorting carried out by level then by row.
Row / Level. This field defines the sequence type inside a travel sequence. Sorting carried out by row then by level.
Row way.This parameter is used to force an aisle travel direction, either in an increasing order or in a decreasing or alternate row order.
Level way.This parameter is used to force an aisle travel direction, either in an increasing order or in a decreasing or alternate level way.
Note: if the way is alternate, the system alternates increasing order and decreasing order each second row.
Diagram of travel sequences: mono face/multi face picking
Diagram: mono face picking, level row order
Mono face picking, row level order:
Mono/multi face picking, alternate order:
Mono/multi face picking, forced order:
Close
Fields
The following fields are present on this tab :
Block number 1
| Code used to identify the store. This code is controlled in the store table. |
| This parameter defines the framework within which the travel sequences are used, either as a sampling-type movement (sort of the sampling orders, of movements in a parcel) or a replenishment-type movement (sort of the replenishment lists) or inventory-type movement (sort of the stock counts). |
Grid Travel Sequences
|
|
|
|
| This field corresponds to the travel sequence, it enables movements to be sorted within a PO. Two types of travel are defined: single-face travel (each aisle must have a unique travel sequence) and multi-face travel (the aisles, prepared at the same time, must have the same travel sequence). |
| This parameter defines the travel type inside a travel sequence. The sorting is carried out either by level, then by row, or by row, then by level. |
| This parameter is used to force an aisle travel direction, either in an increasing order or in a decreasing or alternate row order. |
| This parameter is used to force an aisle travel direction, either in an increasing order or in a decreasing or alternate level order. |
Block number 3
Close
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Store field error, mandatory field
The store MUST be entered.
Store error, record does not exist.
An attempt has been made to enter a non-existent Store.
Store field error, Store without locations
The locations have not been created for this store.