The stock adjustment does not make it possible to move a stock object, but is used to modify it while leaving it in its location. To do so, the object must not be to enter or to issue the stock.
It is also possible to perform a qualitative adjustment during the stock transfer, i.e. with a stock object movement.
This function can be used for consulting either the adjustment movements or the creations.
As soon as it is created, the movement is validated and it is impossible to have a WIP phase on this movement type. So, an adjustment movement cannot be either closed or deleted.
An adjustment movement is characterized by an adjustment type that takes one of the following values:
A qualitative adjustment can be automatically generated by the system if a stock characteristic is modified during a transfer.
Refer to documentation Implementation
A unit adjustment entry is performed from a header tab and an Adjustment tab. The other two tabs save the performed adjustment traceability information.
As a reminder, several adjustment types can be entered and, depending on the cases, different information is entered.
Presentation
The store/address field MUST be entered, then the product field (optional) and the object number field if the product code has not been entered or if several objects exist in the location.
The address field must belong to the selected store.
If information is entered in the product field, the system checks that the product belongs to the current depositor.
If information is entered in the product field, the system checks that a stock object of the product entered in the location really exists.
The entered movement code is compulsory and must be a manual adjustment-type movement code. Depending on the adjustment type, the fields can or cannot be entered in the Adjustment tab.
Close
Fields
The following fields are present on this tab :
Block number 1
| Adjustment movement number. |
| Creation date of the transaction. |
| Creation hour of the transaction. |
Block number 2
| Code used to identify the store. This code is controlled in the store table. |
| Address of the location. |
|   |
|   |
| Product code defined in the GEODE product table. |
|   |
| Identifier created by GEODE upon creation of the stock object. |
|   |
| 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. |
|   |
Close
Presentation
Container of the stock object: the container must be of the same level as the product's and must be defined in the product's palletization program.
Stock nature:it must be defined in the stock nature table
Origin : it must be defined in the origin table
Lot N° : to enter or modify a lot N°, the product must be managed in lot N°.
Support N° : to enter or modify a support N°, the product container must be managed in support N°.
Reservation code
Dates: the dates of a stock object can be modified based on the product date management.
Integrity controls between the modified fields and the location storage type are performed, in particular:
- If the product container is modified, the system checks that the new container is consistent with the location's in terms of:
Container equivalence for this store,
Authorized container equivalence for the location storage type
Stock objects homogeneity
Available space respected based on the filling control
- If the reservation code, the origin code or the lot are modified, the system checks that they are appropriate with the location stock objects' origin code, reservation code or lot.
If the origin and the reservation code are modified, if the system notices that the newly entered values are different to the existent stock objects' and that the location storage type is single-origin or single-reservation, the system then proposes to update all location stock objects with the new values.
If the user agrees, an adjustment by stock object and by modification will be generated by the system.
- If the FIFO date is modified, controls are performed on the basis of the FIFO parameterization on location, especially:
Earlier FIFO date entry authorized
input FIFO gap control
FIFO on location
Single-date
In this case, if there is an incoherence between the modified object's date and the dates of the objects in the location, the system proposes to update all stock objects accordingly. If the user agrees, adjustment movements will be realised for all modified objects.
The product's default palletization program is displayed.
If the product to be created is different, it is necessary to modify the quantities.
Quantity and container: stock object quantity and container
The container must be defined in the product palletization program, and must have the same level as the location container
In a reserve-type location, this quantity is always equal to 1, except when the product container level is equal to 5 (lowest level). If the user enters a quantity superior to 1, the system creates an adjustment movement by object, so by 1 quantity.
In a picking-type location, the objects have a quantity that is equal or superior to 1 irrespective of their container levels.
Quantity and homogeneous container: stock object quantity and lower container.
Though they are calculated by the system on the basis of the palletization program containers and of the container entered for the adjustment, these fields can be modified by the user. The CU equivalent is displayed.
If the entry should be expressed in a more appropriate container, the system proposes to express it differently.
Dates: By default, the dates are updated on the basis of the product record; they can be modified.
Stock nature:it must be defined in the stock nature table
Origin : it must be defined in the origin table
Lot N° : to enter or modify a lot N°, the product must be managed in lot N°.
Support N° : to enter or modify a support N°, the product container must be managed in support N°.
Reservation code
As soon as the increase or decrease-type movement code is entered, the selected object is displayed.
Adjustments of such type can be performed on stock objects with pending output or input; in this case, the adjustment only covers the part that is not in progress.
Quantity and container to be adjusted: quantity and container to be adjusted
By default, the displayed container is that of the stock object homogeneous container. The latter can be modified, but the entered container must belong to the stock object container palletization program.
In the case of a picking-type location, the stock object container is displayed instead of the homogeneous container.
As soon as the deletion-type movement code is entered, the selected object is displayed.
No field can be modified. Upon validating, the object is deleted.
This adjustment type is used to create an object linked to an existent object (merging without accrual function).
If a stock object number is entered, the system proposes to duplicate it and to link it to the entered object.
If no object number is entered, the system considers that it is a a linked object creation. The fields to enter are those of a stock object creation as well as the following field:
Movement link:Stock object N° to be linked to the object to be created.
Close
Fields
The following fields are present on this tab :
Management
| A location control code is requested if the current site, location and product set-up is activated. Validation will only be possible if the entered control code matches the expected control code (it can be viewed in the location record). |
|   |
Dates
| 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. |
Quantities
|   |
|   |
| The term Container encompasses the type and code of the container. |
| 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. |
|   |
|   |
|   |
|   |
| Container in which the quantity to be added to or to be withdrawn from the stock object is expressed. |
| Quantity to be added to (positive adjustment) or to be withdrawn from (negative adjustment) the stock object. |
|   |
|   |
|   |
Characteristics
| The link number is the number connecting stock objects when they are linked together (merging without accrual function) References |
|   |
| 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. |
Numerals/numbers
| Lot number(s) of the stock object(s). |
| Reservation number(s) of the stock object(s). |
| Support number(s) of the stock object(s). |
Close
Presentation
The fields of this tab cannot be entered and indicate, when consulting, the adjusted stock object's original values. This tab is therefore entered for all adjustment types, except for creation-type adjustments.
Close
Fields
The following fields are present on this tab :
Dates
| 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. |
Quantities
|   |
| Initial quantity of the stock object. |
| 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. |
| Quantity of the stock object expressed in CU |
|   |
|   |
|   |
Characteristics
| The link number is the number connecting stock objects when they are linked together (merging without accrual function) References |
|   |
| 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. |
Numerals/numbers
| Lot number(s) of the stock object(s). |
| Reservation number(s) of the stock object(s). |
| Support number(s) of the stock object(s). |
Close
Presentation
Indicates the adjustment creation date and time as well as the operator who generated it if the operator code entry is parameterized.
Close
Fields
The following fields are present on this tab :
Validation
| Adjustment creation date. |
| Adjustment creation time. |
| Operator who created the adjustment. |
Stock count
| Sequence assigned by the system to the inventory. |
| Stock count number |
Assembly
|
Quality control
| Numerical sequence automatically assigned by the system upon creation of the analysis request. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to an analysis request. |
Transfer
| Transfer number. |
Block number 6
|
Close
Adding a comment regardless of the adjustment type is possible before validating the adjustment; to do so, the user must activate the button. |
In addition to the generic error messages, the following messages can appear during the entry :
No modification to be processed.
Within the framework of a qualitative adjustment, no data has been modified compared to the stock object's.
Store: Record non-existent
The entered store does not exist.
Incorrect format
The entered address format does not correspond to the store's.
Location: Record non-existent
The entered location does not exist in the selected store.
Product: Record non-existent
The entered product code does not exist.
Product container: Record non-existent
The entered product container is not defined in the palletization program of the product.
No record selected
The entered location/product criteria do not make it possible to select a stock object.
Movement code: Record non-existent
The entered movement code does not exist for this depositor.
Creation, prohibited movement: Location blocked upon input.
The location is blocked upon input.
Location full
The location available space does not make it possible to accommodate the stock object creation.
Lot N°: Mandatory field
The product must be managed with a lot N°, which has not been entered.
No container of this article does fit for this location.
There is no container correspondance for this container or the storage type prohibits any container correspondance.
Container level different to the location's
The stock object container level has not the same level as the location's.
Quantity superior to standard quantity of container XX1
The entered quantity is superior to the default container quantity of the product record (indicative message).
Express the quantity in homogeneous container
On the basis of the product palletization program, the entered quantity and container could be expressed in another container of the palletization program; the system proposes to convert it.
Negative or null CU quantity after adjustment
The quantity to be adjusted is superior to the available stock object quantity.
Qualitative/deletion: Prohibited movement, stock object with quantity in progress
It is impossible either to perform a qualitative adjustment on an object that is being executed, or to delete an object with WIP.
No serial N° to enter
The adjusted product is not managed with serial numbers.