Automatic replen.
This function allows the generation of replenishment orders of a group picking locations according to two types of preventive replenishment, the replenishment on threshold limit and the systematic..
A simulation can be requested.
Screen management
The screen is made up of a single tab.
Entry screen
Presentation
The screen allows to set-up the automatic generation of the replenishments..
The zones to be filled in are :
Store : compulsory keying in of store to be replenished; only the picking locations of the store are replenished.
Location : key in of a bracket of locations to be replenished or of one location.
Replenishment type : Replenishment on threshold (default value) or systematic replenishment.
The first is triggered when the stock of the picking location is strictly inferior to the threshold limit defined for the location to be replenished.
The stock of the picking location is defined as the total stock object of the location with or without pending input – pending output (depending on function of the parameter ‘Split replenishment objects’ of the stock configurations).
The second is systematically triggered whatever the available stock when the location is not full.
Transfer movement code : it is the movement code of the Transfer type used to carry out the replenishment.
The box to be ticked Simulation indicates if it is a simulation of the replenishment or if the system should really launch the replenishment.
A location is replenished if :
- the location is not blocked in input, neither in output, nor being inventoried,
- the item associated to the location is not being inventoried,
- the store is authorized in output.
The stock objects selected to implement the replenishment are chosen according to the output mode of the item.
The following controls are defined :
- the location <> the keyed in picking location
- the location is not blocked in output
- the location is not being inventoried
- the store is authorized in output
- the store type <> Splitting
- les dates SBD, UBD, SbD are nil and are not set on the item file or >= date of the day
- the detention date < date of the day or not set on the item file
- the reservation n°, and the stock nature are not keyed in
- the container is >= to the container of the location
- the palletisation plan includes the container of the location
- the available quantity (object) > 0
The system will split the stock object to do the replenishment if its quantity is greater than the available space in the picking location and if it is the first stock object selected.
A click on the button creates the replenishment. A replenishment label per selected object and also a replenishment list can be generated if the setting on the stock configuration of the current depositor allows it..
Depending on the stock configuration, the generated replenishment will be validated through Unitary validation or through the Mass validation , or it will be validated automatically.
Close
Fields
The following fields are present on this tab :
| Code used to identify the store. This code is controlled in the store table. |
| Start address of the range of locations to be replenished. |
| End address of the range of locations to be replenished. |
| Replenishment on threshold: the replenishment is triggered if the stock of the picking location is strictly lower than the threshold defined for the location to be replesnished. The stock of the picking location is defined as being the total of the stock object of the location, with or without pending input movments. Systematic replenishment: the replenishment is systematically triggered, irrespective of the available stock, if the picking location is not full. |
| 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. |
| Used to move from the actual mode (by default) to the simulation mode, where all the data are deleted further to the processing. |
Close
Batch task
This function can be run in batch mode. The standard task REAAUT is provided for that purpose.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Store field error, mandatory field
The store should be keyed in.
Store error, data unknown.
Store keyed in is unknown.
Transfer movement code error, mandatory field.
A movement code of the « transfer » type should be keyed in.
Transfer movement code error, Unknown record.
The movement code keyed in is unknown in the current site.
Transfer movement code error, Mvt code forbidden.
The movement code keyed in should be of the transfer type..