Range allocation
Allows to associate each entity generator of workload (EI, EI Line, DO, DO line, parcel, SU, and movement) to a load range, meaning to a calculation rules of the workload of the forecasted task still to be realized.
Access to the function is conditioned by :
- the activity code LA0 (EI, EI Line, DO, DO line ranges)
- the activity code LA2 (parcel, SU, and movement ranges)
Prerequisite
Refer to documentation Implementation
Screen management
The screen is made up of a simple table
Entry screen
Presentation
Definition for each entity (Item, EI, EI Line, DO, DO line, parcel, SU, and movement) of the allocation criteria of a range.
The triplet (site, entity n°, sequence n°) is unique
The sequence n° is compulsory and is recalculated systematically by applying a step of 10 to allow later insertions.
The sequence n° is important in the research of the range.
Algorithm of range determination associated to an entity :
For a given entity, the lines of the table will be considered on the order of the sequences.
If each keyed in criteria of the line has a value identical to the entity, the range of the entity is found if not the next line is considered.
Allocation criteria of the range for an item :
·Depositor
· Family (only if the depositor criteria is keyed in)
· Sub-family (only if the depositor criteria is keyed in)
· Group (only if the depositor criteria is keyed in)
· Sub-group (only if the depositor criteria is keyed in)
· Origin (only if the depositor criteria is keyed in)
· Input mode (only if the depositor criteria is keyed in)
· Output mode (only if the depositor criteria is keyed in)
Allocation criteria of the range for an EI :
· Depositor
· Receipt mode (only if the depositor criteria is keyed in)
· Movement code of the EI header
Allocation criteria of the range for the EI line :
· Depositor
· Receipt mode of the EI (only if the depositor criteria is keyed in)
· Origin of the EI line (only if the depositor criteria is keyed in)
· Movement code of the EI line
· Return indicator of the EI line (Possible values : « yes » or « no »)
· Item load range (determined thru this same table the setting of the item of the EI line)
Allocation criteria of the range for a DO :
· Depositor
· DO status
Values contained between « 1 » and « 8 » because we are only interested on active DO.
If the activity code ACGX2 is not active, we can only fill in the status « 1 », « 2 » or « 3 ».
· DO Preparation mode (only if the depositor criteria is keyed in)
· Palletization indicator (Possible values : « yes » or « no »)
· Loading indicator (Possible values : « yes » or « no »)
· Delivery confirmation indicator (Possible values : « yes » or « no »)
· Movement code of the DO
Allocation criteria of the range for a DO line :
· All the available criteria of the DO header
· DO line status
Values contained between « 1 » and « 8 » because we are only interested on active DO.
If the activity code ACGX2 is not active, we can only fill in the status inferior to « 4 ».
· DO line type (Possible values : item, kit, component)
· Item load range (determined thru this same table the setting of the item of the DO line)
Allocation criteria of the range for the parcel :
· Depositor
· Parcel status.
Values contained between « 4 » and « 8 » because we are only interested on active parcels
·DO Preparation mode (only if the depositor criteria is keyed in)
·DO Palletization indicator (Possible values : « yes » or « no »)
·DO Loading indicator (Possible values : « yes » or « no »)
·DO Delivery confirmation indicator (Possible values : « yes » or « no »)
· « Palletized parcel » indicator (Possible values : « yes » or « no »)
This indicator cannot have the value of « yes », if the palletization indicator has the value « no »
· Container level for a parcel dispatchable in state (Possible values : level 1, 2, 3, 4 or 5)
· Parcel range
· Parcel type
· Preparation area
Allocation criteria of the range for the SU :
· Depositor
· SU status
Values contained between « 6 » et « 8 » because we are only interested on active SU
·DO Preparation mode (only if the depositor criteria is keyed in)
·DO Palletization indicator (Possible values : « yes » or « non »)
·DO Delivery confirmation indicator (Possible values : « yes » or « non »)
· SU Type
Allocation criteria of the range for a movement :
· Depositor
· Movement type.
The possible movement types are : Input, Transfer (« pick » part), transfer (« deposits » part), Replenishment (« pick » part), Replenishment (« deposit » part), output, Transfer in preparation with merging of flows (« pick » part), Transfer in preparation with merging of flows (« deposit » part)
· Movement status
We are interested, in all cases, only to pending movements (Values contained between « 1 » and « 4 ».
Zone that can be filled in only if the movement « type » was keyed in.
·DO Preparation mode (only if the depositor criteria is keyed in and for an « Output » movement « type »)
· Indicator « packed movement » (Possible values : « yes » or « no »)
Zone that can be filled in only for an « Output » movement « type ».
Allows to consider only movements with/without parcels.
· Type of storage of the location
· Store
· Movement level
Þ For a deposit (Input, transfer (« deposits » part), Replenishment (« deposit » part), Transfer in preparation with merging of flows (« deposit ») the level corresponds to that of the generated object.
Þ For a pick (Output, Transfer (« pick » part), Replenishment (« pick » part), Transfer in preparation with merging of flows (« pick » part), the level corresponds normally to that of the object if picked in totality, or if not, to the first superior level whose number of CU is a divisor of that of the movement.
· Movement code
Zone that can be filled in only if a movement « type » was keyed in.
· Item load range (determined thru this same table the setting of the item of the movement)
The load range assigned should be defined for the considered entity type thru the load ranges table and, except for the « item » ranges, should have been associated to workload coefficients thru the load coefficient table.
If the ‘load range’ is not filled in, that means that there will be no calculation of the workload for the entities matching the defined criteria.
Remark :
The load analysis can only be launched if each considered entity was explicitly associated, thru this table, to a range (« real » or « blank »).
It is therefore recommended, for each type of entity, to add systematically a last line without any selection criteria, associated to « blank » range.
Close
Fields
The following fields are present on this tab :
Block number 1
| Table where each recording makes it possible to specify a work load based on the value of some of its fields. |
Grid Assignment
| Number making it possible to use the rules defined in this screen by order of priority. |
| Code representing the depositor. In logistics terms, the concept of depositor makes it possible to process separate flows or traffics within the same site. It encompasses the concept of order-issuing customer for the service providers. After the site, the depositor is the second access key to the Product, Input and Delivery Order files. For the location, the depositor code is entered if the location is allocated to the depositor or to the product, and if the location is single-depositor or single-product or if it is not empty. |
| Code of the receipt mode. A number of management rules relating to the expected input is associated with this code. |
| The family enables products to be classified on the basis of a criterion chosen by the user. It features the entity that defines the packing rules at product level. |
| The Sub-family enables products to be classified on the basis of a criterion chosen by the user. |
| The Group enables products to be classified on the basis of a criterion chosen by the user. |
| The Sub-Grou enables products to be classified on the basis of a criterion chosen by the user. |
| L’The origin’ enables items to be classified on the basis of a criterion chosen by the user. It is generally used to define or further determine the origin (geographical or other) of the products managed by the system. |
| This code represents the input mode. This input mode gathers all the management rules (linked to the product) implemented during an input addressing phase. This code is controlled in the input mode table. |
| Code of the output mode. The output mode determines the rules applied to the products when searching for output locations. |
| No help linked to this field. |
|
|
| Code representing the preparation mode. The preparation mode regroups all the management rules linked to each DO. It makes it possible to specify the processing mode of said DO upon preparation launching. |
|
|
|
|
|
|
|
|
| The storage type defines the management characteristics of a group of locations. These management rules are implemented during an addressing phase on input. |
| Code used to identify the store. This code is controlled in the store table. |
|
|
| Code of the parcel range. The range forms the main access key to the definition of the parcels themselves. It is used, for specific product groups or in the case of specific flows (export, etc.) to indicate the preferred packing type that will be selected. |
| Code of the parcel type. The type is used to define, for a specific parcel range, 1 to n parcel dimensions. |
| Code of the preparation area, checked against the preparation area table. The notion of Preparation area is used when splitting the Picking Orders. |
| Type of SU on which the parcel must be palletized. |
| The movement code is used to make the distinction between movements of the same type.
The movement code is checked against the movement code table. |
|
|
|
|
|
|
|
|
|
|
| No help linked to this field. |
|
|
|
|
| All the characteristics of the recording of an entity to which a unitary work load can be attributed. |
|
|
| All the characteristics of the recording of an entity to which a unitary work load can be attributed. |
Close
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Error zones « Sequence », compulsory zone
The keying in of the zone « sequence » is compulsory
Error zones « Sequence », Code exist already on line X
For an entity, the sequence n° is unique
Filter intercepted by a previous sequence (line N° X)
There exist already a line with the keyed in criteria less restrictive (or similar) and with a smaller sequence n°
Filter intercepted by a later sequence (line N° X)
There exist already a line with the keyed in criteria less restrictive (or similar) and with a higher sequence n°
Error zones « Depositor », Unknown record
The depositor keyed in should exist on the table of depositors for the current site
Error zones « Family », Unknown record
The family keyed in should exist on the table of families for the current site and the depositor keyed in.
Error zones « Sub-family », Unknown record
The sub-family keyed in should exist on the table of sub-families for the current site and the depositor keyed in.
Error zones « Group », Unknown record
The group keyed in should exist on the table of groups for the current site and the depositor keyed in.
Error zones « Sub-Group », Unknown record
The sub-group keyed in should exist on the table of sub-groups for the current site and the depositor keyed in
Error zones « Origin », Unknown record
The origin keyed in should exist on the table of origins for the current site and the depositor keyed in
Error zones « Input mode », Unknown record
The input mode keyed in should exist on the table of input modes for the current site and the depositor keyed in
Error zones « Output mode », Unknown record
The output mode keyed in should exist on the table of output modes for the current site and the depositor keyed in
Error zones « Load range », X YYYY : Unknown record
The load range keyed in should exist on the table of load ranges pour le site courant and should be associated to the entity processed.
Error zones « Load range », Range without load calculation
The load range keyed in is not associated to load coefficients.
Error zones « Receipt mode », Unknown record
The receipt mode keyed in should exist on the table of receipt modes for the current site and the depositor keyed in
Error zones « Mvt code », Unknown record
The movement code keyed in should exist on the table of movement codes for the current site
Error zones « Mvt code », XX : Mvt code forbidden
For the EI, the EI lines and the movements of the type « input », the movement code keyed in should be of the input type.
For the DO, the DO lines and the movements of the type « output », the movement code keyed in should be of the output type.
For the movements of the type « transfer pick », « transfer deposit », « replenish pick », « replenish deposit », « MF pick », « MF deposit », the movement code keyed in should be of the transfer type
Error zones « Item range », Load ranges : 1 XXX, Unknown record
The load range keyed in should exist on the table of load ranges for the current site and should be associated to an entity of the type « item »
Error zones « Preparation mode », Unknown record
The preparation mode keyed in should exist on the table of preparation modes for the current site and the depositor keyed in
Error zones « Parcel range », Unknown record
The parcel range keyed in should exist on the table of parcel ranges for the current site
Error zones « Parcel type », Unknown record
The parcel type keyed in should exist on the table of parcel types for the current site
Error zones « Preparation area », Unknown record
The preparation area keyed in should exist on the table of preparation zones for the current site
Error zones « Type UM », Unknown record
The SU type keyed in should exist on the table of SU types for the current site
Error zones « Storage type», Unknown record
The storage type keyed in should exist on the table of storage types for the current site
Error zones « Store », Unknown record
The store keyed in should exist on the table of stores for the current site