Palletization program update
This function is used to modify the palletization program of a product and to automatically regenerate the Warehousing entities (receipt movements, direct input movements, stock obkects) in compliance with this new palletization program.
Functional use: this tool has been implemented for those situations where the palletization program initially defined for a product is different from the physical packing received from the supplier. If this is the case, the Warehousing entities such as the direct input movements or the received SOs are logically inconsistent with the physical stock.
For example: Let us consider a product with the palletization program 1 PP1 = 10 CU
If 20 CU are received for this product, Warehousing will logically generate 1 direct input movement of 2 PP1 of 10 CU. Yet if the supplier physically sends a pallet of 20 CU, there is a gap between the logical and the physical stock.
Until now, the only solution was to delete the inconsistent stock, create a new product container in the palletization program (it is indeed impossible to delete the PP1 product container if entities exist on this product container) and manually reenter all the operations on this new container.
This new tool improves the procedure because it makes it possible to modify the PP1 product container and automatically regenerate the entities considered.
Operation:
- Step 1: the user specifies the modification of the palletization program that they wish to introduce.
-Step 2: Warehousing lists the various entities (receipt movements, direct input lines and input movements, stock objects) impacted by this modification.
- Step 3: the user selects/deselect the entities that they wish to modify (by default, the entities are all checked) and then saves their request.
- Step 4: Warehousing automatically performs the requested corrections (pall. program, receipt movements, input movements, stock objects).
Limits:
- This tool has not been designed to conduct repacking in the warehouse. In effect no transfer phase of Stock Objects is managed in a repacking store; the Stock Objects are directly generated in their own location.
Prerequisite
Refer to documentation Implementation
Screen management
This screen is sub-divided into 7 parts:
- the header screen: It enables the user to enter the modification data of a palletization program (Product, product container, etc.)
- the tab "Receipt mvts": it lists all the receipt movements impacted by this change in the palletization program.
- the tab "DI lines": it lists all the receipt movements impacted by this change in the palletization program.
- the tab "Blocked DI lines": it lists all the direct input lines which are impacted but which cannot be modified by the system.
- the tab "Stock objects": it lists all the stock objects impacted by this change in the palletization program.
- the tab "Blocked stock objects": it lists all the stock objects which are impacted but which cannot be modified by the system.
- the tab "Non-impacted stock objects": it lists all the stock objects not impacted by this change in the palletization program.
Header
Presentation
This header screen enables the user to specify the modification data of a palletization program that hey wish to perform with this tool.
These data are:
- the product
- the product container that should be modified
- the movement code (Automatic adjustment type) that will be used for all the update operations conducted on the stock objects considered.
- the lower container quantity: initialized by default to its current value; the user enters the new value there.
Furthermore this tool can be launched in simulation mode (no modification performed in Warehousing) with or without the print-out of a report "Correction of the palletization program".
Close
Fields
The following fields are present on this tab :
Block number 1
| Product code defined in the GEODE product table. |
| The term Container encompasses the type and code of the container. |
|
|
|
|
| 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. |
|
|
|
|
| Quantity of container of next lower level of a product container. |
Container of next lower level of a product container. |
|
|
Summary
| This parameter specifies the number of receipt movements impacted by the modification of the palletization program. Definition: a receipt movement is taken into account if is is linked to a non-validated receipt line with the same site, same depositor, same product, same container or higher level container depending on the latter container, and according to the CU quantity of the movement (higher or lower) with respect to the modification made. For instance: let us consider product A (1 PP1 = 10 CC1 = 100 CU) and a Receipt Line with 1 line receiving 100 CUs expressed as a receipt movement |
| This parameter specifies the number of direct input lines impacted by the modification of the palletization program. Definition: a direct input line is taken into account if it is not addressed and if there is at least one input movement not addressed for the same site, the same depositor, the same product, the same container or higher container depending from this container. For example: Let us consider product A (1 PP1 = 10 CC1 = 100 CU) and a DI line of 100 CU having one entry mvt of 1 PP1 of 10 CC1 = 100 CU |
| This parameter specifies the number of direct input lines impacted by the modification of the palletization program but which cannot be modified automatically by the tool. These lines will need to be modified manually. Definition: a DI line cannot be modified if this non-addressed line has at least one input movement that has already been stored (status "8-Stored/Completed"). |
| This parameter specifies the number of stock objects impacted by the modification of the palletization program. Definition: a SO is taken into account if it has the same site, the same depositor, the same product, the same container or higher container that depends on this latter container. Furthermore this SO must have no pending input or output movements, not be in a location that is under stock count or under picking planning. For instance: Let us consider Product A (1 PP1 = 10 CC1 = 100 CU) having 2 SOs |
| This parameter specifies the number of stock object impacted by the modification of the palletization program but which cannot be modified automatically by the tool. Definition: a SO cannot be modified if it is meets at least one of the following characteristics: |
| This parameter specifies the number of stock objects not impacted by the modification of the palletization program. Definition: a SO is not impacted if it is expressed in the container being modified with a palletization program (stored on the SO) corresponding to the new palletization program. For example: Let us consider Product A (1 PP1 = 10 CC1 = 100 CU) having 2 SOs |
Close
Tab Receipt mvts
Presentation
This tab lists all the receipt movements impacted by this change in the palletization program.
Definition: a receipt movement is taken into account if it is linked to a non-validated receipt line, with the same site, the same depositor, the same product, the same container or higher container that depends on this latter container.
Principle: the receipt movements will be expressed according to the new palletization program, and still from the CU quantity initially declared on the line.
For example: Let us consider a palletization program 1 PP1 = 10 CC1 = 100 UC) (1 CC1 = 10 UC)
Let us consider a EI line declared as receipt for a quantity of 180 CU with 2 receipt movements (1 PP1 of 10 CC1 = 100 CU and 1 PP1 of 8 CC1 = 80 CU)
If the palletization program is modified as follows:1 CC1 = 20 CU, then the 180 CU will be expressed with a single receipt movement of 1 PP1 of 9 CC1 = 180 CU
Close
Fields
The following fields are present on this tab :
Grid Receipt mvts
|
|
| Quantity expressed in container type and code of the line. |
| The term Container encompasses the type and code of the container. |
| Quantity expressed in the homogeneous container. |
| 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. |
| Equivalent in CUs of the quantity on the input line (calculated by the system). |
| Administrative receipt no. It is a sequential number assigned automatically by the system upon receipt creation validation. |
|
|
|
|
Close
Action icon
Check all
Used to select all the receipt movements to be found in the "Receipt mvts" tab that will be processed by the tool.
Uncheck all
Used to deselect all the receipt movements to be found in the "Receipt mvts" tab. They will not be processed by the tool.
Receipt
Provides a tunnel to the administrative receipt.
Close
Tab DI lines
Presentation
This tab lists all the direct input lines impacted by this change in the palletization program.
Definition: a direct input line is taken into account if it is not addressed and if there is at least one input movement not addressed for the same site, the same depositor, the same product, the same container or higher container depending from this container. This direct input line must not come from a receipt carried out with receipt movements.
Principle: the DI movements for a DI line will be expressed according to the new palletization program, and still from the CU quantity initially declared on the line.
For example: Let us consider a palletization program 1 PP1 = 10 CC1 = 100 UC) (1 CC1 = 10 UC)
Let us consider a DI line with 100 CU with 1 direct input movement of 1 PP1 of 10 CC1 of 100 CU.
If the palletization program is modified, such that:1 CC1 = 20 CU, then the 100 CU of the DI line will be expressed with a single receipt movement of 1 PP1 of 5 CC1 = 100 CU
Note: the DI lines having DI movements that have been created from receipt movements are not taken into account. In effect the tool uses the standard processings for DI movement regeneration (generation from the receipt movements, if any, otherwise from the palletization program). Since the receipt has already been carried out, the receipt modifications cannot be modified any longer. These DI lines will need to be manually processed (complete the DI line and recreate a new adjustment DI). For information these DI lines will be displayed in the "Blocked DI lines" tab.
Close
Fields
The following fields are present on this tab :
Grid DI lines
|
|
| Quantity expressed in container type and code of the line. |
| The term Container encompasses the type and code of the container. |
| Equivalent in CUs of the quantity on the input line (calculated by the system). |
| Numerical sequence automatically assigned by the system upon validation of the Input header. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a Direct Input. |
|
|
Close
Action icon
Check all
Used to select all the DI lines to be found in the "DI lines" tab. They will then be processed by the tool.
Uncheck all
Used to deselect all the DI lines to be found in the "DI lines" tab. They will not be processed by the tool.
Direct Inputs
Enables a tunnel to the direct input.
Close
Tab Blocked DI lines
Presentation
This tab lists all the direct input lines impacted by this change in the palletization program but which cannot be modified by the tool.
Definition: an impacted direct input line cannot be modified if it originates from a receipt carried out with receipt movements.
In effect the tool uses the standard processings for the regeneration of the DI movements (generation from the receipt movements if any, otherwise from the palletization progam). Since the receipt has already been carried out, it is no longer possible to modify the receipt movements. These DI lines will need to be manually processed (close the DI line and recreate a new adjustment DI)..
Close
Fields
The following fields are present on this tab :
Grid Blocked DI lines
| Quantity expressed in container type and code of the line. |
| The term Container encompasses the type and code of the container. |
| Equivalent in CUs of the quantity on the input line (calculated by the system). |
| Numerical sequence automatically assigned by the system upon validation of the Input header. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a Direct Input. |
|
|
| Administrative receipt no. It is a sequential number assigned automatically by the system upon receipt creation validation. |
|
|
Close
Action icon
Tab Stock objects
Presentation
This tab lists all the stock objects impacted by this change in the palletization program.
Definition: a Stock Object is taken into account if it has the same site, the same depositor, the same product, the same container or higher container that depends on this latter container. Furthermore this SO must have no pending input or output movements, not be in a location that is under stock count or under picking planning and not be a master object.
Update principle: For each location, for each group of stock objects with the same characteristics (product, container, lot, reservation, support no., stock nature, origin, master SO), the total CU quantity by SO group is expressed according to the new palletization program.
For example: Let us consider a palletization program 1 PP1 = 10 CC1 = 100 CU) (1 CC1 = 10 CU)
Let us consider on a given location, the 3 following SOs:
- SO 1: 1 PP1 of 5 CUs (50 CUs)
- SO 2: 1 PP1 of 7 CC1 (70 CUs), same characteristics as SO2)
- SO 3: 1 PP1 of 8 CC1 (80 CUs, with different characteristics)
If the palletization program is modified as 1 CC1 = 20 CU, then
SO 1 + SO 2 (120 CU) will be expressed as 1 PP1 of 6 CC1, and the SO 3 (80 CU) as 1 PP1 of 4 CC1.
Note: it is strongly recommended to update all the SOs of a location. Otherwise the tool may refuse any update request. For instance, if only part of the SOs of a location are updated, there would be some SOs that are not consistent with each other (different palletization program). If the location only manages "homogeneous" objects (storage type parameters), the tool will refuse to perform the update.
Close
Fields
The following fields are present on this tab :
Grid Stock objects
|
|
| Code used to identify the store. This code is controlled in the store table. |
| Address of the location in the store. |
| Quantity expressed in container type and code of the line. |
| The term Container encompasses the type and code of the container. |
| Quantity expressed in the homogeneous container. |
| 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. |
| Equivalent in CUs of the quantity on the input line (calculated by the system). |
| Identifier created by GEODE upon creation of the stock object. |
| Lot concerned by the return. |
| Reservation number assigned to each stock object created from this entity. |
| Support number assigned to each stock object created from this entity. |
| 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. |
| When stock objects are linked among themselves (Merging without accrual functionality), this field is entered. This field is updated with the number of the stock object with which it is linked. If this link number is equal to the object number, the object is referred to as the "master", it it is equal to another object number, the object is referred to as the "child". |
Close
Action icon
Check all
Used to select all the SOs present in the "Stock objects" tab. They will then be processed by the tool.
Uncheck all
Used to deselect all the SOs present in the "Stock objects" tab. They will then be processed by the tool.
Stock objects
Enables a tunnel to the stock object.
Close
Tab Blocked objects
Presentation
This tab lists all the stock objects impacted by this change in the palletization program but which cannot be modified by the tool.
Definition: a SO cannot be modified if it is meets at least one of the following characteristics:
- it has pending input or output movements
- it is in quality control
- it is in a location pending stock count
- it is in a location pending picking replanning
- it is a "master" object (linked SO)
Note: These SOs will not be impacted.
Close
Fields
The following fields are present on this tab :
Grid Blocked objects
| Code used to identify the store. This code is controlled in the store table. |
| Address of the location in the store. |
| Quantity expressed in container type and code of the line. |
| The term Container encompasses the type and code of the container. |
| Quantity expressed in the homogeneous container. |
| 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. |
| Equivalent in CUs of the quantity on the input line (calculated by the system). |
| Total expressed in CUs of the input pending movements for the object. |
| Total expressed in CUs of the output pending movements for the object. |
| Identifier created by GEODE upon creation of the stock object. |
| When stock objects are linked among themselves (Merging without accrual functionality), this field is entered. This field is updated with the number of the stock object with which it is linked. If this link number is equal to the object number, the object is referred to as the "master", it it is equal to another object number, the object is referred to as the "child". |
Close
Action icon
Tab SOs not impacted
Presentation
This tab lists all the stock objects not impacted by this change in the palletization program.
Definition: a SO is not impacted if it is already expressed in the new palletization program.
Close
Fields
The following fields are present on this tab :
Grid Objects not impacted
| Code used to identify the store. This code is controlled in the store table. |
| Address of the location in the store. |
| Quantity expressed in container type and code of the line. |
| The term Container encompasses the type and code of the container. |
| Quantity expressed in the homogeneous container. |
| 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. |
| Equivalent in CUs of the quantity on the input line (calculated by the system). |
| Identifier created by GEODE upon creation of the stock object. |
| Lot concerned by the return. |
| Reservation number assigned to each stock object created from this entity. |
| Support number assigned to each stock object created from this entity. |
| 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. |
| When stock objects are linked among themselves (Merging without accrual functionality), this field is entered. This field is updated with the number of the stock object with which it is linked. If this link number is equal to the object number, the object is referred to as the "master", it it is equal to another object number, the object is referred to as the "child". |
Close
Action icon
Close
Reports
By default, the following reports are associated with this function :
PLZCRT : Palletization plan update
This can be changed using a different setup.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
HMGQTY: Non-editable field.
The tool cannot carry out the update of this SO because the new SO thus created would not comply with the consistency rules of the location (setup linked to the storage type).
Movement xxxxxx: Modification in process on another workstation.
The tool cannot modify this movement because it is being modified by another user.