Try it now Login

UN/EDIFACT SERVICE_V4 CONTRL Message

Review the CONTRL segment sequence, mandatory fields, repeat counts and valid codes for the SERVICE_V4 EDIFACT directory.

Jump to Segment

UNH

UCI

UCM

UCS

UCD

UCF

UCM

UCS

UCD

UNT

UNH To head, identify and specify a message. (Max 1) Required

S009 – Identification of the type, version, etc. of the message being interchanged.
- 0065 – Code identifying a type of message and assigned by its controlling agency.
  Type: an, Max Length: 6 (Required)
- 0052 – Version number of a message type.
  Type: an, Max Length: 3 (Required)
- 0054 – Release number within the current message version number.
  Type: an, Max Length: 3 (Required)
- 0051 – Code identifying a controlling agency.
  Type: an, Max Length: 3 (Required)
- 0057 – Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message.
  Type: an, Max Length: 6
- 0110 – Version number of the code list directory.
  Type: an, Max Length: 6
- 0113 – Code identifying a sub-function of a message type.
  Type: an, Max Length: 6
S010 – Statement that the message is one in a sequence of transfers relating to the same topic.
- 0070 – 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.
  Type: n, Max Length: 2 (Required)
- 0073 – Indication used for the first and last message in a sequence of messages related to the same topic.
  Type: a, Max Length:
S016 – Identification of a message subset by its identifier, version, release and source.
- 0115 – Coded identification of a message subset, assigned by its controlling agency.
  Type: an, Max Length: 14 (Required)
- 0116 – Version number of the message subset.
  Type: an, Max Length: 3
- 0118 – Release number within the message subset version number.
  Type: an, Max Length: 3
- 0051 – Code identifying a controlling agency.
  Type: an, Max Length: 3
S018 – Identification of a scenario.
- 0127 – Code identifying scenario.
  Type: an, Max Length: 14 (Required)
- 0128 – Version number of a scenario.
  Type: an, Max Length: 3
- 0130 – Release number within the scenario version number.
  Type: an, Max Length: 3
- 0051 – Code identifying a controlling agency.
  Type: an, Max Length: 3
0062 – Unique message reference assigned by the sender.
Type: an, Max Length: 14 (Required)
0068 – Reference serving as a key to relate all subsequent transfers of data to the same business case or file.
Type: an, Max Length: 35

UCI 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. (Max 1) Required

S002 – Identification of the sender of the interchange.
- 0004 – Name or coded identification of the sender of the interchange.
  Type: an, Max Length: 35 (Required)
- 0007 – Qualifier referring to the identification code.
  Type: an, Max Length: 4
- 0008 – 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.
  Type: an, Max Length: 35
- 0042 – Sub-level of sender internal identification, when further sub-level identification is required.
  Type: an, Max Length: 35
S003 – Identification of the recipient of the interchange.
- 0010 – Name or coded identification of the recipient of the interchange.
  Type: an, Max Length: 35 (Required)
- 0007 – Qualifier referring to the identification code.
  Type: an, Max Length: 4
- 0014 – 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.
  Type: an, Max Length: 35
- 0046 – Sub-level of recipient internal identification, when further sub-level identification is required.
  Type: an, Max Length: 35
S011 – 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.
- 0098 – 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.
  Type: n, Max Length: 3 (Required)
- 0104 – 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.
  Type: n, Max Length: 3
- 0136 – 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.
  Type: n, Max Length: 6
0020 – Unique reference assigned by the sender to an interchange.
Type: an, Max Length: 14 (Required)
0083 – A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange, or indication of interchange receipt.
Type: an, Max Length: 3 (Required)
0085 – A code indicating the error detected.
Type: an, Max Length: 3
0135 – Code identifying a service segment.
Type: an, Max Length: 3
0534 – Unique reference number assigned by the security originator to a pair of security header and security trailer groups.
Type: an, Max Length: 14
0138 – 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.
Type: n, Max Length: 6

Group SG1 (Max 999999)

UCM 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. (Max 1) Required

S009 – Identification of the type, version, etc. of the message being interchanged.
- 0065 – Code identifying a type of message and assigned by its controlling agency.
  Type: an, Max Length: 6 (Required)
- 0052 – Version number of a message type.
  Type: an, Max Length: 3 (Required)
- 0054 – Release number within the current message version number.
  Type: an, Max Length: 3 (Required)
- 0051 – Code identifying a controlling agency.
  Type: an, Max Length: 3 (Required)
- 0057 – Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message.
  Type: an, Max Length: 6
- 0110 – Version number of the code list directory.
  Type: an, Max Length: 6
- 0113 – Code identifying a sub-function of a message type.
  Type: an, Max Length: 6
