|
|
| INTERCHANGE RESPONSE |
 |
|
To identify the subject interchange, to indicate interchange receipt, to indicate acknowledgement or rejection (action taken) of the UNA, UNB and UNZ segments, and to identify any error related to these segments. It can also identify errors related to the USA, USC, USD, USH, USR, UST, or USU security segments when they appear at the interchange level. Depending on the action code, it may also indicate the action taken on the groups, messages, and packages within that interchange.
Dependency Notes:
1. D5(060, 050) If first, then all
2. D5(070, 060, 050) If first, then all
3. D5(080, 060, 050, 090) If first, then all
4. D5(090, 080, 060, 050) If first, then all
Notes:
5. 0135, may only contain the values UNA, UNB, UNZ, USA, USC, USD, USH, USR, UST, or USU.
6. This data element shall be present when reporting an error in a security segment. |
|
| Pos |
|
Tag |
Name |
S |
R |
Repr |
|
Notes |
| 010 |
|
|
| INTERCHANGE CONTROL REFERENCE |
| Unique reference assigned by the sender to an interchange. |
|
M |
1 |
an..14 |
|
|
| 020 |
|
|
| INTERCHANGE SENDER |
| Identification of the sender of the interchange. |
|
M |
1 |
|
|
|
| |
|
|
| Interchange sender identification |
| Name or coded identification of the sender of the interchange. |
|
M |
1 |
an..35 |
|
|
| |
|
|
| Identification code qualifier |
| Qualifier referring to the identification code. |
|
C |
1 |
an..4 |
|
|
| |
|
|
| Interchange sender internal identification |
| Identification (for example, a division, branch or computer system/process) specified by the sender of interchange, to be included if agreed, by the recipient in response interchanges, to facilitate internal routing. |
|
C |
1 |
an..35 |
|
|
| |
|
|
| Interchange sender internal sub-identification |
| Sub-level of sender internal identification, when further sub-level identification is required. |
|
C |
1 |
an..35 |
|
|
| 030 |
|
|
| INTERCHANGE RECIPIENT |
| Identification of the recipient of the interchange. |
|
M |
1 |
|
|
|
| |
|
|
| Interchange recipient identification |
| Name or coded identification of the recipient of the interchange. |
|
M |
1 |
an..35 |
|
|
| |
|
|
| Identification code qualifier |
| Qualifier referring to the identification code. |
|
C |
1 |
an..4 |
|
|
| |
|
|
| Interchange recipient internal identification |
| Identification (for example, a division, branch or computer system/process) specified by the recipient of interchange, to be included if agreed, by the sender in response interchanges, to facilitate internal routing. |
|
C |
1 |
an..35 |
|
|
| |
|
|
| Interchange recipient internal sub-identification |
| Sub-level of recipient internal identification, when further sub-level identification is required. |
|
C |
1 |
an..35 |
|
|
| 040 |
|
|
| ACTION, CODED |
| A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange, or indication of interchange receipt. |
|
M |
1 |
an..3 |
|
|
| 050 |
|
|
| SYNTAX ERROR, CODED |
| A code indicating the error detected. |
|
C |
1 |
an..3 |
|
1,2,3,4 |
| 060 |
|
|
| SERVICE SEGMENT TAG, CODED |
| Code identifying a service segment. |
|
C |
1 |
an..3 |
|
1,2,3,4,5 |
| 070 |
|
|
| DATA ELEMENT IDENTIFICATION |
| Identification of the position for an erroneous data element. This can be the position of a stand-alone or composite data element in the definition of a segment or a component data element in the definition of a composite data element. |
|
C |
1 |
|
|
2 |
| |
|
|
| Erroneous data element position in segment |
| The numerical count position of the stand-alone or composite data element in error. The segment code and each following stand-alone or composite data element defined in the segment description shall cause the count to be incremented. The segment tag has position number 1. |
|
M |
1 |
n..3 |
|
|
| |
|
|
| Erroneous component data element position |
| The numerical count position of the component data element in error. Each component data element position defined in the composite data element description shall cause the count to be incremented. The count starts at 1. |
|
C |
1 |
n..3 |
|
|
| |
|
|
| Erroneous data element occurrence |
| The numerical occurrence of the repeating stand-alone or composite data element in error. Each occurrence (as indicated by the repetition separator) shall cause the count to be incremented. The count starts at 1. |
|
C |
1 |
n..6 |
|
|
| 080 |
|
|
| SECURITY REFERENCE NUMBER |
| Unique reference number assigned by the security originator to a pair of security header and security trailer groups. |
|
C |
1 |
an..14 |
|
3,4,6 |
| 090 |
|
|
| SECURITY SEGMENT POSITION |
| The numerical count position of a specific security segment that is within the actual received security header/trailer segment group pair, identified by its security reference number. The numbering starts with, and includes, the USH segment as segment number 1. To identify a security segment that contains an error, this is the numerical count position of that security segment. To report that a security segment is missing, this is the numerical count position of the last security segment that was processed before the position where the missing security segment was expected to be. A missing security segment group is denoted by identifying the first segment in the security segment group as missing. |
|
C |
1 |
n..6 |
|
3,4,6 |
