Delivery Orders @ L.V. Expertise X3

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Header
Tab General
Tab Ship-to Customer
Tab Carrier
Tab Bill-to Customer
Tab Lines

Screen management

A DO is created using 4 tab for the header and 2 tabs for the lines.

Header

Presentation

Number.Numerical sequence assigned automatically by the system when saving the DO. This number is a piece of information specific to the site, all depositors included. This piece of information features a unique access key to a DO.

Reference.DO reference. Optional entry.
If this field is left blank, the system automatically assigns the DO number, which can be modified.
If this field is entered, the system imposes the uniqueness of the field depending on the output configuration setup.

Pending transfer. Specifies the DO type.

If the "Pending transfer" flag is activated, this means that the DO has been shipped, via an "inter-site" round, to another site. On this site, the final shipment to the ship-to customer has no taken place yet. This is only when the final shipment has been confirmed that the DO will move to status 9-Shipped/Closed on the preparation site.

A DO can only be shipped to another site and as a consequence be labeled as "pending transfer" via the shipment by "inter-site" round.

On the destination site, a DO labeled as "pending transfer" cannot be deferred, deleted, unloaded or split. The DO "pending transfer" can be consolidated with other DOs of the current site within the same final shipment round or it can be re-shipped to its original site via a so-called return "inter-site" round.

When a DO is shipped to another site within the framework of an "inter-site" round, a so-called "inter-site" DN can be printed if the depositor level configuration is completed (Output configuration).

Status.This field specifies the status code of the DO header.

Date.Date of creation of the DO. When creating a DO, the system date is proposed by default. This field is mandatory. The DO date can be modified by the user.

Fields

The following fields are present on this tab :

Number (field DLONUM)

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.

Reference (field REF)

Document reference.

Date (field DAT)

Creation date of the document (expected input, input, DO, etc.).

In transit (field TNSFLG)

Specifies the DO type. If it is triggered as "Pending transfer", this means that the DO has been shipped, via an "inter-site" round, to another site. On this site, the final shipment to the ship-to customer has no taken place yet. Once said final shipment has been confirmed, the DO will move to status 9-Shipped/Closed on its original site.

Status (field DOHSTA)

Tab General

Presentation

Order

Optional information linked to the level-3 order (order no., order date, order reference, customer reference and order reference for the customer).

Preparation

Movement code. The movement code is used to qualify a DO (restocking order, imposed order, supplier return, etc.). The possible values are those of the Table of the movement codes authorized on output.

Preparation mode.The preparation mode is used to qualify the appropriate preparation type for the DO (declarative load preparation, prepacking, regrouping of a PO, etc.). The possible values are those collected in the preparation mode table.

Merging of flows(Available from version G2). Stipulates whether or not the entered preparation mode is of "merging of flows" type.

Ship-to customer. Entry of the code of the ship-to customer who must be defined in the Customer table. The field is not mandatory and the customer data can be entered directly.

Provisional dates

Launch date. By default, it is equal to the entry date of the DO but the field remains modifiable.

Delivery date. By default, it is equal to the entry date of the DO, but it remains modifiable.

Partial shipment

Value recovered from the ship-to customer code table and modifiable. Stipulates if the customer accepts partial shipment:
Yes.The customer accepts partial shipment irrespective of the requested quantity
By line. The customer accepts partial shipment provided the whole line has been shipped. If a shortage is detected on a line of the DO, the whole line will be completed during the wave launching.
No. The customer does not accept partial shipment. As soon as the system detects a shortage, the DO will be automatically completed upon wave launching.

For all the other functions that can modify the quantity launched on preparation (PO validation, parcel validation, DO deferment, etc.), the following principle shall be applied: For a DO, it is possible to partly validate the balance, then delete it. On the other hand, it is not possible to delete the balance, then validate it. This principle has been adopted to meet the issue of "preparation disruption" whenever a quantity has already been prepared and validated.

Urgent. This setup is used to subsequently create urgent DO waves to be handled in priority.

Service priority(Available from version G2). This setup is exclusively used in the launching of waves for DOs whose preparation mode is the "merging of flows" mode. It makes it possible to set priorities in the stock shortages by DO.

Effective dates

Launching. Date updated by the system, upon the last wave launch of the DO.

Packing(Available from version G2). Date updated by the system, upon last load preparation the DO.
For the DOs in prepacking preparation mode, the load preparation date is equal to the date of the last launch.
For the DOs in declarative load preparation mode, it is the last load preparation date of the DO..

