| Pos |
|
Tag |
Name |
S |
R |
Repr |
|
Notes |
| 010 |
|
|
| MESSAGE REFERENCE NUMBER |
| Unique message reference assigned by the sender. |
|
M |
1 |
an..14 |
|
2 |
| 020 |
|
|
| MESSAGE IDENTIFIER |
| Identification of the type, version, etc. of the message being interchanged. |
|
M |
1 |
|
|
1,2 |
| |
|
|
| Message type |
| Code identifying a type of message and assigned by its controlling agency. |
|
M |
1 |
an..6 |
|
|
| |
|
|
| 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 |
|
|
| |
|
|
| Controlling agency, coded |
| Code identifying a controlling agency. |
|
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 |
|
|
| |
|
|
| Code list directory version number |
| Version number of the code list directory. |
|
C |
1 |
an..6 |
|
|
| |
|
|
| Message type sub-function identification |
| Code identifying a sub-function of a message type. |
|
C |
1 |
an..6 |
|
|
| 030 |
|
|
| COMMON ACCESS REFERENCE |
| Reference serving as a key to relate all subsequent transfers of data to the same business case or file. |
|
C |
1 |
an..35 |
|
|
| 040 |
|
|
| STATUS OF THE TRANSFER |
| Statement that the message is one in a sequence of transfers relating to the same topic. |
|
C |
1 |
|
|
|
| |
|
|
| Sequence of transfers |
| Number assigned by the sender indicating the transfer sequence of a message related to the same topic. The message could be an addition or a change to an earlier transfer related to the same topic. |
|
M |
1 |
n..2 |
|
|
| |
|
|
| First and last transfer |
| Indication used for the first and last message in a sequence of messages related to the same topic. |
|
C |
1 |
a1 |
|
|
| 050 |
|
|
| MESSAGE SUBSET IDENTIFICATION |
| Identification of a message subset by its identifier, version, release and source. |
|
C |
1 |
|
|
1 |
| |
|
|
| Message subset identification |
| Coded identification of a message subset, assigned by its controlling agency. |
|
M |
1 |
an..14 |
|
|
| |
|
|
| Message subset version number |
| Version number of the message subset. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Message subset release number |
| Release number within the message subset version number. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Controlling agency, coded |
| Code identifying a controlling agency. |
|
C |
1 |
an..3 |
|
|
| 060 |
|
|
| MESSAGE IMPLEMENTATION GUIDELINE IDENTIFICATION |
| Identification of a message implementation guideline by its identifier, version, release and source. |
|
C |
1 |
|
|
1 |
| |
|
|
| Message implementation guideline identification |
| Coded identification of the message implementation guideline, assigned by its controlling agency. |
|
M |
1 |
an..14 |
|
|
| |
|
|
| Message implementation guideline version number |
| Version number of the message implementation guideline. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Message implementation guideline release number |
| Release number within the message implementation guideline version number. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Controlling agency, coded |
| Code identifying a controlling agency. |
|
C |
1 |
an..3 |
|
|
| 070 |
|
|
| SCENARIO IDENTIFICATION |
| Identification of a scenario. |
|
C |
1 |
|
|
|
| |
|
|
| Scenario identification |
| Code identifying scenario. |
|
M |
1 |
an..14 |
|
|
| |
|
|
| Scenario version number |
| Version number of a scenario. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Scenario release number |
| Release number within the scenario version number. |
|
C |
1 |
an..3 |
|
|
| |
|
|
| Controlling agency, coded |
| Code identifying a controlling agency. |
|
C |
1 |
an..3 |
|
|
