-

C

1

-

 

Function:

 

To head, identify and specify a functional group.

EDIFACT

Description

0038

Functional group identification

M

an..6

Identification of a message contained in the functional group, e.g. INVOIC.

S006

APPLICATION SENDER'S IDENTIFICATION

M

0040

Sender identification

M

an..35

GLN (n13)

Partner identification code qualifier

C

an..4

=

GS1

S007

APPLICATION RECIPIENT'S IDENTIFICATION

M

0044

Recipient's identification

M

an..35

GLN (n13)

Partner identification code qualifier

C

an..4

=

GS1

S004

DATE/TIME OF PREPARATION

M

0017

Date of preparation

M

n6

YYMMDD

0019

Time of preparation

M

n4

HHMM

0048

Functional group reference number

M

an..14

Unique reference identifying the functional group. Created by the interchange sender.

Controlling agency

M

an..2

=

UN/CEFACT

S008

MESSAGE VERSION

M

Message version number

M

an..3

=

Draft version/UN/EDIFACT Directory

Message release number

M

an..3

The value of this data element depends on the message type.

=

Release 2001 - B

Association assigned code

C

an..6

The value of this data element depends on the message type.

0058

Application password

C

an..14

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'