Refer to documentation Implementation
The keying in is carried out in three parties :
- The 1st presents the movement code to be used for the transfer, the transfer type to be implemented (normal or whole container) then a window wherein one can write the request allowing the selection of the objects to be transferred
- The 2nd presents the elements of the selected stock objects to be transferred (stock nature and reservation n°) and the container of the transfer.
- The 3rd presents the address of destination of the transfer.
Presentation
The movement code is a compulsory field and the movement type keyed in should be defined on the movement types table as a transfer movement type..
If the box ‘Whole container transfer’ is ticked, the stock objects linked to the ‘master’ object are also transferred; if not, only the ‘master’ object is transferred and it becomes a « normal » object.
A stock nature and a reservation code can also be keyed in.
All carried out transfer movements will then have these characteristics and during the validation of the transfers, a qualitative adjustment movement will be generated automatically by the system.
A transfer store and address can be keyed in and also a container of the transfer.
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. |
| In this field, enter a formula grouping the stock objects to be selected. |
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
After the launching of the process through the button, coherence controls are implemented between the entering item and the storage type of the destination location.
It is the samecontrol as that of the unitary transfers and mass transfers function.
After the processing, the display of the anomalies allows the view of the errors generated during the creation of transfers.
Only the stock objects without pending movements can be transferred in mass.
Two elements can be created at the moment of the creation of the transfer movement.
The printing of the reports are set-up on the site table for the current site :
Transfer/Replenishment list.
Transfer/Replenishment label.
This function can be run in batch mode. The standard task TRMAUT is provided for that purpose.
In addition to the generic error messages, the following messages can appear during the entry :
Movement code : Compulsory field
The keying in of a movement code is compulsory .
Movement code: unknown record
The movement code keyed in is unknown for this depositor.
Movement code : E01 forbidden movement code
The movement code keyed in should be a transfer type.
Stock nature : unknown record
The keyed in stock nature is unknown for the current site.
Container : unknown record
The keyed in container is unknown for the current site.
Store : unknown record
The keyed in store is unknown for the current site.
Incorrect format
The keyed in address format does not correspond to that of the store.
Emplacement : unknown record
The location keyed in is not found on the selected store.
Picking location
The keyed in destination location should be of reserve type .
Forbidden movement : The location is blocked in input.
The location is blocked in input.
Forbidden movement : The location is blocked by an inventory.
The location is being inventoried. .
The location is full
The available space of the location cannot receive the creation of the stock object.