Preparation. Date updated by the system, upon validation of the last movement of the DO.

Shipment. Date updated by the system, when moving to status 9 of the DO.

Management setups: Palletization, Loading, Shipment, Balance management.
By default, these setups are equal to those of the output configuration. Nevertheless, they can still be modified foe each DO.

Transmitted by L3. Mentions if the DO has been created via the interface of the delivery orders.

Wave no.. Value updated by the system upon allocating the DO to a wave.

Splitting no.(Available from version G2). Value updated by the system, when using the DO splitting function.

Fields

The following fields are present on this tab :

Order

Client (field ORDCLT)

Customer reference.

Customer reference (field CLTORDREF)

Order reference for the customer.

Transmitted by L3 (field TRM)

Number (field ORDNUM)

Level 3 order number.

Date (field ORDDAT)

Level 3 order date.

Reference (field ORDREF)

Level 3 order reference.

Preparation

Movement code (field MVT)

The movement code is used to make the distinction between movements of the same type.
It is required when creating:

An expected input
A supplier input
A factory input
A customer return
A DO
An adjustment
A transfer
A consumable input/output

The movement code is checked against the movement code table.

Picking mode (field PMD)

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.

Merging of flows (field WAVFLC)

Ship to (field WDLVCLT)

Code of the ship-to customer that must be defined in the customer table.

SU type (field SHU)

Type of SU on which the parcel must be palletized.

SU group (field GRUSHP)

Single consignee SU (field SHPSNGDLV)

It will be possible to regroup in one SU parcels belonging to the same CR, i.e. parcels with identical information (round, carrier, transport mode, ship-to customer code, company name (1st line), delivery postal code, Incoterm code and location).

Single DO SU (field SHPSNGDLO)

If it is checked, it is possible to only regroup parcels from the same DO into a SU.

Partial delivery (field PTLPIK)

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).

Urgent (field URG)

Used to subsequently create urgent DO waves to be handled in priority.

Service priority (field PIR)

The service priority is used to define an order of priority for the processing of the delivery orders.

Planned dates

Launch (field EXPLNCDAT)

Provisional date for the wave launching. By default, it is equal to the entry date of the DO. It remains modifiable.

field EXPLNCTIM

Provisional time for the wave launching. By default, it is equal to the entry time of the DO. It remains modifiable.

Delivery (field EXPDLVDAT)

Provisional delivey date of the DO. By default, it is equal to the entry date of the DO. It remains modifiable.

field EXPDLVTIM

Provisional delivey time of the DO. By default, it is equal to the entry time of the DO. It remains modifiable.

Effective dates

Launch (field LNCDAT)

Date updated by the system, upon the last wave launch of the DO.

field LNCTIM

Packing (field PKGDAT)

Date updated by the system, upon last load preparation the DO.
For the DOs in prepacking preparation mode, the load preparation date is equal to the date of the last launch.
For the DOs in declarative load preparation mode, it is the last load preparation date of the DO..

field PKGTIM

Preparation (field PIKDAT)

Date updated by the system, upon validation of the last movement of the DO.

field PIKTIM

Shipment (field SHPDAT)

Shipment date for the entity.

field SHPTIM

Management options

Parcel palletisation (field PRCPLZ)

Specifies if the parcel palletization phase is active for the current depositor.
If the box is not checked, parcel palletization is not managed.
If the box is checked, parcel palletization is managed. Each parcel of the DO must be palletized.

Loading of parcels (field LODCTL)

Specifies if a unitary parcel loading declaration must be carried out.
At this stage, "unitary" refers to: the parcel, if palletization is not managed, or the SU if palletization is managed.
If the box is not checked, the parcel loading declaration is not used.
If the box is checked, the parcel loading declaration is used.

Shipment management (field DSPMGT)

Informs the system on the use of the "Shipment confirmation" function for a DO, packed or not.
If the box is not checked, the shipment confirmation is not used. The system takes the DO status to 9, shipped, closed, to the final phase before shipment.
If the box is checked, the shipment confirmation is used according to two possible modes, by DO or by shipment round.

Note: it is not necessary for all the pickings (parcels/P.O.) of a DO to be validated for the shipment of a DO (partial shipment) to be confirmed, if shipment deferments are used.

