| |
| |
|
Syntax identifier |
Coded identification of the agency controlling the syntax, and of the character repertoire used in an interchange.
Notes:
1. The data value consists of the letters 'UN', upper case, identifying the syntax controlling agency, directly followed by an a2 code identifying the character repertoire used. |
|
|
|
| |
|
Syntax version number |
Version number of the syntax.
Notes:
1. Increments 1 for each version. |
|
|
|
| |
|
Interchange sender identification |
Name or coded identification of the sender of the interchange.
Notes:
1. Organization code or name as agreed between interchange partners.
2. If coded representation is used, its source may be specified by the qualifier in data element 0007. |
|
|
|
| |
|
Identification code qualifier |
Qualifier referring to the identification code.
Notes:
1. A qualifier code may refer to an organization identification as in ISO/IEC 6523. |
|
|
|
| |
|
Interchange sender internal identification / S3: Address for reverse routing |
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.
Format for Syntax 3:
an..14
Format for Syntax 3X:
an..14 |
|
|
|
| |
|
Interchange recipient identification |
Name or coded identification of the recipient of the interchange.
Notes:
1. Organisation code or name as agreed between interchange partners.
2. If coded representation is used, its source may be specified by the qualifier in data element 0007. |
|
|
|
| |
|
Interchange recipient internal identification / S3: Address for reverse routing |
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.
Format for Syntax 3:
an..14
Format for Syntax 3X:
an..14 |
|
|
|
| |
|
Date |
Local date when an interchange or a group was prepared.
Notes:
1. Format is CCYYMMDD.
Format for Syntax 3:
n6 |
|
|
|
| |
|
Time |
Local time of day when an interchange or a group was prepared.
Notes:
1. Format is HHMM in 24 h clock. |
|
|
|
| |
|
Interchange control reference |
Unique reference assigned by the sender to an interchange. |
|
|
|
| |
|
Recipient reference/password |
Reference or password to the recipient's system or to a third party network as specified in the partners' interchange agreement.
Notes:
1. To be used as specified in the partners' interchange agreement. It may be qualified by data element 0025. |
|
|
|
| |
|
Recipient reference/password qualifier |
Qualifier for the recipient's reference or password.
Notes:
1. To be used as specified in the partners' interchange agreement. |
|
|
|
| |
|
Application reference |
Identification of the application area assigned by the sender, to which the messages in the interchange relate e.g. the message type, if all the messages in the interchange are of the same type.
Notes:
1. Identification of the application area (e.g. accounting, purchasing) or of the message type, as applicable. |
|
|
|
| |
|
Processing priority code |
Code determined by the sender requesting processing priority for the interchange.
Notes:
1. To be used as specified in the partners' interchange agreement. |
|
|
|
| |
|
Acknowledgement request |
Code requesting acknowledgement for the interchange.
Notes:
1. Used if the sender requests that a message related to syntactical correctness be sent by the recipient in response.
2. For UN/EDIFACT a specific message (Syntax and service report - CONTRL) is defined for this purpose. |
|
|
|
| |
|
Interchange agreement identifier |
Identification by name or code of the type of agreement under which the interchange takes place.
Notes:
1. Name or code to be specified in the partners' interchange agreement. |
|
|
|
| |
|
Test indicator |
Indication that the structural level containing the test indicator is a test. |
|
|
|
| |
|
Interchange control count |
The number of messages and packages in an interchange or, if used, the number of groups in an interchange. |
|
|
|
|
|
|
Message group identification |
Identification of the single message type in the group.
Notes:
1. This data element will be deleted from the next version of the standard. Therefore its use is not recommended. |
|
|
|
| |
|
Application sender identification |
Name or coded identification of the application sender (for example, a division, branch or computer system/process). |
|
|
|
| |
|
Interchange sender internal sub-identification |
Sub-level of sender internal identification, when further sub-level identification is required. |
|
|
|
| |
|
Application recipient identification |
Name or coded identification of the application recipient (for example, a division, branch or computer system/process). |
|
|
|
| |
|
Interchange recipient internal sub-identification |
Sub-level of recipient internal identification, when further sub-level identification is required. |
|
|
|
| |
|
Group reference number |
Unique reference number for the group within an interchange. |
|
|
|
| |
|
Controlling agency, coded |
Code identifying a controlling agency.
Format for Syntax 3:
an..2
Format for Syntax 3X:
an..2 |
|
|
|
| |
|
Message version number |
Version number of a message type. |
|
|
|
| |
|
Message release number |
Release number within the current message version number. |
|
|
|
| |
|
Association assigned code |
Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message. |
|
|
|
| |
|
Application password |
Password to the recipient's division, department or sectional application system/process. |
|
|
|
| |
|
Group control count |
The number of messages and packages in the group. |
|
|
|
| |
|
Message reference number |
Unique message reference assigned by the sender. |
|
|
|
| |
|
Message type |
Code identifying a type of message and assigned by its controlling agency.
Notes:
1. In UNSMs (United Nations Standard Messages), the representation is a6. |
|
|
|
| |
|
Common access reference |
Reference serving as a key to relate all subsequent transfers of data to the same business case or file. |
|
|
|
| |
|
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.
Notes:
1. The first message in the sequence shall be assigned as number 1. |
|
|
|
| |
|
First and last transfer |
Indication used for the first and last message in a sequence of messages related to the same topic. |
|
|
|
| |
|
Number of segments in a message |
The number of segments in a message body, plus the message header segment and message trailer segment.
Format for Syntax 3:
n..6
Format for Syntax 3X:
n..6 |
|
|
|
| |
|
Syntax release number |
The number of a syntax release (within an existing syntax version number). |
|
|
|
| |
|
Service code list directory version number |
Version number of the service code list directory. |
|
|
|
| |
|
Section identification |
Identification of the separation of sections of a message. |
|
|
|
| |
|
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. |
|
|
|
| |
|
Syntax error, coded |
A code indicating the error detected. |
|
|
|
| |
|
Anti-collision segment group identification |
To identify uniquely an anti-collision segment group in a message.
Notes:
1. The value of this data element shall be the segment group number of the UGH/UGT segment group as stated in the message specification. |
|
|
|
| |
|
Segment position in message body |
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. |
|
|
|
| |
|
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. |
|
|
|
| |
|
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. |
|
|
|
| |
|
Code list directory version number |
Version number of the code list directory. |
|
|
|
| |
|
Message type sub-function identification |
Code identifying a sub-function of a message type.
Notes:
1. The code qualifies the message type data element (0065) to allow the recipient to identify a specific sub-function of a message. |
|
|
|
| |
|
Message subset identification |
Coded identification of a message subset, assigned by its controlling agency. |
|
|
|
| |
|
Message subset version number |
Version number of the message subset. |
|
|
|
| |
|
Message subset release number |
Release number within the message subset version number. |
|
|
|
| |
|
Message implementation guideline identification |
Coded identification of the message implementation guideline, assigned by its controlling agency. |
|
|
|
| |
|
Message implementation guideline version number |
Version number of the message implementation guideline. |
|
|
|
| |
|
Message implementation guideline release number |
Release number within the message implementation guideline version number. |
|
|
|
| |
|
Scenario identification |
Code identifying scenario. |
|
|
|
| |
|
Scenario version number |
Version number of a scenario. |
|
|
|
| |
|
Scenario release number |
Release number within the scenario version number. |
|
|
|
| |
|
Character encoding, coded |
Coded identification of the character encoding used in the interchange.
Notes:
1. To be used as specified in the partners' interchange agreement, for the purpose of identifying the character repertoire encoding technique used in the interchange (when the default encoding defined by the character repertoire's associated character set specification is not used). |
|
|
|
| |
|
Service segment tag, coded / S3(X) Tag: 0013 |
Code identifying a service segment.
In syntax version 3 this data element has the identifier 0013 with identical properties.
Format for Syntax 3:
a3
Format for Syntax 3X:
a3 |
|
|
|
| |
|
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. |
|
|
|
| |
|
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. |
|
|
|
| |
|
Initiator control reference |
A reference assigned by the dialogue initiator. |
|
|
|
| |
|
Initiator reference identification |
Organization code or name assigned by the party that initiated the transaction or dialogue. |
|
|
|
| |
|
Responder control reference |
A reference assigned by the dialogue responder. |
|
|
|
| |
|
Transaction control reference |
A reference assigned by the transaction initiator. |
|
|
|
| |
|
Dialogue identification |
Code identifying a dialogue. |
|
|
|
| |
|
Event time |
Time of event.
Notes:
1. Format is HHMMSS ... with up to 9 more digits of precision. A 'Z' as the last character indicates UTC time. (ISO 8601) |
|
|
|
| |
|
Sender sequence number |
Identification of the sequence number of the message or package within the sender interchange. |
|
|
|
| |
|
Transfer position, coded |
Indication of the position of a transfer. |
|
|
|
| |
|
Duplicate Indicator |
Indication that the structure is a duplicate of a previously sent structure. |
|
|
|
| |
|
Report function, coded |
Coded value identifying type of status or error report. |
|
|
|
| |
|
Status |
Textual explanation of the reason for the status or error report. |
|
|
|
| |
|
Status, coded |
Code identifying the reason for the status or error report. |
|
|
|
| |
|
Language, coded |
Code identifying the language used.
Notes:
1. The code list for this data element is maintained by ISO (ISO 639). |
|
|
|
| |
|
Time offset |
UTC (Universal Coordinated Time) offset from event time.
Notes:
1. Format is HHMM. Shall be prefixed with '-' for negative offsets. (ISO 8601) |
|
|
|
| |
|
Event date |
Date of event.
Notes:
1. Format is YYMMDD or CCYYMMDD. |
|
|
|
| |
|
Interactive message reference number |
Unique interactive message reference assigned by the sender. |
|
|
|
| |
|
Dialogue version number |
Version number of a dialogue. |
|
|
|
| |
|
Dialogue release number |
Release number of a dialogue. |
|
|
|
| |
|
Security service, coded |
Specification of the security service applied. |
|
|
|
| |
|
Response type, coded |
Specification of the type of response expected from the recipient. |
|
|
|
| |
|
Filter function, coded |
Identification of the filtering function used to reversibly map any bit pattern on to a restricted character set. |
|
|
|
| |
|
Original character set encoding, coded |
Identification of the character set in which the secured EDIFACT structure was encoded when security mechanisms were applied. |
|
|
|
| |
|
Role of security provider, coded |
Identification of the role of the security provider in relation to the secured item. |
|
|
|
| |
|
Security party identification |
Identification of a party involved in the security process, according to a defined registry of security parties. |
|
|
|
| |
|
Security party code list qualifier |
Identification of the type of identification used to register the security parties. |
|
|
|
| |
|
Security party code list responsible agency, coded |
Identification of the agency in charge of registration of the security parties. |
|
|
|
| |
|
Date and time qualifier |
Specification of the type of date and time. |
|
|
|
| |
|
Encryption reference number |
Reference number to the encrypted EDIFACT structure. |
|
|
|
| |
|
Security sequence number |
Sequence number assigned to the EDIFACT structure to which security is applied.
Notes:
1. This sequence number is security related and may differ from the identification of the EDIFACT structure that may appear elsewhere. It may be used when sequence integrity is required. |
|
|
|
| |
|
Use of algorithm, coded |
Specification of the usage made of the algorithm. |
|
|
|
| |
|
Cryptographic mode of operation, coded |
Specification of the mode of operation used for the algorithm. |
|
|
|
| |
|
Algorithm, coded |
Identification of the algorithm. |
|
|
|
| |
|
Algorithm code list identifier |
Specification of the code list used to identify the algorithm. |
|
|
|
| |
|
Algorithm parameter qualifier |
Specification of the type of parameter value. |
|
|
|
| |
|
Mode of operation code list identifier |
Specification of the code list used to identify the cryptographic mode of operation. |
|
|
|
| |
|
Security reference number |
Unique reference number assigned by the security originator to a pair of security header and security trailer groups.
Notes:
1. 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. |
|
|
|
| |
|
Certificate reference |
Identifies one certificate for a certification authority. |
|
|
|
| |
|
Key name |
Name used to establish a key relationship between the parties. |
|
|
|
| |
|
Scope of security application, coded |
Specification of the scope of application of the security service defined in the security header.
Notes:
1. It defines the data that have to be taken into account by the related cryptographic process. |
|
|
|
| |
|
Certificate original character set repertoire, coded |
Identification of the character set repertoire used to create the certificate it was signed. |
|
|
|
| |
|
Certificate syntax and version, coded |
Coded identification of the syntax and version used to create the certificate. |
|
|
|
| |
|
User authorization level |
Specification of the authorization level associated with the owner of the certificate. |
|
|
|
| |
|
Service character for signature |
Service character used when the signature was computed.
Notes:
1. In order to avoid translator problems, this service character is represented by its value in the character set identified by the original character set encoding data element (0507), hexa-filtered on, at least, two characters. For example the service character "'" is coded "27" (two characters), if ASCII 8bit code page is used. |
|
|
|
| |
|
Service character for signature qualifier |
Identification of the type of service character used when the signature was computed. |
|
|
|
| |
|
Algorithm parameter value |
Value of a parameter required by the algorithm.
Notes:
1. If necessary, this value shall be filtered by an appropriate filter function. Note that key names do not need to be filtered. |
|
|
|
| |
|
Length of data in octets of bits |
A count of the data octets of bits. |
|
|
|
| |
|
List parameter |
Specification of the list requested or delivered. |
|
|
|
| |
|
Validation value |
Security result corresponding to the security function specified.
Notes:
1. If necessary, this value shall be filtered by an appropriate filter function. |
|
|
|
| |
|
Validation value qualifier |
Identification of the type of validation value. |
|
|
|
| |
|
Message relation, coded |
Relationship with another message, past or future. |
|
|
|
| |
|
Security status, coded |
Identification of the security element (key or certificate, for instance) status. |
|
|
|
| |
|
Revocation reason, coded |
Identification of the reason why the certificate has been revoked. |
|
|
|
| |
|
Security error, coded |
Identifies the security error causing the rejection of the EDIFACT structure.
Notes:
1. This element shall specify the security error encountered. These may be the reason for non-acknowledgement by a request for secure acknowledgement, or may be sent on the initiative of the receiver of an AUTACK or secured EDIFACT structure which contains error. |
|
|
|
| |
|
Certificate sequence number |
Specification of a certificate's position within a certification path.
Notes:
1. Allows certification paths to be ordered by specifying the ordinal number of the certificate within a certification path. |
|
|
|
| |
|
List parameter qualifier |
Specification of the type of list parameter. |
|
|
|
| |
|
Security party qualifier |
Identification of the role of the security party. |
|
|
|
| |
|
Key management function qualifier |
Specification of the type of key management function. |
|
|
|
| |
|
Number of padding bytes |
Count of the number of padding bytes. |
|
|
|
| |
|
Security party name |
Name of the security party. |
|
|
|
| |
|
Number of security segments |
The number of security segments in a security header/trailer group pair, plus the USD and USU segments where the security header/trailer group pair is used for encryption.
Notes:
1. Each security header/trailer group pair shall contain its own count of the number of security segments within that group pair.
2. The count of the number of security segments includes the USR segment in the security trailer. |
|
|
|
| |
|
Padding mechanism, coded |
Padding mechanism or padding scheme applied. |
|
|
|
| |
|
Padding mechanism code list identifier |
Specification of the code list used to identify the padding mechanism or padding scheme. |
|
|
|
| |
|
Package reference number |
Unique package reference number assigned by the sender. |
|
|
|
| |
|
Reference identification number |
Reference number to identify a message, message group and/or interchange, which relates to the object. |
|
|
|
| |
|
Object type qualifier |
Qualifier referring to the type of object. |
|
|
|
| |
|
Object type attribute |
The attribute applying to the object type. |
|
|
|
| |
|
Object type attribute identification |
Coded identification of the attribute applying to the object type. |
|
|
|
| |
|
Length of object in octets of bits |
Count of the number of octets of bits in the object.
Notes:
1. The count shall exclude the segment terminator of the preceding EDIFACT structured segment and the first character ('U') of the following EDIFACT structured segment. |
|
|
|
| |
|
Reference qualifier |
Code giving specific meaning to a reference identification number. |
|
|
|
| |
|
Number of segments before object |
A count of the number of segments appearing between the UNO segment and the start of the object. |
|
|
|
| |
|
Component data element separator
|
|
|
| |
|
Data element separator
|
|
|
| |
|
Decimal mark |
The character transferred in this position shall be ignored by the recipient. Retained to maintain upward compatibility with earlier versions of the syntax. |
|
|
|
| |
|
Release character
|
|
|
| |
|
Repetition separator
|
|
|
| |
|
Segment terminator
|
|
|
