Output movements
This screen is used to display an output movement.
Prerequisite
Refer to documentation Implementation
Screen management
A movement no. is selected and the system displays its characteristics:
DO data. Number and status of the involved DO.
DO line data. Number, product and status of the associated DO line.
Movement data. Number and status of the output movement.
Pending transfer: if it is activated, this means that the DO to which the movement is linked is itself "pending transfer", i.e. it has been shipped to another site. On this site, the final shipment to the ship-to customer has no taken place yet.
Destination site: assigned if the flag "pending transfer" is activated. Specifies the site to which the movement has been shipped.
General tab. General data on the movement (Quantities, Dates, Lot, reservation and support numbers)
Management tab. Data on the addressing, preparation, validation, packing and shipping.
RemarksAn output movement is always associated with a single DO line.
The output movements are created by the system upon DO wave launching.
An output movement represents the smallest entity of a picking operation.
The output movements contain a status, they cannot be modified directly but their statuses and characteristics change with the DO processing steps.
Header
Fields
The following fields are present on this tab :
DO
| Numerical sequence automatically assigned by the system upon validation of the DO header. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a Delivery Order. |
|
|
|
|
Line
| Line number (numerical sequence automatically assigned by the system upon creation of the DO). |
|
|
| Product code defined in the GEODE product table. |
|
|
|
|
Movement
| Numerical sequence automatically assigned by the system to the movement. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a movement. |
| Specifies the movement type. If it is triggered as "Pending transfer", this means that the movement has been shipped, via an "inter-site" round, to another site. On this site, the final shipment to the ship-to customer has no taken place yet. |
| Destination site of the movement "pending transfer". |
| Movement status. |
Close
Tab General
Fields
The following fields are present on this tab :
Quantities
| Container of the stock object. |
| Stock object quantity. |
| The homogeneous container of a stock object is defined as the first container of a level other than level 1 (the pallet) whose CU stock quantity is a multiple. |
| Quantity expressed in the homogeneous container. |
| The term Container encompasses the type and code of the container. |
| Quantity expressed in container type and code of the line. |
| Quantity of the stock object expressed in CU |
|
|
|
|
| Number of necessary components to form a compound product. |
|
|
|
|
Dates
| Production date corresponding to the end of the item production cycle. |
| Detention date. This date corresponds to the instant before which the stock object is unavailable for an output movement. (for instance, quarantine). |
| Sale-by Date (SbD). The SbD is generally used as FIFO date for food products. |
| Best Before Date (BBD). This date is also called Optimum Use By Date. It is usually mentioned on the packaging of food or pharmaceutical products. |
| Use-by date (SBD). The UBD makes it possible to limit the circulation of a product in time: - for instance, within the framework of a commercial operation (discount), - or because of its expiry date. |
| The FIFO date can determine the stock removal order of the products (depending on the setup) when an order picking is launched. This date is used to ensure that some operations like merging are possible. |
Characteristics
| 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. |
| L’The origin’ enables items to be classified on the basis of a criterion chosen by the user. It is generally used to define or further determine the origin (geographical or other) of the products managed by the system. |
| It is used to manage the quality-related differences at stock object level: expiry, reconditioning, etc. |
| Code representing the preparation mode. The preparation mode regroups all the management rules linked to each DO. It makes it possible to specify the processing mode of said DO upon preparation launching. |
Numerals/numbers
| Requested lot number. |
| Requested reservation number. |
| Requested support number. |
Close
Tab Controls
Fields
The following fields are present on this tab :
Addressing
| Identifier created by GEODE upon creation of the stock object. |
| Code used to identify the store. This code is controlled in the store table. |
| Physical storage address of the stock object. |
| The location type determines whether the locations are of the reserve type (the allocation and vacating of the locations are carried out in dynamic mode) or of the picking type (the locations are assigned to a container for the Depositor/Product pair). |
Packing
| Parcel number (sequence automatically generated by the sytem upon parcel creation). |
| Parcel numbering internal to the DO. |
|
|
|
|
Preparation
| Numerical sequence assigned automatically by the system upon wave launching. |
| Preparation order number (sequence automatically assigned by the system). |
| Date of the wave launch. |
| Time of the wave launch. |
| Movement sorting field (internal to GX). |
Shipment
|
|
| Number assigned by the system and used to identify the round in a unique way within a site. |
| Delivery Note number. |
Validation
| Movement validation date. |
| Movement validation time. |
| Description of the operator code having validated the movement, if the configuration set-up requires it. |
Close