UNG |
- |
C |
1 |
- |
FUNCTIONAL GROUP
HEADER |
|
Function: |
To start, identify and
specify a functional group. |
|
|
|
|
|
|
|
FUNCTIONAL GROUP
IDENTIFICATION |
|
|
|
|
Identifies the type of
message contained in the functional group, e.g.
INVOIC |
|
|
|
APPLICATION SENDER'S
IDENTIFICATION |
|
|
|
|
|
|
|
|
|
|
EAN location number (n13) |
|
|
|
|
Identification code
qualifier |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
EAN location number (n13) |
|
|
|
|
Identification code
qualifier |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional group
reference number |
|
|
|
|
Unique reference
identifying the functional group. Created by the
interchange sender. |
|
|
|
|
|
|
|
EN = EAN International
UN = UN/ECE/TRADE/WP.4, United Nations Standard
Messages (UNSM) |
|
|
|
|
|
|
|
|
|
|
Message type version
number |
|
|
|
|
|
|
|
|
Message type release
number |
|
|
|
|
|
The value of this data
element depends on the message type. |
|
|
|
|
Association assigned code |
|
|
|
|
|
The value of this data
element depends on the message type. |
|
|
|
|
|
|
|
The use of this data
element depends on agreements between the trading
partners. |
|
|
Segment Notes: |
Within EANCOM the use of
the UNG..UNE segments is not recommended as the
grouping of same message types is not considered
to add significant value to simply including
multiple same message types within one
interchange, i.e. between UNB..UNZ. |
|