Remainder management (field SHRMGT)

If the box is not checked, a DO partly covered or not covered at all is automatically closed further to the moving to status 9.
If the box is checked, all those lines that are not covered are kept in the portfolio.

A DO is fully kept (moving to status 2-Pending nth preparation) if:
- the DO is in partial or total shortage upon wave launching,
- picking orders are cancelled or partly cancelled,
- the shipment cancellation is used.

To finally close it, it then becomes necessary to go to each DO and close each one in turn.

SSCC management on output (field SSCFLG)

Cross Docking

Control level (field CDKLVLCTL)

Specifies the last phase that can be crossed by the DO lines as long as the Cross-Docking requirements are under process for the DO.

Block number 6

Wave no (field WAVNUM)

Numerical sequence assigned automatically by the system upon wave launching.

Fraction no (field DLOORG)

field SPLNUM

Tab Ship-to Customer

Presentation

If the customer code is entered, the customer data originating from the customer code table are displayed. Otherwise it is necessary to enter the company's name, address, postal code and town.
The postal code can be defined in a table but it remains modifiable.

Comments are printed on the DN and they can be the subject of delivery or sales notices.

The data of the ship-to customer can be modified as long as the DO has neither been palletized nor loaded.

Fields

The following fields are present on this tab :

Ship to

Code (field DLVCLT)

Code of the ship-to customer who must be defined in the Customer table.

Country (field DLVCRY)

Country code of the ship-to customer.

field DLVCRYNAM

Country description of the ship-to customer.

field DLVNAM

Company name of the ship-to customer.

field DLVADD

Ship-to customer address.

Postal code (field DLVPOS)

Postal code of the ship-to customer.

City (field DLVCTY)

Ship-to customer's town.

Region (county, state, ..) (field DLVSAT)

Ship-to customer status.

Telephone (field DLVTEL)

Ship-to customer's telephone number.

Fax (field DLVFAX)

Fax number of the ship-to customer.

Comments (field DLVREM)

Comments that will be printed on the Delivery Note.

Tab Carrier

Presentation

Rounds

Generic round. A customer code can be assigned to a pre-determined round, that will be displayed if it has been entered in the customer table. Otherwise the generic round can be entered and it is controlled with respect to the generic round table.
This round will be subsequently used to create the shipment round and assign DOs of the same generic round to it.
To enter this field, the DO must have the "shipment management setup" set to yes.

Round no., round date and time. Values updated by the system upon allocating or disallocating the DO of a round.

Quay(Available from version G2).Store of "quay" type and address, originating either from the generic round code, or from the shipment round.

Round position. Data coming from the customer code table or entered directly. Specifies the filling order of the truck in order to unload the goods depending on the carrier forwarding order.

Destination site. Specifies the destination site of a DO "pending transfer" once the latter has been shipped via an "inter-site" round.

Transport

Carrier and transport method, freight type. Default values of the customer code table if said values are entered, or of the generic round if the latter is entered for the DO.

Transport reference. Optional field

Delivery field: Optional field that can be used in case of assignment of a carrier/transport method.

The information related to the transport can be modified via the round management if the DO has already been assigned to a round. Otherwise, it can be modified in the DO header as long as the DO has neither been palletized nor loaded.

Delivery Note

Print : Used to mention the name of the DN print-out for this DO. Default value of the customer code table if it has been entered or of the depositor configuration.

Languagee. Used to set up the language used to print the DN.

Freight amount calculation. Used to calculate the freight amount of the DN during shipment.

Price list code. Stipulates the price list code to be used to calculate the freight amount

Currency: Specifies the currency to be used.

Fields

The following fields are present on this tab :

Round

Generic round (field GDR)

A generic round is a set delivery round (with respect to days and maximum shipping time), a round being the content of a truck.

Round no. (field QYMNUM)

Number assigned by the system and used to identify the round in a unique way within a site.

Round position (field DRNPST)

Order in which the round must be loaded. This information is used to allocate an unloading or loading sequence number to the DOs of a round.

Date (field DRNDAT)

Time (field DRNTIM)

Appt (field CRANUM)

Dock (field DRNSTO)

field DRNSLO

Destination site (field DENFCY)

Destination site of the DO "pending transfer".

Transport

Carrier (field CRR)

Code identifying the carrier. This code must be defined in the carrier table.

Transportation method (field CRRMOD)

