EANCOM PART I |  |

Segment Layout | - UNG segment

UNG | - | C | 1 | - | FUNCTIONAL GROUP HEADER
Function:
To start, identify and specify a functional group.
EDIFACT
EAN
*
Description |
0038
FUNCTIONAL GROUP IDENTIFICATION
M |  | an..6
M
Identifies the type of message contained in the functional group, e.g. INVOIC |
S006
APPLICATION SENDER'S IDENTIFICATION
M |
M
| 0040
| Sender identification |
M |  | an..35
M
EAN location number (n13) |
| 0007
| Identification code qualifier |
C |  | an..4
R
*
14 = EAN International |
S007
APPLICATION RECIPIENT'S
M |
M
| 0044
| Recipient identification |
M |  | an..35
M
EAN location number (n13) |
| 0007
| Identification code qualifier |
C |  | an..4
R
*
14 = EAN International |
S004
DATE/TIME OF PREPARATION
M |
M
| 0017
| Date |
M |  | n6
M
YYMMDD |
| 0019
| Time |
M |  | n4
M
HHMM |
0048
Functional group reference number
M |  | an..14
M
Unique reference identifying the functional group. Created by the interchange sender. |
0051
Controlling agency
M |  | an..2
M
*
EN = EAN International UN = UN/ECE/TRADE/WP.4, United Nations Standard Messages (UNSM) |
S008
MESSAGE VERSION
M |
M
| 0052
| Message type version number |
M |  | an..3
M
D = Draft directory |
| 0054
| Message type release number |
M |  | an..3
M
The value of this data element depends on the message type. |
| 0057
| Association assigned code |
C |  | an..6
R
The value of this data element depends on the message type. |
0058
Application password
C |  | an..14
D
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.

(c) Copyright EAN 1997 |