|
|
|
| |
Function: |
| |
To head, identify and specify a functional group. |
|
| |
|
EAN |
* |
|
|
|
|
Functional group identification |
|
|
M |
|
|
Identification of a message contained in the functional group, e.g. INVOIC. |
|
|
|
|
APPLICATION SENDER'S IDENTIFICATION |
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
Partner identification code qualifier |
|
|
R |
* |
|
|
|
|
APPLICATION RECIPIENT'S IDENTIFICATION |
|
|
M |
|
|
|
|
|
Recipient's identification |
|
|
M |
|
|
|
|
|
Partner identification code qualifier |
|
|
R |
* |
|
|
|
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
|
M |
|
|
|
|
|
Functional group reference number |
|
|
M |
|
|
Unique reference identifying the functional group. Created by the interchange sender. |
|
|
|
|
|
M |
* |
|
|
|
|
|
M |
|
|
|
|
|
|
M |
* |
|
|
|
|
|
M |
* |
|
|
|
|
Association assigned code |
|
|
R |
|
|
The value of this data element depends on the message type. |
|
|
|
|
|
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 should not be used for grouping of multiple message types in the same interchange as this is not considered good practice. However, they can be used by organisations to create their own identifiable application level envelopes, which can be addressed from the originating department to a department in the recipient's system, e.g. to group multiple issuers in one transmission file with invoices.
UNG+INVOIC+5412345678908:14+8798765432106:14+020102:1000+471123+UN+D:01B:EAN010' |
|