Usually, the transport mode corresponds to the notions of messaging, freight, express,... The transport mode is checked against the transport modes table.

Carriage reference (field CRRREF)

Carrier reference.

Transport type (field CGT)

The freight type can contain the Incoterm codes, for example (freight charges, paid, etc.).

Delivery area (field DLVARE)

Delivery field of the ship-to customer.

Delivery note

Report (field DLNEDT)

Name of the report for the print-out of the DN and packing list, jointly printed if the DN is in the packing stage. The name set up here is used as the default value of the corresponding DO header field.

Language (field EDTLAN)

Setup of the requested language to print the delivery note and the packing list.

Carr. amount calculation (field DLNCST)

Used to calculate the freight charges for the CR and/or CN upon shipment confirmation via the transport preinvoicing functionality.

Price list code (field DLNRAC)

Price list code used to calculate the freight amount by means of the

freight pre-invoicing functionality.

Currency (field DLNCUR)

Specifies the currency used for the delivery note.

Tab Bill-to Customer

Presentation

A bill-to customer code can be associated with a ship-to customer code, or it can be directly entered in the DO.

Fields

The following fields are present on this tab :

Code (field INVCLT)

The invoicing customer code can be different from the ship-to customer code. This code is controlled in the customer code table.

Country (field INVCRY)

Country code of the bill-to customer.

field INVCRYNAM

Country description of the bill-to customer.

field INVNAM

Company name of the bill-to customer.

field INVADD

Bill-to customer address.

Postal code (field INVPOS)

Postal code of the bill-to customer.

City (field INVCTY)

Bill-to customer's town.

Region (county, state, ..) (field INVSAT)

Bill-to customer status.

Telephone (field INVTEL)

Bill-to customer's telephone number.

Fax (field INVFAX)

Fax number of the bill-to customer.

Notes (field INVREM)

Comments.

Tab Lines

Presentation

This tab displays in the form of a grid all the characteristics of the DO lines previously entered (reference, quantity put-away, FIFO, etc.).
The first column mentions the line nature: blank value for the normal lines, value equal to "K" for the Kit line, and value equal to "C" for the Component lines.

Fields

The following fields are present on this tab :

Grid

T (field TYPAFF)

Product (field ITM)

Code (field COD)

Reference (field LINREF)

Order (field ORDNUM)

No. (field CTRQTY)

Cntr. (field CTR)

CU/STK no. (field CUQ)

STK (field UOMSYM)

Total shipped (field TOTSHP)

Mvt code (field MVT)

Nature (field SKN)

Date (field DAT)

FIFO (field FIFDAT)

Parcel range (field IPSPRA)

Group of parcel (field GRUCOD)

Max lev. disp. state (field DSTMAXLVL)

Lot no. (field LOT)

Reservation no (field RSA)

Support no. (field SPT)

Serial number (field SRNDAC)

Status (field DOLSTA)

Action icon

Serial Number Entry

Reports

By default, the following reports are associated with this function :

OL : DO portfolio

This can be changed using a different setup.

Close
Lines

Menu Bar

Used to close a header or a line. Closure is an operation that consists in switching to status 9 of the header or lines; in effect, the deletion is not authorized for entities that can be transmitted via an interface.
Closure of a Kit type line closes all the associated component lines.

To gain direct access to the detail of the DO lines

Header

The elements specified here are those that come from the DO header previously created or selected. The following data are mentioned here:

Number, Reference, Status and Date.

Line/row

Number. Number assigned by the system. Within the frame of an inquiry, the number of the line to be queried needs only to be entered and its content is displayed automatically.

Status.This field specifies the status code of the DO. line.

Line nature(Available from version G2). Stipulates if the entered product has the "normal", "Kit" (or Compound) or "Component" type.
When selecting the Kit value, the system searches for the product code entered in the kit table:
if this code is found, the operator is asked is they want the system to create the next lines according to the defined BOM; the creation is then submitted to the operator by the unit , who can then validate the creation by means of the "Create" button or interrupt it by means of the "Abort" button.
If the code is not found, the BOM declaration is performed by the unit and left free.

A kit nature line must contain at least two lines of a Component nature.
The quantities of each component line must be multiples of the kit number.

Product. Code of the item to be received for the input line

Title.Description of the item code.

General

Quantities

