4.1 — Presentation of data elements

All names and definitions in TDED shall comply with the Oxford English Dictionary (both spelling and meanings).

The first line of each data element entry contains the numeric tag and the name of the data element; and elements belonging to the United Nations Trade Data Interchange Directory (UNTDID) are noted with an “E” (see section 1.8).

In addition, and in accordance with the principles set out in section 1.6, each data element entry contains a number of parts, identified by a header. The following headers are used to designate the different parts of the entries:

Desc

description of the data element

Repr

character representation, space available and location of the data entry, as explained below

Note

additional information, when appropriate

Ref

reference to an indicated source of information in cases where a “Note” is not sufficient. (Reference to other sections in the Directory is normally indicated by “cf” and the section number.)

Syn

synonymous names of the data element

A line separates data element entries from each other. Data elements with directly related clear text (even tag number) and coded (the next odd number) value representations appear one after the other.

When character representation is specified, using these abbreviations, it refers either to the space available for the data entry, and the location of the entry in the United Nations Layout Key (UNLK), or in another aligned international document referred to, or to the representation in an identified interchange protocol.

Whenever line and character positions are given for data elements appearing in internationally-established, aligned forms, this is done with a view either to confirm conformity to the UNLK, or to indicate deviations from the UNLK, or differences between such forms.

If fixed field lengths have been specified in a particular interchange protocol, this will be shown after an acronym, e.g. SWIFT: n6, CIMP: an..12, UNSM: an5. This is done mainly to indicate possible constraints for data items likely to be transmitted through such systems. In some instances organizations have introduced sectoral codes other than those recommended within UNECE. Such cases are indicated by reference to the relevant organization or Convention, e.g. currency code in Rail Consignment Note: CIM n2.

In specifications of character representation and entry location in aligned forms, these acronyms are used as follows:

1. Representation and location unique for AWB: Repr: AWB: a2; L 24, P 49-50
2. Representation and location in AWB deviates from general UNLK-based standard: Repr: n..10; L 54-60, P 49-56
   - AWB: n..8; L 33-44, P 39-46
3. Representation in AWB and CMR follows general standard but location is specific for each document: Repr: an..17; L 04, P 63-80
   - AWB: L 01, P 08-22
   - CMR: L 59, P 20-26
4. Representation in AWB follows general standard but differs in CIM: Repr: n..14
   - AWB: L 60, P 09-22
   - CIM: an..8; L 49, P 51-58

As set out in 1.8, the data elements have been grouped into broad categories in a way that will assist users of the Directory, at the same time taking into account the need to reserve substantial capacity for national and company use. This version of the directory does not include the service data elements (tags 0001-0699), as they are provided within the ISO 9735 EDIFACT Syntax, version 4 release 1 Part 10, 2002.

The system selected for the Directory for grouping data elements into broad categories is based on the characteristics of the data item, taking into account its nature rather than its application area. This means that all dates are placed in one group, all names in another, and all amounts in a third, without any consideration of the kind of date, name and amount.

Users, even if they do not know the exact name of a data element, or in which application area a particular data element might have been placed, are likely to know the expected contents of the data item with sufficient accuracy to be able to find it within a limited range of not more than one hundred data elements placed together according to this principle.

Attention is drawn to the allocation of tag numbers in each category:

• Up to 699 are reserved for allocation by the TDED Maintenance Agency.
• Tags 700 to 799 are used in message under development and are allocated by the submitter.
• Tags from 800 upwards are for use within national or regional message development groups.

In UN/EDIFACT UNCL Code List, rule 1.3: if a generic data element combined with a qualifier value is identical to an existing specific data element in TDED, then the description of the qualifier code value starts with the tag of the specific data element in [square brackets]. Example: under 3035 Party function code qualifier, the value BB “Buyer’s bank” carries [3420] Bank employed by the buyer to make payment — indicating that 3420 is a specific data element in the current TDED.

Rule 1.4: if a generic data element combined with a qualifier value is identical to an existing specific data element in TDED but the specific data element gives information which is normally provided in EDIFACT messages in associated separate data elements, then only the functional meaning is copied and the description of the qualifier code value starts with the tag of the specific data element in (round brackets). Example: under 3035, the value AL “Principal” carries (3340) Party accepting liability for goods held or moving (e.g. transit) under a Customs authorization and — when applicable — a guarantee.

This rule has now been applied similarly in TDED, allowing the same flagging, but the other way round.

Four-digit numbers are used as data element identifiers (tags) in the Directory. Taking into account the desirability of grouping the data elements into broad categories in a way that will assist users of the Directory, and also the need to reserve substantial capacity for national and company use, numbers have been assigned as follows, within the framework of a sub-division into 9 general categories.

Even tag numbers are used to designate the plain language representation of the data item (which includes numerical values other than codes), whereas the following odd, uneven number is reserved for the coded representation, when applicable, of the same data element, e.g. 4460 Payment means; 4461 Payment means, coded.

For identifiers:

• identifiers, also alpha-numerical ones, should have an odd tag (except for sequence identifiers, having an even tag);
• the preceding even number should not be used, except if a text version is required.

Existing entries not compliant with this rule should be corrected only if an explicit business need has been identified, asking for such a change. The purpose of the tags is to provide language independent identifiers for the data elements; the only significance attributed to the numbers is their designation of broad categories and the indication of plain language and coded version.

Data elements used in UNSMs are identified by an “E” in front of the issue number. This information is available only from the source database. These data elements are also included in the United Nations Trade Data Interchange Directory (UNTDID), Part 5, Chapter 6, EDED.

Each data element has been given an issue number:

1. for data elements used in UNSMs (identified by “E”), version/release control is reflected in data elements 0052 and 0054 and is based on changes to UN/EDIFACT directory version/release procedures;
2. for other data elements, the year of introduction into TDED or of amendment (e.g. 87).