Delivery Note

• Number (field DLNNUM)

• Inter-site (field INSFLG)

Specifies the DN type. If the "inter-site" is activated, this means that the DN has been generated within the framework of an "inter-site" round.

• Date (field DLNDAT)

Creation date of the Delivery Note.

• Time (field DLNTIM)

Creation time of the Delivery Note.

• Final DN (field DLNSTA)

• Upd DN (field TDNSTA)

• CN no (field CANNUM)

• CR no (field NTRNUM)

• Client (field ORDCLT)

• Customer reference (field CLTORDREF)

• Number (field ORDNUM)

• Date (field ORDDAT)

• Reference (field ORDREF)

• Picking mode (field PMD)

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

• Preparation area (field PKZ)

• Partial delivery (field PTLPIK)

• DO no (field DLONUM)

• Reference (field REF)

• Wave no (field WAVNUM)

• Planned delivery (field EXPDLVDAT)

• field EXPDLVTIM

• Shipment (field SHPDAT)

Shipment date for the entity.

• field SHPTIM

Shipment time for the entity.

• Report (field DLNEDT)

• Language (field EDTLAN)

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

• Code (field DLVCLT)

• Country (field DLVCRY)

• field DLVCRYNAM

• field DLVNAM

• field DLVADD

• Postal code (field DLVPOS)

• City (field DLVCTY)

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

• Telephone (field DLVTEL)

• Fax (field DLVFAX)

• Notes (field DLVREM)

• Code (field INVCLT)

• Country (field INVCRY)

• field INVCRYNAM

• field INVNAM

• field INVADD

• Postal code (field INVPOS)

• City (field INVCTY)

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

• Telephone (field INVTEL)

• Fax (field INVFAX)

• Notes (field INVREM)

• Shipment site (field SHPFCY)

• Generic round (field GDR)

• Round no. (field QYMNUM)

• Round position (field DRNPST)

• Date (field DRNDAT)

• field DRNTIM

• Dock (field DRNSTO)

• field DRNSLO

• Destination site (field DENFCY)

Destination site of the "inter-site" DN.

• Carrier (field CRR)

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

• field CRRDES

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

• field CRMDES

• Carriage reference (field CRRREF)

• Transport type (field CGT)

• Delivery area (field DLVARE)

• Freight Charge (field CRGAMT)

Transport cost of the DN generated upon shipment confirmation or when recalculating the transport cost.

• field CURSYM

• No. of parcels (field NBRPRC)

• No SU (field NBRSHP)

• Nr of lines DO (field NBRLIG)

• Weight (field WEI)

Net weight. Four digits after the comma

• field WEILIB

• Volume (field VOL)

• field VOLLIB

• Linear meters (field LMT)

Linear metering of an entity.

• field LMTLIB

• EDI management (field EDISTA)

Used to know if the transport EDI is managed for the DN and, if this is the case, what its progress status is.

The possible values are:

'Pending': DN managed by the transport EDI and not having received its last EDI message

'Completed': DN managed by the transport EDI and having received its last EDI message

'Not concerned': DN not managed by the transport EDI

• field DLNNUM2

The magnifier is used to display all the EDI messages already received by the processed DN.

• EDI level (field TYPEDI)

Mentions the type of entity managed in the EDI messages.

The processed entity can be either the CR, the DN, the SU or the parcel.

• field NBRPRCEDI2

• Number (field EDHNUM)

Number of the EDI message.

Numerical sequence automatically assigned by the system

upon creation of an EDI message, either via an interface or manually. This number is an information specific to

the site, all depositors included. This information features a unique access key

to the EDI message.

• Entity (field TYPNUM2)

Type and number of the event processed in the EDI message.

• Severity (field NUMERR)

Specifies a hierarchy on the reason codes based on the gravity.

For instance: a 'compliant' reason code has a gravity code equal to 0.

• Status code (field COD1)

It describes the situation of the entity (removed, delivery under progress, etc.)

Statuses are defined for all the carriers and their codification is defined upon each interchange agreement with the carrier.

• Phase (field ORN)

The phase code stipulates the order in the message reception.

It enables the system to ensure that, upon return message integration, the phase code is higher thant the phase code of those messages already received for the processed entity.

• Reason code (field COD2)

The reason code provides a justification or an explanation for a status (eg. missing, damaged, etc.)

It is defined upon interchange agreement with the carrier.

• Event date (field CLTDAT)

Date and time of the event processed in the EDI message.

Upon integration of the EDI messages, consistency checks are performed between the event dates and times of the new message and those messages already received for the entity.

The event date and time of the new message must be prior to those of the already received messages.

• field CLTTIM

• End (field LASREC)

Used to specify whether or not the EDI message is the last one to be received from the pairs (status code, reason code) for the processed entity.

The possible values are:

Yes: last message to be received for the entity

No: the system accepts to receive other message for the entity

• Processing date (field CRRDAT)

Processing date and time of the event described in the EDI message.

• field CRRTIM

• Next message (field NEXDAT)

Date and time of the next message to be received for the entity processed in the EDI message

• field NEXTIM