UCM Message/package response

To identify a message or package in the subject interchange, and to indicate that message's or package's acknowledgement or rejection (action taken), and to identify any error related to the UNH, UNT, UNO, and UNP segments. It can also identify errors related to the USA, USC, USD, USH, USR, UST, or USU security segments when they appear at the message or package level.

Position: 010 · Element: 0062 · Name: Message reference number · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 14 · Repeat: 1

Unique message reference assigned by the sender.

020 S009 Message identifier Composite (composite) Conditional 1

Position: 010 · Element: 0065 · Name: Message type · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 6 · Repeat: -

Code identifying a type of message and assigned by its controlling agency.

In UNSMs (United Nations Standard Messages), the representation is a6.

Position: 020 · Element: 0052 · Name: Message version number · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 3 · Repeat: -

Version number of a message type.

Position: 030 · Element: 0054 · Name: Message release number · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 3 · Repeat: -

Release number within the current message version number.

Position: 040 · Element: 0051 · Name: Controlling agency, coded · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 3 · Repeat: -

Code identifying a controlling agency.

Position: 050 · Element: 0057 · Name: Association assigned code · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 6 · Repeat: -

Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message.

Position: 060 · Element: 0110 · Name: Code list directory version number · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 6 · Repeat: -

Version number of the code list directory.

Position: 070 · Element: 0113 · Name: Message type sub-function identification · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 6 · Repeat: -

Code identifying a sub-function of a message type.

The code qualifies the message type data element (0065) to allow the recipient to identify a specific sub-function of a message.

Position: 030 · 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: 040 · Element: 0085 · Name: Syntax error, coded · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 3 · Repeat: 1

A code indicating the error detected.

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

Code identifying a service segment.

060 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: 070 · Element: 0800 · Name: Package reference number · Type: String (AN) · Requirement: Conditional · Min: 1 · Max: 35 · Repeat: 1

Unique package reference number assigned by the sender.

080 S020 Reference identification Composite (composite) Conditional 99

Position: 010 · Element: 0813 · Name: Reference qualifier · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 3 · Repeat: -

Code giving specific meaning to a reference identification number.

Position: 020 · Element: 0802 · Name: Reference identification number · Type: String (AN) · Requirement: Mandatory · Min: 1 · Max: 35 · Repeat: -

Reference number to identify a message, message group and/or interchange, which relates to the object.

Position: 090 · 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: 100 · 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.