Merging on stock
This function launch in batch or in interactive manner the merging functionality of the stock. A simulation function is also possible.
Prerequisite
Refer to documentation Implementation
Screen management
The information of the original and destination objects to be merged are filled in on the dialog box.
Entry screen
Presentation
Movement code : compulsory keying in of a transfer type of movement code. The transfers generated by this function is the Merging with accumulation type of transfer.
Maxi nbr mvts/objects : expressed the number of movements to be carried out per stock objects. On the merging in input, the value is fixed to 2, meaning that an object to be merged can not be merge on more than 2 incomplete objects.
Maxi nbr mvts : expressed the total number of transfer movements to be implemented at the launching of the process.
Simulation : box to be ticked ; in simulation a summarized table of transfers that can be carried out is displayed.
Depositor : a limitation criteria for the objects to be merged.
Items : a limitation criteria for the objects to be merged
Ruptured objects only : if ticked, the process includes only the objects considered as ruptured. A ruptured object is an object whose CU quantity is less than the % of incomplete and the CU quantity of the item container of the stock object. If not ticked, all the stock objects not standard are included.
Occupation % has more priority than incomplete: if ticked, the process favors the locations less occupied wherein to choose the stock objects to be merged to the detriment of the quantity of the stock object. If not ticked, the object the most incomplete or those whose CU quantity the smallest are favored in relation to the occupation percentage of the locations.
Origin
Store : geographical criteria where to get the original objects to be merged..
Location : Address limitation criteria of the original objects to be merged.
Including the stores forbidden in output : include or not the external stores; generally this parameter is not ticked.
Note : the notion of origin here is linked to the stock objects that will be moved to be merged with the other (called the destination).
Destination
Store : geographical criteria where to put the destination objects merged.
Location : Address limitation criteria of the destination objects to be merged.
Including the stores forbidden in output : include or not the external stores; generally this parameter is not ticked.
Advanced selection Origin/Destination
Window to key in the different formula according to the necessity :
The pressing of the button launch the interactive process either in simulation or in creation.
According to the setting the reports and the labels can be generated.
Depending on the setting, the associated movements can be validated automatically; in this case an operator code could be demanded.
Close
Fields
The following fields are present on this tab :
Transfer
| 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. |
| Specifies the number of moves to be completed by stock object in order to form a complete object. |
| (Modifiable) value indicating the maximum number of transfer movements that the system can create for a transfer. |
| Used to move from the actual mode (by default) to the simulation mode, where all the data are deleted further to the processing. |
| Used to display the log (progress) of the program at the end of the processing. |
Selection
| 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. |
| Product code defined in the GEODE product table. |
|
|
| Tellsif the merging should take only thestock objects considered as incomplete or all the stock objects. |
| Tellsif the system should give priority to the locations that are least occupied orthe stock objects that are most incomplete. |
Source
| Code used to identify the store. This code is controlled in the store table. |
| Field used to specify the start address of the location address range. |
| Field used to specify the end address of the location address range. |
| If it is checked, the search of objects to be merged takes into account the stores prohibited on output. If it is not checked, only the stores authorized on output are taken into account. |
Destination
| Code used to identify the store. This code is controlled in the store table. |
| Field used to specify the start address of the location address range. |
| Field used to specify the end address of the location address range. |
| If it is checked, the search of objects to be merged takes into account the stores prohibited on output. If it is not checked, only the stores authorized on output are taken into account. |
Advanced selection
| Entry window of a formula to select the "original" stock objects to be merged. |
Advanced selection
| Entry window of a formula to select the "destination" stock objects to be merged. |
Close
Batch task
This function can be run in batch mode, but no dedicated standard task is delivered to run it.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Mvt code : Mandatory zone
The keying in of a movement code is mandatory
Mvt code : Unknown record
The movement code keyed in is unknown in the current site.
Mvt code : Mvt code forbidden
The movement code keyed in is not of the transfer type.
Maxi nbr mvts / object : Mandatory zone
The maximum number of movements by object should be different from 0.
Maxi nbr mvts : Mandatory zone
The maximum number of movements should be different from 0.
Maxi nbr mvts : Incorrect value (<X)
The maximum number of movements should be greater or equal to the maximum number of movements/object.
Depositor : Unknown record
The depositor keyed in is unknown in the current site.
Items : Unknown record
The item keyed in is unknown in the current site and depositor keyed in.
Store : Unknown record
The store keyed in is unknown in the current site..
Store : Type of store <> Principal
The store should be of principal type.
Locations : Format incorrect
The format of the location keyed in is different to that of the store.
Locations : Unknown record
The location is unknown for the store.
Locations : Picking location
The location keyed in should be of the reserve type.
Locations : incorrect value
The end location < the start location