|
|
| GROUP HEADER |
 |
|
To head, identify and specify a group of messages and/or packages, which may be used for internal routing and which may contain one or more message types and/or packages.
Dependency Notes:
1. D2(010,060,070) All or none
Notes:
(010,060,070) This data element is only used if the following conditions apply:
i) the group contains messages only, and
ii) the messages are of a single message type.
040 S004, if S004 is not present in UNG, the date and time of preparation is the same as indicated for the interchange in S004 in UNB.
(010,060,070) This data element will be deleted from the UNG segment in the next version of the standard. Therefore its use in UNG is not recommended.
(020,030,050) The combination of the values carried in data elements S006, S007 and 0048 shall be used to identify uniquely the group within its interchange, for the purpose of acknowledgement. |
|
| Pos |
|
Tag |
Name |
S |
R |
Repr |
|
Notes |
| 010 |
|
|
| MESSAGE GROUP IDENTIFICATION |
| Identification of the single message type in the group. |
|
C |
1 |
an..6 |
|
1,2,4 |
| 020 |
|
|
| APPLICATION SENDER IDENTIFICATION |
| Sender identification of for example a division, branch or application computer system/process. |
|
C |
1 |
|
|
5 |
| |
|
|
| Application sender identification |
| Name or coded identification of the application sender (for example, a division, branch or computer system/process). |
|
M |
1 |
an..35 |
|
|
| |
|
|
| Identification code qualifier |
| Qualifier referring to the identification code. |
|
C |
1 |
an..4 |
|
|
| 030 |
|
|
| APPLICATION RECIPIENT IDENTIFICATION |
| Recipient identification of for example a division, branch or application computer system/process. |
|
C |
1 |
|
|
5 |
| |
|
|
| Application recipient identification |
| Name or coded identification of the application recipient (for example, a division, branch or computer system/process). |
|
M |
1 |
an..35 |
|
|
| |
|
|
| Identification code qualifier |
| Qualifier referring to the identification code.. |
|
C |
1 |
an..4 |
|
|
| 040 |
|
|
| DATE AND TIME OF PREPARATION |
| Date and time of preparation of the interchange. |
|
C |
1 |
|
|
3 |
| |
|
|
| Date |
| Local date when an interchange or a group was prepared. |
|
M |
1 |
n8 |
|
|
| |
|
|
| Time |
| Local time of day when an interchange or a group was prepared. |
|
M |
1 |
n4 |
|
|
| 050 |
|
|
| GROUP REFERENCE NUMBER |
| Unique reference number for the group within an interchange. |
|
M |
1 |
an..14 |
|
5 |
| 060 |
|
|
| CONTROLLING AGENCY, CODED |
| Code identifying a controlling agency. |
|
C |
1 |
an..3 |
|
1,2,4 |
| 070 |
|
|
| MESSAGE VERSION |
| Specification of the version and release numbers of all of the messages of a single type in the group. |
|
C |
1 |
|
|
1,2,4 |
| |
|
|
| Message version number |
| Version number of a message type. |
|
M |
1 |
an..3 |
|
|
| |
|
|
| Message release number |
| Release number within the current message version number. |
|
M |
1 |
an..3 |
|
|
| |
|
|
| Association assigned code |
| Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message. |
|
C |
1 |
an..6 |
|
|
| 080 |
|
|
| APPLICATION PASSWORD |
| Password to the recipient's division, department or sectional application system/process. |
|
C |
1 |
an..14 |
|
|