Quantity and LU code.Container quantity and type and code of the DO line.
The entered container must be defined in the palletization program of the product and its output must not be prohibited.
If the entered LU code is level 5, the system guarantees during wave launching that a search will be conducted on one or several stock objects of different levels, whose total meets the requested quantity.
If the requested LU code has a different level, a stock object with exactly the same level will be looked for during wave launching.

The CU total linked to the LU quantity is displayed, as well as the palletization program of the entered LU code.

Reference.. Reference of the DO line. Optional entry. Can be used to establish a link between L2 and L3 during interfaces; in that case, this field is automatically fed.

Order. Optional entry, order line no. or order no. in case of a multi-order DO.

Dates

DO lines. DO header creation date.

FIFO. Requested FIFO date. Upon wave launching, if such a date is entered, and based on the output configuration set-up, the system picks stock objects with a FIFO date strictly equal to the requested date, or with a date later than or equal to the date of the DO line.

Movement code. Default movement code of the DO header.

Stock nature. Requested stock nature. Upon wave launching, if such a nature is entered, the system picks stock objects with the same stock nature.

Numbers:

Lot no.. Imposed lot no. Upon wave launching, if such a lot is entered, the system picks stock objects with the same lot number. If it is not entered, the system picks stock objects based on the priorities of the output criteria.

Reservation no.. Requested reservation no. Upon wave launching, if such a number is entered, and based on the output configuration set-up, the system picks stock objects with the same reservation code or a different reservation code in case of insufficient stock.

Support no.(Available from version G2). Requested support no. Upon wave launching, if such a number is entered, the system picks stock objects with the same support number.

Packing (Available from version G2).

Parcel routing. Parcel routing imposed for the line; during prepacking, the system short-circuits the search for the optimum parcel to use the one imposed for the DO line.

Regrouping. If it is assigned, during pre-packing, the system short-circuits the search for the standard grouping code in order to only use that of the DO line.

Maximum level for the 'dispatchable as is' setup.By default, it is set to level 5. This setup is used to sort-circuit the 'dispatchable as is' set-up of the product container. To be dispatchable as is, a product container must, in addition to its own set-up, have a level higher than or equal to that of the line.

For example: let us consider a product with 5 levels of container dispatchable as is.

The DO line is equal to 1 => only the level 1 objects will be dispatchable as is.
The DO line is equal to 2 => only the level 1 and 2 objects will be dispatchable as is, the others will be packed unsorted/in bulk.

Etc.

The DO line is equal to 5 => all the objects will be dispatchable as is.

Comments

Comments. If it is entered, the comment on the line is printed on each DN line.

Notes. The field is not printed on the DN..

Progress

Preparation

Launched. Quantity expressed in CU updated by the system upon creation of the DO line, and when moving to status 9 of the DO in case of balance management.
By default, the launched CU quantity is equal to the CU quantity of the DO line, then, in case of balance management, it is equal to the balance left to be delivered.

Shortage. Quantity expressed in CU updated by the system, upon wave launching of the DO line in case of shortage, upon deletion of a PO or a parcel in case of missing stock, upon shipment cancellation if the DO is partly cancelled.

Transferred(Available from version G2).Quantity expressed in CU updated by the system if the DO is in preparation mode with merging of flows type, and corresponding to the transferred (validated) CU quantity to cover the DO line.

Not transferred(Available from version G2). Quantity expressed in CU updated by the system if the DO is in preparation mode with merging of flows type, and corresponding to the non-transferred (cancelled) CU quantity to cover the DO line.

Prepared. Quantity expressed in CU updated by the system, upon partial or total validation of the output movement.

Shipment

Cancelled. Quantity expressed in CU updated by the system, upon cancellation of the shipment either by DO or by parcel.

Deferred. Quantity expressed in CU updated by the system, upon shipment deferment.

Shipped. Quantity expressed in CU updated by the system, upon DO shipment.

Dates

Launching. The launching date and time is the last date and time of the wave launching of the DO line.

Pending shipment. The shipment waiting date and time is the last shipment waiting date and time of the DO line.

Shipment. The shipment date and time is the last shipment date date and time of the DO line.

The "Delete" button is active as long as the creation of the line has not been saved at the level of the DO header.

The "Insert" button is used during line creation to insert a line between 2 previously created lines. This button is active as long as the creation of the line has not been saved at header level.

Only the "Complete" and "Create" buttons are active from the moment that the lines have been created and saved at header level.

List

