Receipt validation
This phase corresponds to the declaration of the products that are actually received from a quality and quantity point of view.
There are two receipt modes:
- The "Standard" mode: closes the receipt upon each validation of the received quantities. The administrative receipt moves to status '4-Validated'.
- The "Drip and Drop"mode: keeps the administrative receipt open after validation of the received quantities. This mode is used to receive the goods of a receipt in several phases while staying on the same administrative receipt. The administrative receipt remains at status '2-Pending'.
Prerequisite
Refer to documentation Implementation
Screen management
After selecting the receipt no., the quantities and disputes are entered in the EI lines tab.
Header
Presentation
Entry or selection of the receipt no.; the receipt status is displayed.
Close
Fields
The following fields are present on this tab :
| Administrative receipt no. It is a sequential number assigned automatically by the system upon receipt creation validation. |
|
|
Close
Tab Receipt
Presentation
Information entered or updated upon creation of the administrative receipt.
Close
Fields
The following fields are present on this tab :
Carrier
| Code identifying the carrier. This code must be defined in the carrier table. |
| Carrier trade name. |
| Usually, the transport mode corresponds to the notions of messaging, freight, express,... The transport mode is checked against the transport modes table. |
| Carrier reference. |
Characteristics
|
|
| Document creation date. By default, it is equal to the system date. |
| Document creation time. By default it is equal to the system time. |
|
|
|
|
|
Close
Tab EI lines
Presentation
The line tab is used to declare the received products further to the quality and quantity check of the receipt.
Lines are displayed by expected input number and expected input line number.
When positioned on a line, the summary elements of the line are displayed at the bottom of the screen, including the product description, the expected quantity, the quantity already received and/or pending receipt as well as the balance quantity.
For "Drip and drop" receipt, the "Drip and drop" column is inserted between "Received DU" and "Dispute". This column is used to indicate the line(s) to be received in this mode by double-clicking the relevant line.
Method of operation:General entry : For each line, enter the quantity actually received in the "Received DU" column.
Some fields in the table can be directly entered: Input container if the received container is different from the default container of the product record; Source code if you wish to modify or enter the code of the expected receipt line; Reservation no.; Lot no.if the product is managed by lot; Support no.. Based on the product set up, it may prove mandatory to enter some dates.
It is possible to duplicate lines provided they have different quality-related characteristics.
After pressing Enter on each entered line, the entry is saved but it remains modifiable as long as the button has not been used.
Entry of disputes : for any partial dispute on the line, it is possible to insert a receipt line by clicking the Action icon on the grid.
The original line is then duplicated and it is possible to enter the Dispute column.
The dispute is related to a transport or supplier anomaly. If the dispute is set to Yes, entering a stock nature is mandatory.
If a dispute is declared for the line, the Put-away flag can be entered:
- If it is set to 'Yes', a direct input line will be created upon receipt validation, thus enabling the stock objects to be created. This case refers to the identified dispute put away with a specific stock nature. Later this stock must be the subject of a supplier return or recycling.
- If it is set to 'No', no input line will be created upon receipt validation, and thus no stock will be created for this line. This case refers to the dispute picked up by the carrier upon receipt.
Receipt in "Drip and Drop" mode: : after saving the quantities to be received in the "Received DU" column for each line of the receipt, the button becomes available.
Once this button has been selected, the line(s) to be received under the "Drip and Drop" mode need to be mentioned in the corresponding column, by double-clicking on said lines.
The button is used to abort the operation.
Finally, the button is used to validate the receipt in "Drip and drop" mode. The direct entry is generated and the administrative receipt is closed.
The parameters "Close the line" and "Close the input" of the receipt mode act like a balance management. This means that the absence of balance management is not compatible with the "Drip and Drop" receipt mode.
Should an administrative receipt need to be closed further to a receipt carried out in "Drip and Drop" mode, the receipt will have to be validated with lines whose quantities are null.
Receipt in "Standard" mode: : after saving the quantities to be received in the "Received DU" column for each line of the receipt, the becomes available.
This button is used to validate the receipt in "Standard" mode. The direct entry is generated and the administrative receipt is closed.
Supplier date contract:When recording a receipt line, if the line is applicable for a Supplier date contract, a control checks that the FIFO date on the line is consistent with the rules of the date contract and date return options. If it is not consistent, a message is displayed informing the operator that the line can be disputed against a stock nature, depending on the setup used.
Close
Fields
The following fields are present on this tab :
|
|
| Used to trigger Cross-Docking for the receipt mode. |
|
|
| CU quantity received for the input line. |
|
|
| Used to stipulate which lines should be received in "Drip and Drop" mode. |
| Mentions a dispute, if any. If the entered value is 'Yes', it is mandatory to enter a nature identifying a transport or a supplier dispute. |
| Specifies whether or not the goods are put away (the entered value is 'Yes', an entry line will be created, the entered value is 'No', the entered quantitywill not be put away, and the goods are supposed to be taken away by the carrier). |
| It is used to manage the quality-related differences at stock object level: expiry, reconditioning, etc. |
| Code used to identify the store. This code is controlled in the store table. |
| The system exclusively addresses the goods to the requested store. If the search in this store fails, the system does not try to make the link to other stores. |
| Type and code of the input container of the line. By default, it is the product default input container. |
| 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. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Specifies the number of receipt movements declared for the receipt line. A movement corresponds to a container physically received in the datawarehouse. |
|
|
|
|
|
|
|
|
Info
|
|
|
|
|
|
| Specifies the total number of units already received or being received. |
|
|
|
|
Numerals/numbers
| Lot number assigned to each stock object created from this entity. |
| Reservation number assigned to each stock object created from this entity. |
| Support number assigned to each stock object created from this entity. |
Dates
| Production date corresponding to the end of the item production cycle. |
| Sale-by Date (SbD). The SbD is generally used as FIFO date for food products. |
| Detention date. This date corresponds to the instant before which the stock object is unavailable for an output movement. (for instance, quarantine). |
| 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
Action icon
Expected inputs
Provides access to the expected input to which the administrative receipt line is linked.
Init of received DU
Used to automatically complete the "Received DU" column with the remaining quantities, quantities to be received and quantities mentioned in the "Close DU" field. This operation can be carried out from any receipt line and it will be applied to all the receipt lines.
Key in receipt mvts
Used to declare the containers actually received in the warehouse.
example: let us consider product A with the following palletization plan: 1 PP1 -> 2 CC1 of 25 ACUs each. It is possible to declare the receipt of 40 ACUs as follows: 1 PP1 of 2 CC1 of 20 ACUs each.
In case of inconsistency between the number of DU declared and the number of DU specified in the "Received DU" column, the "Received DU" cell is displayed in red and the information is displayed in bold characters. Otherwise, information is set to bold only.
A column entitled "Receipt mvt nbr" provides information on the number of declared receipt movements for a receipt line.
The receipt movements declared in the administrative receipt are to be considered as a priority over the setup of the expression of the input mode movements linked to the products upon creation of the input movements. Same thing for the input movement regeneration function.
Entry of the receipt movements is performed for each receipt line.
Standard Rerouting Action
Select all
Used to check in one single go all the lines to be received in "Drip and Drop" mode.
Uncheck all
Used to uncheck in one single go all the lines to be received in "Drip and Drop" mode.
Close
Specific Buttons
Used to save the quantities entered in the "Received CUs" column. |
Used to carry out the receipt of the quantities previously entered in "Drip and Drop" mode. |
Menu Bar
Functions/Load analysis
Used to launch the load analysis for the selected receipt
The load analysis function is contingent upon the LA0 activity code for a non-received receipt and on the LA2 activity code for a validated receipt.
The analysis will apply to:
• receipts in progress, on the EI list (and related lines) of the receipt
• validated receipts, on the input movements in progress originating from the receipt.
Following a load analysis request:
• a new analysis is created with the following characteristics:
- Flag to maintain = "no"
- Template (for info.):
▪the template associated to the triplet (function, current site, current depositor) for a single-depositor function
▪ By default, or for a multi-depositor function, the template associated to the triplet (function, current site, depositor set to "blank").
▪ By default, the template associated to the triplet (function, site set to "blank", depositor set to "blank")
▪ By default, the template is set to "blank".
▪ The calculation for the analysis is launched.
▪ The operator accesses the load display screens from which it can also access the information related to the analysis (description and flag "To be kept") and request the printing of the analysis results.
Functions / Calculation of containers
Used to know what the quantities that remain to be received represent in terms of number of default containers according to the palletization program of each product. This grid is sorted by product code and can be viewed as long as the administrative receipt has not been closed.
Functions / Receipt lines
Used to obtain a detailed history, sorted by product code, of the received quantities in "Standard" or "Drip and Drop" mode. It can be viewed irrespective of the status of the administrative receipt.
Functions / Consumable movements
Used to declare 1 or n input-to-stock movements of consumables within the framework of the administrative receipt.
This entry can take place at any moment, irrespective of the AR status.
Various data must be entered to complete a consumable input movement:
- The consumable code: is specified in the product record of the consumables
- The movement code: must belong to the group of the 'CONSUMABLE ' processes and be of 'INPUT' type
- The quantity:quantity of the input movement
Since the input movement of the consumable is declared from a known entity, the carrier, transport method, supplier and supplier title information are, if need be, entered with that of the entity.
For an input movement, such information as customer, customer title, the type of entity and the number of said entity is not accessible.
Depending on the setup, it is requested to enter an operator code to validate the input movement. The stock is incremented upon validation.
The movement can no longer be modified after validation. Therefore it is not updated when updates are carried out on the entity with which this movement is associated.
It is possible to generate 3 reports:
- In File/Print/Record:
- Stock of the consumables sorted by consumable or by quantity
- Screen print for the selected record
- In File/Print/List:
- Movements of the consumables sorted by consumable or by date
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Received quantity > planned quantity.
The receipt mode of the EI does not make it possible to exceed the balance quantity on the EI line.
Product containers: X124PP5 Record does not exist
The input container entered has not been defined for the product
Stock nature: Z Record does not exist
The stock nature entered has not been defined.
Origin: TO: Record does not exist
The stock nature entered has not been defined
Lot no. field error: mandatory entry
Entry of the lot number is mandatory.
Received DU error: mandatory field
Entry of the received quantity is mandatory
Validation impossible, no Drip and Drop line has been checked.
The Drip and Drop receipt mode has been chosen but no line has been selected.
Drip and Drop prohibited if quantity = 0
No quantities to be received have been entered and saved for the selected line.
Validation impossible, qty of the receipt line <>qty of the receipt mvts
Inconsistency between the quantity declared in the option "Entry of receipt movements" and the quantity to be received, mentioned in the "Received CUs" field, for the entry line.
The error messages associated with the consumable movement declaration are the following:
"Consumable" field error. Mandatory field.
The consumable code is a mandatory entry.
"Movement code" field error. Mandatory field.
The movement code is a mandatory entry.
"Movement code" field error. Movement code of non-consumable type.
The entered movement code must belong to the group of the 'CONSUMABLE' processes.
"Movement code" field error. Movement code of output type.
The entered movement code must necessarily be of 'INPUT' type.
"Quantity" field error. Mandatory field
The quantity of the input movement must necessarily be entered.
Application error. The depositor must be entered for this origin.
When an input movement is associated with an expected input or a direct input, the depositor must necessarily be entered.
"Mvt origin no." field error. Reference of the origin not found.
The number of the Warehousing entity must necessarily be entered and exist for the site.
"Consumable" field error. Consumable blocked upon input.
The consumable must necessarily be authorized for input for an input movement to be completed.