Mass transfers
This screen allows to carry out the mass transfers of stocks after having selected the stock objects.
The validation of the transfer movement are carried out by another function, Transfer/Replenishment Validations.
At its creation, the movement creates a pending output from its original location, and a pending input in its destination location. It should be validated to delete the pendings.
Therefore a transfer movement has a status.
This function allows the implementation of a « normal » and « whole container » type of transfer. These same transfers can be carried out in a unitary way in the transfer management function.
Available from version G2
Prerequisite
Refer to documentation Implementation
Screen management
This functionality can take place in several phases :
1°)Key in the selection research criteria of the stock objects
2°)Selection of the stock objects
3°)Keying in of the destination location or the launching of addressing
4°)Display of anomalies if there exist.
Header
Presentation
This tab gives the following characteristics of the transfer :
Movement code : The movement code is a mandatory field, the movement type keyed in should be defined on the movement codes table as a movement of transfer type.
Whole container transfer :if ticked, the stock objects linked to the « master » objects are also transferred ; if not, only the « master » object is transferred and therefore it becomes a « normal » object
Date :date and time of transfer
Adjustment : a stock nature and a reservation code can be keyed in ; all the transfer movements carried out will therefore have these characteristics, during the validation of the transfer, a qualitative adjustment movement will be automatically generated by the system.
Container :a transfer container can be keyed in. In this case, the transfer movements will be generated with this container code that could be different from that of the stock object.
Destination : a transfer store can be keyed in and also a storing address..
Close
Fields
The following fields are present on this tab :
Block number 1
| 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. |
| If the flag is checked, the stock objects linked to the master objects are also transferred. Otherwise, only the master object gets transferred and it then becomes a normal object. |
| Creation date of the transaction. |
| Creation hour of the transaction. |
Adjustment
| Checkbox used to specify the reset to zero of the stock nature, or the entry of a specific nature during transfer. |
It is used to manage the quality-related differences at stock object level: expiry, reconditioning, etc. |
| Checkbox in order to specify the reset to zero or the entry of the reservation code during the transfer. |
| Reservation number(s) of the stock object(s). |
| The term Container encompasses the type and code of the container. |
Destination
| Destinationstore of the stock object(s). |
| Physicaldestination address of the stock object(s). |
|
|
|
|
|
|
Close
Tab Stock objects
Presentation
This tab lists the stock objects of the site with the available quantity.
Possibility to select one by one the stock objects to be transferred by ticking the box ‘Sel’ or in mass selection by click right on the mouse and ‘Select all’
After the selection of the records of the stock to be transferred, press on the button .
Close
Fields
The following fields are present on this tab :
Grid
|
|
| No help linked to this field. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Close
Action icon
Tab Link stock objects
Presentation
This tab lists for each « master » stock object, the stock objects linked to it .
In the case of whole container transfer , this allows the acknowledging of the linked objects that will be transferred at the same as the master objects.
Close
Fields
The following fields are present on this tab :
Grid
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Close
Action icon
Other conditions
Coherence controls are implemented between the entering item and the storage type of the location ; they are the same controlsas that of the unitary transfer.
Depending on the setting of the current site, the transfer movement can be validated automatically at its generation. In this case, the keying in of location control code is inhibited whatever the setting.
Two printouts can be created at the time of the creation of the transfer movement ; the printing of theses printouts can be set on the site table of the current site
Transfer/Replenishment list Transfer/Replenishment label
Menu Bar
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
No record selected
The keyed in criteria do not allow the selection of stock objects.
Movement code: Mandatory field
The keying in of movement code is mandatory.
Movement code: unknown record
The keyed in movement code is unknown for this depositor.
Movement code: Forbidden mvt code
The movement code keyed in is not transfer type..
Stock nature : unknown record
The stock nature keyed in is unknown in the current site.
Containers : unknown record
The container keyed in is unknown in the current site.
Store : unknown data
The keyed in store is unknown
Address : Incorrect format
The keyed in address format does not corresponds to that of the store.
Address : unknown record
The keyed in location is unknown in the selected store
Address : Picking location
The keyed in location should be reserve type.
Address : Location blocked in input
The location is blocked in input.
Address : Location blocked for inventory
The location is being inventoried.
Location is full
The available space of the location cannot accept the creation of a stock object.