S011 – 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.
- 0098 – 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.
  Type: n, Max Length: 3 (Required)
- 0104 – 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.
  Type: n, Max Length: 3
- 0136 – 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.
  Type: n, Max Length: 6
S020 – Identification of the reference relating to the object.
- 0813 – Code giving specific meaning to a reference identification number.
  Type: an, Max Length: 3 (Required)
- 0802 – Reference number to identify a message, message group and/or interchange, which relates to the object.
  Type: an, Max Length: 35 (Required)
0062 – Unique message reference assigned by the sender.
Type: an, Max Length: 14
0083 – A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange, or indication of interchange receipt.
Type: an, Max Length: 3 (Required)
0085 – A code indicating the error detected.
Type: an, Max Length: 3
0135 – Code identifying a service segment.
Type: an, Max Length: 3
0800 – Unique package reference number assigned by the sender.
Type: an, Max Length: 35
0534 – Unique reference number assigned by the security originator to a pair of security header and security trailer groups.
Type: an, Max Length: 14
0138 – 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.
Type: n, Max Length: 6

Group SG2 (Max 999)

UCS To identify either a segment containing an error or a missing segment, and to identify any error related to the complete segment. (Max 1) Required

0096 – The numerical count position of a specific segment that is within the actual received message body. The numbering starts with, and includes, the UNH or the UIH segment as segment number 1. To identify a segment that contains an error, this is the numerical count position of that segment. To report that a segment is missing, this is the numerical count position of the last segment that was processed before the position where the missing segment was expected to be. A missing segment group is denoted by identifying the first segment in the group as missing.
Type: n, Max Length: 6 (Required)
0085 – A code indicating the error detected.
Type: an, Max Length: 3

UCD To identify an erroneous stand-alone, composite or component data element, and to identify the nature of the error. (Max 99)

S011 – 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.
- 0098 – 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.
  Type: n, Max Length: 3 (Required)
- 0104 – 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.
  Type: n, Max Length: 3
- 0136 – 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.
  Type: n, Max Length: 6
0085 – A code indicating the error detected.
Type: an, Max Length: 3 (Required)

Group SG3 (Max 999999)

UCF To identify a group in the subject interchange and to indicate acknowledgement or rejection (action taken) of the UNG and UNE 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 group level. Depending on the action code, it may also indicate the action taken on the messages and packages within that group. (Max 1) Required

S006 – Sender identification of for example a division, branch or application computer system/process.
- 0040 – Name or coded identification of the application sender (for example, a division, branch or computer system/process).
  Type: an, Max Length: 35 (Required)
- 0007 – Qualifier referring to the identification code.
  Type: an, Max Length: 4
S007 – Recipient identification of for example a division, branch or application computer system/process.
- 0044 – Name or coded identification of the application recipient (for example, a division, branch or computer system/process).
  Type: an, Max Length: 35 (Required)
- 0007 – Qualifier referring to the identification code.
  Type: an, Max Length: 4
S011 – 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.
- 0098 – 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.
  Type: n, Max Length: 3 (Required)
- 0104 – 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.
  Type: n, Max Length: 3
- 0136 – 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.
  Type: n, Max Length: 6
0048 – Unique reference number for the group within an interchange.
Type: an, Max Length: 14 (Required)
0083 – A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange, or indication of interchange receipt.
Type: an, Max Length: 3 (Required)
0085 – A code indicating the error detected.
Type: an, Max Length: 3
0135 – Code identifying a service segment.
Type: an, Max Length: 3
0534 – Unique reference number assigned by the security originator to a pair of security header and security trailer groups.
Type: an, Max Length: 14
0138 – 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.
Type: n, Max Length: 6

Group SG4 (Max 999999)

UCM 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. (Max 1) Required

Elements and codes as defined at UCM above.

Group SG5 (Max 999)

UCS To identify either a segment containing an error or a missing segment, and to identify any error related to the complete segment. (Max 1) Required

Elements and codes as defined at UCS above.

UCD To identify an erroneous stand-alone, composite or component data element, and to identify the nature of the error. (Max 99)

Elements and codes as defined at UCD above.

UNT To end and check the completeness of a message. (Max 1) Required

0074 – The number of segments in a message body, plus the message header segment and message trailer segment.
Type: n, Max Length: 10 (Required)
0062 – Unique message reference assigned by the sender.
Type: an, Max Length: 14 (Required)

Sources and further reading

GS1 EDI standards GS1 guidance on EDI standards used for supply-chain document exchange.
UNECE introduction to UN/EDIFACT United Nations guidance on UN/EDIFACT for structured business data exchange.
X12 EDI standards Official X12 standards body for North American EDI transaction standards.
OpenPeppol post-award specifications OpenPeppol documentation for e-procurement and e-invoicing specifications.