Version History
Version | Notes |
0.6 2024-02-22 | Added notes. |
0.5 2024-02-20 | Tiny fixes. |
0.4 2017-01-27 | 4th draft |
0.3 2016-12-12 | 3rd draft |
0.2 2016-11-08 | 2nd draft version |
0.1 2016-11-04 | Draft, for demonstration purposes |
General
Subset definition
Message implementation guideline for the despatch advice messages sent to Company X using EDIFACT DESADV D.00A message format.
Functional definition
A message specifying details for goods despatched or ready for
despatch under agreed conditions.
The United Nations Despatch Advice Message serves both as a
specification for Delivery Despatch Advice and also as a
Returns Despatch Advice message. Throughout this document, the
reference to 'Despatch Advice' may be interpreted as conveying
the wider meaning of 'Delivery Despatch Advice/Returns Despatch
Advice'.
Field of application
The Despatch advice message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
Subset abbreviations
Default statuses
- M
- Mandatory
- C
- Conditional
Custom statuses for conditional items
- R
- Required (conditional status changed to mandatory)
- A
- Advised / Recommended
- D
- Dependent (Mandatory when certain conditions apply)
- O
- Optional
- X
- Excluded / Not used
Status and repeat examples
- M1
- Mandatory, must be repeated exactly once
- C99
- Conditional, can be repeated at most 99 times
- R5
- Required, must be repeated atleast once and at most 5 times
Data type examples
- an..35
- alphanumeric value, at most 35 characters
- an3
- alphanumeric value, exactly 3 characters
- n..9
- numeric value, at most 9 numbers
- n3
- numeric value, exactly 3 numbers
- a1
- alphabetic characters, exactly 1 character
Message Structure
This is an overview of segments and segment groups used in scenarios covered by this message implementation guideline.
Tag | Name | St | Rp |
UNH | MESSAGE HEADER | M | 1 |
BGM | BEGINNING OF MESSAGE | M | 1 |
DTM | DATE/TIME/PERIOD | R | 2 |
GRP1 | RFF-DTM | C | 10 |
-RFF | REFERENCE | M | 1 |
-DTM | DATE/TIME/PERIOD | C | 1 |
GRP2 | NAD | R | 99 |
-NAD | NAME AND ADDRESS | M | 1 |
GRP10 | CPS-GRP11-GRP17 | R | 9999 |
-CPS | CONSIGNMENT PACKING SEQUENCE | M | 1 |
-GRP11 | PAC-MEA | R | 9999 |
--PAC | PACKAGE | M | 1 |
--MEA | MEASUREMENTS | R | 10 |
-GRP17 | LIN-QTY-GRP18 | R | 9999 |
--LIN | LINE ITEM | M | 1 |
--QTY | QUANTITY | R | 10 |
--GRP18 | RFF-DTM | A | 99 |
---RFF | REFERENCE | M | 1 |
---DTM | DATE/TIME/PERIOD | C | 1 |
UNT | MESSAGE TRAILER | M | 1 |
Message Segments
UNH | MESSAGE HEADER | M1 |
A service segment starting and uniquely identifying a message. The message type code for the Despatch advice message is DESADV.
Tag | Name | St | Type | Notes |
0062 | MESSAGE REFERENCE NUMBER | M | an..14 | |
S009 | MESSAGE IDENTIFIER | M | ||
0065 | Message type | M | an..6 |
|
0052 | Message version number | M | an..3 |
|
0054 | Message release number | M | an..3 |
|
0051 | Controlling agency, coded | M | an..3 |
|
- Example:
- UNH+1+DESADV:D:00A:UN'
BGM | BEGINNING OF MESSAGE | M1 |
A segment for unique identification of the Despatch Advice document, by means of its name and its number.
Tag | Name | St | Type | Notes |
C002 | DOCUMENT/MESSAGE NAME | R | ||
1001 | Document name code | R | an..3 |
|
C106 | DOCUMENT/MESSAGE IDENTIFICATION | R | ||
1004 | Document identifier | R | an..35 |
- Example:
- BGM+351+123456'
DTM | DATE/TIME/PERIOD | R2 |
Date/time/period related to the whole message. The DTM segment must be specified at least once to identify the Despatch Advice date.
Tag | Name | St | Type | Notes |
C507 | DATE/TIME/PERIOD | M | ||
2005 | Date or time or period function code qualifier | M | an..3 |
|
2380 | Date or time or period value | R | an..35 | Pattern: [0-9]{8} Example: 20161101 |
2379 | Date or time or period format code | R | an..3 |
|
- Example:
- DTM+137:20150515:102'
GRP1 | RFF - DTM | C10 |
A group of segments giving references where necessary, their dates relating to the whole message, e.g. contract number.
- Remarks
- Provide references primarily on a header level.
RFF | REFERENCE | M1 |
A segment for referencing documents relating to the whole despatch advice message, e.g. purchase orders, delivery instructions, import/export license.
Tag | Name | St | Type | Notes |
C506 | REFERENCE | M | ||
1153 | Reference function code qualifier | M | an..3 |
|
1154 | Reference identifier | R | an..25 |
GRP1 | RFF - DTM | C10 |
DTM | DATE/TIME/PERIOD | C1 |
Date/time/period from the referred document.
Tag | Name | St | Type | Notes |
C507 | DATE/TIME/PERIOD | M | ||
2005 | Date or time or period function code qualifier | M | an..3 | |
2380 | Date or time or period value | R | an..35 | Pattern: [0-9]{8} Example: 20161101 |
2379 | Date or time or period format code | R | an..3 |
|
GRP2 | NAD | R99 |
A group of segments identifying names, addresses, locations, and required supporting documents relevant to the whole Despatch Advice.
- Remarks
- Here comes segment group specific remarks.
NAD | NAME AND ADDRESS | M1 |
A segment for identifying names, addresses, and their functions relevant to the whole Despatch Advice. Identification of the parties involved is recommended for the Despatch Advice message, and is to be given in the NAD segment. It is recommended that where possible, only the coded form of the party ID should be specified, e.g. the buyer and seller are known to each other, thus only the coded ID is required. The consignee or delivery address may vary and would have to be clearly specified, preferably in structured format.
Tag | Name | St | Type | Notes |
3035 | PARTY FUNCTION CODE QUALIFIER | M | an..3 |
Here comes element specific remarks. |
C082 | PARTY IDENTIFICATION DETAILS | R | Here comes composite specific remarks. | |
3039 | Party identifier | M | an..15 | |
1131 | Code list identification code | C | an..3 |
|
3055 | Code list responsible agency code | C | an..3 |
|
C058 | NAME AND ADDRESS | X | Not used | |
C080 | PARTY NAME | R | ||
3036 | Party name | M | an..35 | |
3036 | Party name | C | an..35 |
- Example:
- NAD+CZ+5678765::92++ZXC Consignor'
- Remarks
- Here comes segment specific remarks.
GRP10 | CPS - GRP11 - GRP17 | R9999 |
A group of segments providing details of all package levels and of the individual despatched items contained in the consignment. This segment group provides the capability to give the hierarchical packing relationships. The group defines a logical top-down order structure. The lowest level package information of the hierarchy is followed by the detail product information.
CPS | CONSIGNMENT PACKING SEQUENCE | M1 |
A segment identifying the sequence in which packing of the consignment occurs, e.g. boxes loaded onto a pallet.
Tag | Name | St | Type | Notes |
7164 | HIERARCHICAL STRUCTURE LEVEL IDENTIFIER | M | an..35 | |
7166 | HIERARCHICAL STRUCTURE PARENT IDENTIFIER | X | Not used | |
7075 | PACKAGING LEVEL CODE | C | an..3 |
|
- Example:
- CPS+123456789987654321++1'
GRP11 | PAC - MEA | R9999 |
A group of segments identifying packaging, physical dimensions, marks and numbers, quantities, date and time information, handling information and information about packing at this level.
PAC | PACKAGE | M1 |
A segment specifying the number and type of the packages/physical units and the physical type of packaging for the despatched goods.
Tag | Name | St | Type | Notes |
7224 | PACKAGE QUANTITY | R | n..8 |
- Example:
- PAC+1'
GRP11 | PAC - MEA | R9999 |
MEA | MEASUREMENTS | R10 |
A segment specifying physical measurements of the packages/physical units described in the PAC segment.
Tag | Name | St | Type | Notes |
6311 | MEASUREMENT ATTRIBUTE CODE | M | an..3 |
|
C502 | MEASUREMENT DETAILS | R | ||
6313 | Measured attribute code | R | an..3 |
|
C174 | VALUE/RANGE | R | ||
6411 | Measurement unit code | M | an..3 | |
6314 | Measurement value | R | an..18 |
- Example:
- MEA+AAE+ABJ+LTR:500'
GRP17 | LIN - QTY - GRP18 | R9999 |
A group of segments providing details of the individual despatched items.
LIN | LINE ITEM | M1 |
A segment identifying the product being despatched. All other segments in the detail section following the LIN segment refer to that line item.
Tag | Name | St | Type | Notes |
1082 | LINE ITEM IDENTIFIER | R | an..6 | |
1229 | ACTION REQUEST/NOTIFICATION DESCRIPTION CODE | X | Not used | |
C212 | ITEM NUMBER IDENTIFICATION | R | ||
7140 | Item identifier | R | an..35 | |
7143 | Item type identification code | R | an..3 |
|
- Example:
- LIN+1++123456:SA'
GRP17 | LIN - QTY - GRP18 | R9999 |
QTY | QUANTITY | R10 |
A segment to give quantity information concerning the product.
Tag | Name | St | Type | Notes |
C186 | QUANTITY DETAILS | M | ||
6063 | Quantity type code qualifier | M | an..3 |
|
6060 | Quantity | M | an..35 | |
6411 | Measurement unit code | R | an..3 |
- Example:
- QTY+12:200:PC'
GRP18 | RFF - DTM | A99 |
A group of segments to give reference numbers and dates.
RFF | REFERENCE | M1 |
A segment identifying documents related to the line item.
Tag | Name | St | Type | Notes |
C506 | REFERENCE | M | ||
1153 | Reference function code qualifier | M | an..3 |
|
1154 | Reference identifier | R | an..35 | |
1156 | Document line identifier | R | an..6 |
- Example:
- RFF+CO:1234:10'
GRP18 | RFF - DTM | A99 |
DTM | DATE/TIME/PERIOD | C1 |
A segment for date/time/period relative to the referred document.
Tag | Name | St | Type | Notes |
C507 | DATE/TIME/PERIOD | M | ||
2005 | Date or time or period function code qualifier | M | an..3 |
|
2380 | Date or time or period value | R | an..35 | Pattern: [0-9]{8} Example: 20161101 |
2379 | Date or time or period format code | R | an..3 |
|
- Example:
- DTM+171:20150513:102'
UNT | MESSAGE TRAILER | M1 |
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
Tag | Name | St | Type | Notes |
0074 | NUMBER OF SEGMENTS IN A MESSAGE | M | n..10 | |
0062 | MESSAGE REFERENCE NUMBER | M | an..14 |
- Example:
- UNT+19+1'