This tab enumerates all the DO lines and summarizes the detail information available from the previous tabs.

Drill Down / SUs
Drill Down/Parcels
Drill Down/Transactions
Drill Down/DO line shortages
Drill Down/Overview
Drill Down / Transfer history
Functions / Load analysis
Functions / Consumable movements

Menu Bar

Drill Down / SUs

From a DO header, it is possible to display the Shipping Units of the DO.

Drill Down/Parcels

From a DO header, it is possible to display the parcels of the DO.

Drill Down/Transactions

From a DO header, it is possible to view the output movements.

Drill Down/DO line shortages

From a DO header, it is possible to view the DO lines on shortage.

Drill Down/Overview

Used to launch the load analysis for the selected DO.

The load analysis function is dependent on:
- the LA0 activity code for a DO with a status less than 4
- the LA2 activity code for a DO with a status less than 9
- the DO status that must be less than 9 (DO neither shipped nor completed).

The system considers that he load remaining to be received regarding the DO, i.e. the sum of the loads specific to:
- the DO header
- each line of the DO that is not or only partly shipped, while only considering the quantities that remain to be shipped and that are not deferred.
- Each output movement under progress associated with the DO
- Each validated unpacked output movement of the DO (preparation mode with declarative load preparation)
- Each unshipped DO parcel
- Each unshipped DO SU.

Further to a load analysis request
• a new analysis is created with the following characteristics:
- Flag to be kept to "no"
- Template (for information):
the template associated with the triplet (function, current site, current depositor) for a single-depositor function.
By default, or for a multi-depositor function, the template associated with the triplet (function, current site, depositor set to "blank".
By default, the template associated with the triplet (function, site set to "blank", depositor set to "blank").
By default, the template is left blank.
The calculation is launched for the analysis
The operator has access to the display screens of the load from which they will also have access to the information relating to the analysis (description and flag "to be kept") and be able to request the printing of the analysis results.

Drill Down / Transfer history

Used to declare 1 or n stock-issue movements of consumables within the framework of the delivery order.

This entry can take place at any moment, irrespective of the DO status.

It is necessary to enter various information to perform a consumable output 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 'OUTPUT' type
The quantity:quantity of the output movement

Since the output movement of the consumable is declared from a known entity, the carrier, transport method, customer and customer title information is, if need be, entered with that of the entity.

For an output movement, such information as supplier, supplier title, type of entity and 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

Functions / Load analysis

Used to launch the load analysis for the selected DO.

Further to a load analysis request
• a new analysis is created with the following characteristics:
- Flag to be kept to "no"
- Template (for information):
  ▪ the template associated with the triplet (function, current site, current depositor) for a single-depositor function
     ▪ By default or for a multi-depositor function, the template associated with the triplet (function, current site, depositor set to "blank".
  ▪ By default, the template associated with the triplet (function, site set to "blank", depositor set to "blank")
     ▪ By default, the template is left blank.
• The calculation is launched for the analysis
• The operator has access to the display screens of the load from which they will also have access to the information relating to the analysis (description and flag "to be kept") and be able to request the printing of the analysis results.

Functions / Consumable movements

Used to declare 1 or n stock-issue movements of consumables within the framework of the delivery order.

This entry can take place at any moment, irrespective of the DO status.

It is necessary to enter various information to perform a consumable output 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 'OUTPUT' type
The quantity:quantity of the output movement

Since the output movement of the consumable is declared from a known entity, the carrier, transport method, customer and customer title information is, if need be, entered with that of the entity.

For an output movement, such information as supplier, supplier title, type of entity and 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

Generic messages

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Movement code field error (line or header), record does not exist

An attempt has been made to enter a non-existent movement code.

Preparation mode field error, mandatory field

The preparation mode MUST be entered.

Carrier field error, record does not exist.

An attempt has been made to enter a non-existent carrier code.

Transport method error, record does not exist.

An attempt has been made to enter a non-existent transport method.

Country field error, record does not exist.

An attempt has been made to enter a non-existent country.

Code field error, record does not exist.

An attempt has been made to enter a non-existent customer code.

The error messages associated with the consumable movement declaration are the following: This name cannot contain the '/' character.

"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 entry type.

The entered movement code must necessarily be of 'OUTPUT' 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 output.

The consumable must necessarily be authorized for output for an output movement to be completed.

Tables used

SEEREFERTTO Refer to documentation Implementation