UCI 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.

Position: 010 · Element: 0020 · Name: Interchange control reference · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 14 · Repeat: 1

Unique reference assigned by the sender to an interchange.

020 S002 Interchange sender Composite (composite) Mandatory 1

Position: 010 · Element: 0004 · Name: Interchange sender identification · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 35 · Repeat: -

Name or coded identification of the sender of the interchange.

Organisation code or name as agreed between interchange partners.

If coded representation is used, its source may be specified by the qualifier in data element 0007.

Position: 020 · Element: 0007 · Name: Identification code qualifier · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 4 · Repeat: -

Qualifier referring to the identification code.

A qualifier code may refer to an organisation identification as in ISO 6523.

Position: 030 · Element: 0008 · Name: Interchange sender internal identification · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 35 · Repeat: -

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.

Position: 040 · Element: 0042 · Name: Interchange sender internal sub-identification · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 35 · Repeat: -

Sub-level of sender internal identification, when further sub-level identification is required.

030 S003 Interchange recipient Composite (composite) Mandatory 1

Position: 010 · Element: 0010 · Name: Interchange recipient identification · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 35 · Repeat: -

Name or coded identification of the recipient of the interchange.

Organisation code or name as agreed between interchange partners.

If coded representation is used, its source may be specified by the qualifier in data element 0007.

Position: 020 · Element: 0007 · Name: Identification code qualifier · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 4 · Repeat: -

Qualifier referring to the identification code.

A qualifier code may refer to an organisation identification as in ISO 6523.

Position: 030 · Element: 0014 · Name: Interchange recipient internal identification · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 35 · Repeat: -

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.

Position: 040 · Element: 0046 · Name: Interchange recipient internal sub-identification · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 35 · Repeat: -

Sub-level of recipient internal identification, when further sub-level identification is required.

Position: 040 · Element: 0083 · Name: Action, coded · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 3 · Repeat: 1

A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange, or indication of interchange receipt.

Position: 050 · Element: 0085 · Name: Syntax error, coded · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 3 · Repeat: 1

A code indicating the error detected.

Position: 060 · Element: 0135 · Name: Service segment tag, coded · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 3 · Repeat: 1

Code identifying a service segment.

070 S011 Data element identification Composite (composite) Conditional 1

Position: 010 · Element: 0098 · Name: Erroneous data element position in segment · Type: Numeric (N) · Requirement: Mandatory · Min: 1 · Max: 3 · Repeat: -

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.

Position: 020 · Element: 0104 · Name: Erroneous component data element position · Type: Numeric (N) · Requirement: Conditional · Min: 1 · Max: 3 · Repeat: -

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.

Position: 030 · Element: 0136 · Name: Erroneous data element occurrence · Type: Numeric (N) · Requirement: Conditional · Min: 1 · Max: 6 · Repeat: -

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.

Position: 080 · Element: 0534 · Name: Security reference number · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 14 · Repeat: 1

Unique reference number assigned by the security originator to a pair of security header and security trailer groups.

The value shall be arbitrarily assigned, but the same value shall not be used more than once within the same EDIFACT structure, I.e. interchange, group, message or package.

Position: 090 · Element: 0138 · Name: Security segment position · Type: Numeric (N) · Requirement: Conditional · Min: 1 · Max: 6 · Repeat: 1

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.