Refer to documentation Implementation
The screen is made up of a single tab
Presentation
The process can be triggered :
for all the containers of all items of all the depositors of all the sites
for all the containers of all items of all the depositors of a particular site
for all the containers of all items of a particular depositor
for all the containers of a particular item
for a particular container of an item
Close
Fields
The following fields are present on this tab :
| Code of the logistics site. |
| 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. |
| The term Container encompasses the type and code of the container. |
|   |
Close
This function can be run in batch mode. The standard task OFRUPD is provided for that purpose.
In addition to the generic error messages, the following messages can appear during the entry :
Zone ‘Site’, Unknown data
The value keyed in does not exist on the sites table
Zone ‘Depositor’, Unknown data
The value keyed in does not exist on the depositors table of the site being processed.
Zone ‘Item’, Unknown data
The value keyed in does not exist on the items table of the site and depositor being processed
Zone ‘Item container, Unknown data
The value keyed in does not exist on the containers table of the item being processed.