Cross-Docking PO
This screen is used to launch or close a Cross-Docking PO (in other words, all the requirements of the corresponding DO).
Prerequisite
Refer to documentation Implementation
Screen management
When a Cross-Docking PO is launched, the corresponding requirements are launched on preparation.
When launching a Cross-Docking PO, the input pending movements into the Cross-Docking store are considered as being available stock unlike a wave launch where input pending movements (into the Cross-Docking store) are considered as being available stock or not, depending on the setup of the output configuration.
Further to the launch of the Cross-Docking PO, if there are still shortages, the missing quantities are kept in the Cross-Docking PO. On the other hand, for the other quantities (those that are available), Preparation Orders are prepared.
Closing a Cross-Docking PO is equivalent to cancelling the preparation of the PO quantities. Consequently if the DO was fully on Cross-Docking PO, closing the latter would mean closing the DO.
Entry screen
Fields
The following fields are present on this tab :
Grid Delivery order
| No help linked to this field. |
|
|
| Numerical sequence assigned automatically by the system upon wave launching. |
| 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. |
| Document reference. |
| The service priority is used to define an order of priority for the processing of the delivery orders. |
| Used to subsequently create urgent DO waves to be handled in priority. |
| Specifies if all the DO requirements are covered. The requirement on a DO line is considered to be covered when there is some stock (at least 1 CU) available for the product in the Cross-Docking store. |
| Delivery Order status. |
| 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. |
| Provisional date and time of the wave launching. |
| Provisional DO delivery date and time. |
| Specifies if the customer accepts to be delivered in part; there are three possibilities, either yes (the customer accepts, irrespective of the requested quantity), or by line (the customer accepts a partial delivery provided the whole line is delivered), or no, (the customer does not accept a partial delivery). |
| Code of the ship-to customer who must be defined in the Customer table. |
| Company name of the ship-to customer. |
| Postal code of the ship-to customer. |
| Delivery field of the ship-to customer. |
Grid Lines
|
|
| Product code defined in the GEODE product table. |
| Specifies if the DO line requirements is covered. The requirement on a DO line is considered to be covered when there is some stock (at least 1 CU) available for the product in the Cross-Docking store. |
| Specifies the quantity in CUs of the requirement of the DO line. |
| Requested lot number. |
| Requested reservation number. |
| Concerning a DO line holding a reservation number, the system only accepts to issue quantities having the same number. In case of shortage on a reservation number, the balance is never taken from non-reserved stock. |
| Requested support number. |
| It is used to manage the quality-related differences at stock object level: expiry, reconditioning, etc. |
Block number 3
| 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. |
Close
Action icon
Specific Buttons
The "Close requirement" button is used to close the requirements for the selected DOs. |
The "Log file" button is used to display how the process has gone. |
The "Criteria" button is used to select the Cross-Docking POs thanks to criteria that concern the DO like, for instance, the DO number, date ranges, wave no. etc. |