Refer to documentation Implementation
The screen is sub-divided into:
The assembling declaration procedure is sub-divided into 3 steps:
The operator enters the information of the ‘quantity’ block (container no., container, etc.). The quantity for the kit to manufacture is indicated in the “Number PAC” field.
This step consists in checking the component lines and entering the quantity to be assembled ("Number PAC" field). This operation can be done either manually or automatically using the "Auto" button.
Whenever a line is checked, the system automatically transfers the entered qty to the "Total DU" field of the corresponding component line of the "Kit/Component" tab.
Based on the selected component quantities and the requested kit quantity, the declaration can take the following statuses:
Note: The "Save" button is used to save the declaration progress status.
When all the components have been selected and the declaration has the status "6-Compliant", the operator can then validate it.
Upon declaration validation and after possibly entering an operator code (based on the configuration at stock configuration level), the system:
The kit disassembling declaration procedure is sub-divided into 3 steps:
The operator enters the information of the ‘quantity’ block (container no., container, etc.). The quantity of the kit is indicated in the “Number PAC” field.
This step consists in checking the component lines and entering the quantity to be created ("Number PAC" field).
Whenever a line is checked, the system automatically transfers the entered qty to the "Total DU" field of the corresponding component line of the "Kit/Component" tab.
Note: The "Save" button is used to save the declaration progress status.
When all the components have been selected and the declaration has the status "6-Compliant", the operator can then validate it.
Upon declaration validation and after possibly entering an operator code (based on the configuration at stock configuration level), the system:
Fields
The following fields are present on this tab :
|   |
|   |
|   |
|   |
|   |
|   |
|   |
Close
Presentation
This tab is used to list all the "To consume" movements linked to the AO line.
Close
Fields
The following fields are present on this tab :
| No help linked to this field. |
|   |
| Quantity to be validated or cancelled expressed in CU. |
|   |
|   |
| Homogeneous container. |
| Quantity to be validated or cancelled expressed in homogeneous containers. |
|   |
|   |
| Requested lot number. |
|   |
| Requested support number. |
Close
Presentation
This tab displays the involved AO kit line with the component quantities selected during the declaration procedure. It is also used to check the consistency of the kit proportions as well as the kit quantity to be produced (the "Total DU" box is displayed in red in case of inconsistency).
If the component quantities do not comply with the kit composition coefficients, the "Total DU" box is displayed in red for the involved component lines.
Based on the quantity of selected components, the system determines the number of kits that can be declared ("Total DU" field of the first Kit line). If this number is different from the kit quantity to be produced defined in the "Stock object" tab ("Number PAC" field), then the "Total DU" box is displayed in red.
Close
Fields
The following fields are present on this tab :
Block number 1
|   |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
Close
Presentation
This tab is used to define the characteristics of the stock objects to be produced, both from a quantitative (quantity, container, etc...) and qualitative (FIFO date, lot no., stock nature, reservation no., etc.) point of view:
Close
Fields
The following fields are present on this tab :
| Product code defined in the GEODE product table. |
| The term Container encompasses the type and code of the container. |
| Quantity expressed in container type and code of the line. |
|   |
| Quantity expressed in the homogeneous container. |
| Quantity of the stock object expressed in CU |
| It is used to manage the quality-related differences at stock object level: expiry, reconditioning, etc. |
| 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. |
| Requested lot number. |
| Requested reservation number. |
| Requested support number. |
| Date corresponding to the input to store of the stock object. |
| 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. |
Close
Used to validate a declaration. This button is active only if the declaration has the status "6-Compliant". |
This is used to delete a declaration. This button is active only if no component movements has been selected. Deleting this declaration will close the AO line. |
Used to automatically select movements “to be consumed” based on the kit quantity to be declared. This button is active and can only be accessed during the assembling procedure. |