Tradacomms Syntax Manual

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 153 [warning: Documents this large are best viewed by clicking the View PDF Link!]

April 1995 Page 1
April 1995 Page 2
NOTE: Whilst every effort has been made to ensure the advice and information given in this
manual is as accurate as possible, the Article Number Association is not liable
for any loss or damage suffered, or costs incurred, whether or not as a result of
any errors in the manual.
April 1995 Page 3
April 1995 Page 4
This manual contains the syntax (the grammar) and the data dictionary (the vocabulary) for the
TRADACOMS standard messages for direct computer to computer communications.
Section A contains the UN/GTDI syntax rules which govern how the messages are structured.
Section B lists the directory of standard data elements which make up the messages. Each data
element is identified by a 4-digit alphabetic code and the list is ordered alphabetically, for ease
of use. There is an additional reference number which identifies each element, which is used by
some systems. The data elements are also listed in name order.
Section C is a directory of the segments. These are logical groupings of related data elements.
Each TRADACOMS message is made up of a sequence of segments. The segments are
identified by a 3-digit alphabetic code. The segment directory is listed in alphabetic order of
these identifiers.
Section D contains the standard code values lists. Much of the data which is carried in
TRADACOMS messages can be standardised and coded. The use of codes allows easier
automatic processing of the communicated data. Each list is identified by a number and they are
given in numerical order.
Annex 1 contains information on the use of data narrative segments.
Annex 2 shows how the integrity of a TRADACOMS transmission can be checked without
processing the data content. This function can be performed by a Value Added Network
See Volume 1 for more detailed information on the ANA and Electronic Data Interchange. This
provides the background to the standards and the benefits which can be obtained by using them.
Volumes 2 and 3 contain the transmission structuring segments for each file format. There are
25 file formats available as this manual is issued, but there are new files under development
which may be added to Volume Three at a later date.
April 1995 Section A Page 5
Page No.
1.1 Background 5
1.2 Scope and Purpose 6
1.3 Advantages 6
1.3.1 Media Independence 6
1.3.2 Machine Independence 6
1.3.3 System Independence 6
1.3.4 Flexibility 6
1.3.5 Efficiency 7
1.3.6 Intelligibility 7
1.4 Messages and Documents 7
1.5 Syntax Rules Example 7
2.1 Introduction 11
2.2 General Terminology 11
2.2.1 Data Elements and Sub-Elements 11
2.2.2 Data Element Identifiers 11
2.2.3 Segments 12
2.2.4 Data Segments 12
2.2.5 Standard Segments 12
April 1995 Section A Page 2
2.2.6 Segment Codes 12
2.2.7 Interchange Messages 12
2.2.8 Message Types 13
2.2.9 Transmission 13
2.3 Data Separators and Terminators 13
2.3.1 Segment Terminator (') 13
2.3.2 Data Element Separator (+) 14
2.3.3 Sub-Element Separator (:) 14
2.3.4 Segment Code Separator (=) 14
2.3.5 Allowable Sequences of Data and
Separators/Terminators 14
2.4 Character Set and Related Subjects 15
2.4.1 Character Set for Interchange 15
2.4.2 Character Code 15
2.4.3 Release Character 15
2.4.4 Scope of the Character Set 16
2.4.5 Character Representation 16
2.4.6 Decimal Separator (.) 16
2.4.7 Negative Numbers 16
2.5 Absence of Data 16
2.5.1 Mandatory and Conditional Data 16
2.5.2 Rules for Indicating the Absence of Data 17
2.5.3 Variable Length Data 19
April 1995 Section A Page 3
2.6 Transmission Structuring Segments 19
2.6.1 A Transmission 19
2.6.2 Start of Transmission Segment (STX) 21
2.6.3 End of Transmission Segment (END) 21
2.6.4 Interchange Messages 21
2.6.5 Message Header Segment (MHD) 22
2.6.6 Message Trailer Segment (MTR) 23
2.6.7 Formats for the Standard Segments 23
2.7 Repeated and Nested Data 23
2.7.1 Introduction 23
2.7.2 Repeating Segments 23
2.7.3 Nested Segments 24
2.7.4 Sequence Numbers 24
2.8 Batching of Messages 24
2.8.1 Batching of Messages within a Transmission
(BAT and EOB) 24
2.8.2 Batch Header Segment (BAT) 25
2.8.3 Batch Trailer Segment (EOB) 25
2.9 TRADACOMS Conventions 27
2.9.1 Single File Transmissions 27
3.1 Applicability of the Syntax Rules to Various
Interchange Environments 28
3.1.1 Introduction 28
3.1.2 Computer (or Intelligent Terminal) to
Computer (or Intelligent Terminal) 28
3.1.3 Carriage Return and Line Feed Characters 29
April 1995 Section A Page 4
3.1.4 Computer to Unintelligent Terminal
(including Facsimile and Telex) 32
3.1.5 Unintelligent Terminal to Computer 29
3.2 Advantages of the Syntax Rules over Conventional
Computer Records for Interchange Systems 29
3.2.1 Drawbacks of Conventional Layouts for
Interchange Purposes 30
3.2.2 How Syntax Rules Overcome these
Disadvantages 30
3.2.3 Absence of Data 33
3.2.4 Conclusion 33
April 1995 Section A Page 5
1.1 Background
The TRADACOMS UNGTDI Syntax Rules are a subset of the full SITPRO Syntax
Rules which were originally developed for international trade applications. The full
name for the Syntax Rules is the United Nations Economic Commission for Europe
(UNECE) Guidelines for Trade Data Interchange (GTDI). The ANA now maintains this
for the benefit of TRADACOMS users in the UK.
The UNGTDI syntax has been used for the exchanged of trade data in several countries,
and was specified by H M Customs and Excise for their Period Entry Exports
interchange scheme. This and other international applications are now based on the later
UN EDIFACT (EDI for Administration, Commerce and Transport) syntax. For further
details of EDIFACT trade messages contact the ANA.
1.2 Scope and Purpose
The Syntax rules provide a method of assembling data elements within messages
interchanged between organisations.
The standards for individual data elements are provided in the Standard Data Element
Directory in Section B. The standards for the contents of interchange messages are
provided in the Message Format Specifications in Volumes 2 and 3. The syntax rules in
this Section specify how the data elements in Section B are structured into the message
formats in Volumes 2 and 3.
A full understanding of the syntax rules is necessary for the correct interpretation and
use, in practice, of the standard message formats.
The syntax rules are independent of machine, media and systems considerations, and
are, therefore, suitable for the interchange of data between computer systems, by a
telecommunications link or by physical media such as magnetic tapes or floppy discs
(diskettes). They are also independent of the structure of data within users' internal
computer systems. They are intended as a bridge between systems, for use at the point
of interchange. The sender converts from his internal record layouts and the recipient
converts into his internal layouts:
Computer A
File Layout
Convert to
Computer B
Methods for the initial capture of data (in the sender's own system) and the final output
April 1995 Section A Page 6
of data (in the recipient's own system) are, therefore, outside the scope of the syntax
rules, except possibly where the interchange does not involve computer processing at
one end of the exchange, as may happen in certain fall-back situations. These are briefly
discussed in paras. 3.1.1 to 3.1.4 at the end of this Section.
The syntax rules do not dictate the extent to which data should be validated prior to
transmission. The onus is on the sender of a message to provide accurate
information which has been correctly assembled. The recipient of a message should
carry out validation checks, however, to help ensure that invalid data does not corrupt
internal computer records.
The syntax rules only apply to the data interchanged. They do not apply to the
communications protocols and media labels within which the data is transmitted.
Privacy of data is outside the scope of the rules. Where required, encryption or other
techniques can be agreed between interchange partners. Facilities are provided,
however, for the transmission of control totals in the TRADACOMS Standards message
formats, to check the safe transmission of data.
1.3 Advantages
The advantages of using the syntax rules can therefore be summarised as follows:-
1.3.1 Media Independence
Data is structured in the same way whether it is interchanged via magnetic media or a
telecommunications link. The syntax rules help minimise the cost of changing from one
medium to another in inter-organisation exchange, and the cost to a single organisation
sending or receiving data via several types of media.
1.3.2 Machine Independence
Incompatibilities of record size and character representation between different makes of
computer are avoided. No reprogramming costs need be incurred by existing members
of an interchange application when a new member, who has a different make of
computer, joins.
1.3.3 System Independence
The rules are not influenced by the constraints of any particular system design, such as
batch, on-line, file/record design or retrieval techniques, communications techniques,
1.3.4 Flexibility
The rules allow a great deal of flexibility in the design and structuring of messages.
Changing message specifications should be less costly with data structured using the
syntax rules than with conventional records. Using table-driven programs makes
changes particularly easy to effect.
April 1995 Section A Page 7
1.3.5 Efficiency
The rules allow data to be transmitted in an economical manner (see paragraph 2.9
below). This can be important over telecommunications links.
1.3.6 Intelligibility
By using special character data separators and alpha segment codes, the syntax rules
make messages relatively easy to interpret, and thus aid tasks such as investigating
A fuller discussion of the advantages of messages designed according to the
TRADACOMS Syntax Rules over conventional computer records, for data exchange,
appears at the end of this Section, in paras. 3.2.1 to 3.2.4.
1.4 Messages and Documents
An interchange message can often be considered as the equivalent of a document, for
example an invoice or an order. However, other forms of interchange messages are not
directly equivalent to conventional documents. Depending on the nature and purpose of
the interchange system, these are then equivalent to several documents or to only part of
a document, or might have no documentary equivalent at all.
1.5 Syntax Rules Example
The syntax rules can be illustrated by comparing part of a typical order document
(Figure A.1) with the equivalent interchange messages assembled according to the rules
(Figure A.2). The example messages are in standard TRADACOMS format.
April 1995 Section A Page 10
Figure A.2
CDT = 5000600003101:68100+ANY SHOP PLC+HEAD OFFICE:72 KING STREET:
FIL = 1+1+940321'
MTR = 6'
CLO = 5000600003240::68322'
ORD = 981::940321'
OLD = 1+5000100481452+5000100074326++12+10++++PRODUCT A'
OLD = 2+5000100350666+5000100068271++6+10++++PRODUCT B'
OLD = 3+5000100154073+5000100154066++4+30++++PRODUCT C'
OTR = 3+6'
MTR = 9'
CLO = 5000600003282::68347'
ORD = 982::940321'
OLD = 1+5000100769680+5000100769673++6+5++++PRODUCT K'
OLD = 2+5000100658465+5000100668136++6+8++++PRODUCT L'
OTR = 2+13'
MTR = 7'
OFT = 2'
MTR = 3'
END = 4'
April 1995 Section A Page 11
2.1 Introduction
In the following paragraphs:
a) the general terminology used within the specification of the syntax rules is
b) the character set recommended for interchange is defined
c) the basic syntax rules are specified.
These basic syntax rules are applicable for the majority of interchange applications,
including the TRADACOMS system.
2.2 General Terminology
2.2.1 Data Elements and Sub-Elements
Different organisations use different terminology to describe or define basic items of
data. In these rules, the following terms are used:-
a) Data Element
This is an item of data which has been identified separately for interchange by its
inclusion in the TRADACOMS Data Element Directory. It may consist of a
single item of data, eg. Earliest Delivery Date, in which case it is called a simple
data element, or it may consist of several items of data, eg. the data element
Unit of Ordering. This consists of the number of consumer units in a trade unit,
the ordering measure and a measure indicator. In this case it is called a
composite data element. A data element is identified by its position within a
'segment', defined below.
b) Sub-Element
This is the name given to each item of data within a composite data element. In
the example above, measure indicator is a sub-element. A sub-element is
identified by its position within a data element.
2.2.2 Data Element Identifiers
Data elements are allocated unique 4 character data element identifiers. These are used
to identify data elements in the TRADACOMS Data Element Directory, in message
specifications and in the tables used to construct and translate standard TRADACOMS
messages. They can also be used for system and program documentation. Data element
identifiers are not transmitted.
April 1995 Section A Page 12
2.2.3 Segments
a) Related data elements are grouped together within the syntax rules to form a
segment. A segment is the basic unit for the transmission of data; individual
data elements can only be transmitted within a segment. A segment can contain
one or more data elements.
b) There are two types of segment:
- Data Segments
- Standard Segments
2.2.4 Data Segments
These contain the amounts, values, names, places and other data required for
transmission. The contents of data segments are independent of the syntax rules.
2.2.5 Standard Segments
The only category of standard segments that is used in these basic syntax rules, applying
to TRADACOMS transmissions, is that of the Transmission Structuring Segments that
are used to assemble interchange transmission in a standard way. Standard segments are
provided to start and end each interchange, and to start and end each message within an
interchange. They are discussed in para. 2.6 of this Section.
2.2.6 Segment Codes
a) Segments are uniquely identified by a 3-character segment code which must be
b) Segment codes have been reserved for each of the standard segments included in
the syntax rules.
c) Segment codes are transmitted at the start of the segments they identify.
2.2.7 Interchange Messages
a) An interchange message consists of a number of segments structured in
accordance with the syntax rules, ie. it must begin with the standard message
header segment and end with the standard message trailer segment.
b) In the TRADACOMS environment all interchange messages are Data
Messages. These contain the data segments required for the message in addition
to the message header and message trailer segments. The ANA maintains
standard message specifications, which are found in Volumes 2 and 3 of this
April 1995 Section A Page 13
2.2.8 Message Types
Interchange messages are identified by a message type which is included in the standard
message header segment. A message type consists of two sub-elements:
- the message type itself. This is a 6-character alphabetic code;
- a version number. This is a single digit numeric sub-element. It is used in
connection with changes to data message specifications, to distinguish one
version of a message from another.
2.2.9 Interchange Transmission
a) All the data to be transmitted between two organisations at one time is referred
to as an interchange transmission. An interchange can contain a single message
or many messages. The standard Start of Transmission segment is used to
identify the start of the data being transmitted. The standard End of
Transmission segment is used to denote the end of the data being transmitted.
b) The only restriction imposed by the syntax rules on the number of messages
included in an interchange transmission is that the message count on the end of
transmission segment cannot exceed 99,999. There are no restrictions on the
number of different types of message which can be included in a transmission.
However see paragraph 2.9 below.
c) The syntax rules do not themselves specify the order in which messages should
be transmitted within an interchange transmission, but the standard messages are
all grouped within TRADACOMS-designated files and within each file a
message sequence is specified. The sender can forward a number of designated
files, one after another, in an order of his choosing, unless participants in an
exchange application agree otherwise. The conventional format of interchange
transmissions is described in 2.9.
d) Participants can agree restrictions on the number of files or messages in a
transmission if they so wish. See paragraph 2.9.
2.3 Data Separators and Terminators
2.3.1 Segment Terminator (')
Each segment is terminated by a segment terminator, the apostrophe (or single quote) (')
eg. .......... 123'
April 1995 Section A Page 14
2.3.2 Data Element Separator (+)
a) Data elements within a segment are separated from each other by a data element
separator, a plus (+)
eg. ..........+ABC+123
b) The last data element in a segment is terminated by the segment terminator. A
data element separator is not required.
2.3.3 Sub-Element Separator (:)
a) Sub-elements with a composite data element are separated from each other by a
sub-element separator, the colon (:)
eg. ..........+5530:KG+.....
b) The last sub-element within a composite data element is terminated by a data
element separator. A sub-element separator is not required.
2.3.4 Segment Code Separator (=)
A segment code is separated from the data within a segment by a segment code
separator, an equals sign (=)
eg. IRF=8728511+810320'
2.3.5 Allowable Sequences of Data and Separators/Terminators
The logic of the syntax rules allows only the sequences of data, separators and
terminators indicated in the following table (Figure A.3).
Figure A.3
Can only be followed by item(s) ticked
End of
Segment Code
Data Element
April 1995 Section A Page 15
2.4 Character Set and Related Subjects
2.4.1 Character Set for Interchange
In the TRADACOMS environment the character set for data is restricted to:
Blank Space Ampersand & Asterisk *
Open Bracket ( Close Bracket ) Comma ,
Hyphen - Full Stop . Solidus /
Percent %
The numerals zero to 9.
The upper case alphabet A to Z.
The following characters are reserved for control purposes within the syntax rules and
their use in data should be avoided wherever possible:
Apostrophe ' Plus sign + Colon :
Equals = Padding Character ^
2.4.2 Character Code
The coded representation of each allowable character for the various transmission media
is discussed in Section E of Volume 1.
2.4.3 Release Character
The question mark, ?, is reserved for use within the syntax rules as a release character.
The release character is provided for use where separator or terminator characters
(ie. =:'+) have to be transmitted as part of a data element or sub-element. Where a
question mark is itself included in data it must also use the release character function.
It is strongly recommended that the five characters =:'+? be excluded from data elements
and sub-elements wherever possible. It should be possible to avoid the use of the
release character by replacing these characters in data by another character without any
loss of meaning. For example, an apostrophe could be replaced by a space (O'REILLY
would be transmitted as O REILLY).
The release character must be inserted in a transmission immediately preceding each
occurrence in data of any of the five characters =:'+?. It signifies that the next single
character is not to be interpreted as a data separator, terminator or release character. For
Data required 736 + 834 = 1570
Data transmitted 736? + 834? = 1570
The release character is not counted as part of the length of any data element or sub-
April 1995 Section A Page 16
element within which it is transmitted. Release characters can be inserted by the
computer so that data can be input and output without any special manual requirements,
except where messages are manually structured or interpreted.
2.4.4 Scope of the Character Set
The full recommended character set including the special characters +=:' applies only to
the data content of the transmission. Requirements for telecommunication protocols,
media labels, etc., are outside the scope of this recommendation. They are dealt with in
Section E of Volume 1 of this manual.
2.4.5 Character Representation
Character formats are recommended within these syntax rules. Binary, packed decimal
or other forms of hardware/software-dependent representation must not be used for
interchange as these features are not available, or are not dealt with in the same way, on
all makes of computer.
2.4.6 Decimal Separator (.)
a) An implied decimal separator or point is used in the TRADACOMS system.
b) Thousands must not be indicated by any form of separator (such as commas).
2.4.7 Negative Numbers
a) A negative number is indicated by a leading minus sign.
eg. SEG=..... +-1250+.... is correct.
b) In many cases the need for negative numbers can be avoided through the use of
data elements such as the Credit Line Indicator used in TRADACOMS invoice
Notes: Provision should be made in translation tables for negative numbers using
leading minus signs in messages where the totals could become negative
if the credit values exceed the normal debit ones. For example,
statement totals could be negative if credit adjustments exceeded new
2.5 Absence of Data
2.5.1 Mandatory and Conditional Data
a) Within a segment, data elements are specified as mandatory or conditional.
b) Mandatory data elements are those which must always be transmitted, eg. the
message type on a standard message header segment or the invoice number and
date in an invoice message.
c) Conditional data elements are those which need to be transmitted only in a
April 1995 Section A Page 17
particular set of circumstances, depending on the nature of the goods, the mode
of transport, etc., eg. a special price indicator in an order message.
d) Segments must also be designated as mandatory or conditional within each
message type.
e) A mandatory segment may consist entirely of conditional data elements. At least
one of these must be transmitted for this type of segment.
f) Within a composite data element, individual sub-elements are also designated as
mandatory or conditional and, similarly, if all are conditional within a mandatory
data element, at least one sub-element must be transmitted.
2.5.2 Rules for Indicating the Absence of Data
a) Where no data exists for a conditional segment, the segment must not be
b) Where no data is required for one or more data elements in a segment, which
precede another data element for which data is required, the data element
separator is used to indicate the absence of data:-
i) If there are 5 data elements, AAAA, BBBB, CCCC, DDDD and EEEE
in a segment with the segment code SEG and data is only required for
SEG = data for AAAA + data for BBBB + data for CCCC ++ data for
no data for DDDD
ii) Similarly, if data is only required AAAA, BBBB and EEEE:
SEG = data for AAAA + data for BBBB +++ data for EEEE'
├── no data for CCCC
└── no data for DDDD
c) Where no data is required for one or more data elements at the end of a segment,
two options are available:
i) The preferred option is to use the segment terminator to truncate the
segment following the last data element for which data is required:
April 1995 Section A Page 18
eg. Using the example shown in b) above, the following can be transmitted
if data is only required for AAAA and BBBB:
SEG = data for AAAA + data for BBBB'
ii) Alternatively, data element separators can be used to indicate positively
the absence of data for each data element.
eg. Using the above example, if data is only required for AAAA and BBBB:
SEG = data for AAAA + data for BBBB +++'
│ └──── no data for EEEE
│ └────── no data for DDDD
└──────── no data for CCCC
Note: Users' programs should cater for both these techniques, as each is valid.
d) The absence of data for one or more conditional sub-elements within a
composite data element is indicated using similar principles to those described
above. A data element separator is inserted following the last sub-element for
which data is required. The absence of data for one or more sub-elements which
precede another, for which data is required, is indicated by the sub-element
i) If a data element contains 4 sub-elements, K, L, M and N and only the
first 2 are required:
....+ data for K: data for L +....
ii) In the same example, if data is only required for K and N:
....+ data for K:::data for N +....
│└────── no data for M
└─────── no data for L
e) A typical use of conditional sub-elements is for data elements defined as
containing both a code and a clear language version, eg. transmission sender.
The rules allow either or both the sub-elements to be transmitted in a consistent
April 1995 Section A Page 19
....+ 123:ABC CO+........................
....+ 123 +...................................
....+ :ABC CO+............................
are valid ways of constructing a data element which can contain a code and/or a
clear language sub-element.
2.5.3 Variable Length Data
a) Separators allow the omission of leading zeros in numeric items and trailing
spaces in alphanumeric items for those data elements defined as "variable
length" in the Data Directory.
For example:
i) RTL = .............+ ABC LTD'
ii) OLD = .............+ 930:KG+..............
OLD = .............+ 12100:KG+...........
b) Where variable length data is interchanged, the sender may elect to transmit, in
accordance with the syntax rules and without reference to the recipient, either the
actual number of characters used or any number of characters up to and
including the maximum number of characters. Where the maximum number of
characters is transmitted, the following rules apply:
i) Numeric data should be right-aligned with leading zeros or spaces to pad
the data to its maximum length, but there must be one zero before the
decimal separator for amounts less than one.
ii) Alphabetic/alphanumeric data should be left-aligned with trailing spaces
used to pad the data to its maximum length.
2.6 Transmission Structuring Segments
NB The normal rules for indicating the absence of conditional data, specified in
subsection 2.5, apply to these standard segments.
2.6.1 A Transmission
a) The data transmitted at one time between two organisations is a transmission.
Standard segments are provided to denote the start and the end of the data
within a transmission.
b) The first segment in all transmissions must be the Start of Transmission
segment which has the segment code STX.
April 1995 Section A Page 20
c) The last segment in all transmissions must be the End of Transmission segment
which has the segment code END.
d) A transmission can therefore be depicted as:-
┌── STX segment
│ <
│ >
│ data
│ <
│ >
└── END segment
Figure A.4 Example STX Segment
STX=ANA:1+123:ABC CO+:XYZ CO+811206:121500+A143+B26+ASYS+A'
where STX is the segment code
ANA:1 identifies version 1 of the TRADACOMS Syntax Rules
123:ABC CO identifies the sender of the message in code and plain language
:XYZ CO identifies the recipient of the messages in plain language only
811206:121500 811206 is the transmission date
121500 is the time of transmission
A143 is the sender's reference for the transmission
B26 is the recipient's reference for the transmission, if known to the
ASYS is an application reference
A is a transmission priority code if required
Note: 1. The data element specifications for this and all other standard segments are
contained in the TRADACOMS Data Element Directory and message
specifications in this manual.
2. When using STX for transmissions across Value Added Networks, it is
recommended that the user manual is consulted as each has used the elements
in STX to achieve network addressing and control features. These are specific
usages of the elements defined in this segment and will have to be respected if
that service is used
April 1995 Section A Page 21
2.6.2 Start of Transmission Segment (STX)
a) Mandatory information included in this segment identifies:
- the syntax rules being used
- the sender and recipient of the transmission
- the date of transmission
- the sender's reference for the transmission
b) Conditional information which can be included in the segment consists of:
- the time of transmission
- the recipient's reference for the transmission
- an application code (this would enable a recipient to identify, at the STX
level, whether the transmission contained data for an import application,
an export application, an accounting application, etc.). The application
reference may also be used to indicate whether a transmission is 'live' or
'test' in status. In this case, the reference abbreviations given in Code
Values List 16 should be used
- priority code
c) Figure A.4 contains an example of an STX segment in which all the conditional
data is illustrated.
2.6.3 End of Transmission Segment (END)
a) This segment contains one data element, in which a count of the number of
messages in a transmission must be provided.
b) The count includes all data messages in the transmission, to a maximum of
99,999 messages.
eg. END = 1' indicates a transmission consisting of 1 message
END = 25' indicates a transmission consisting of 25 messages
2.6.4 Interchange Messages
a) With the exception of the standard segments STX and END used to delimit a
transmission, all data must be interchanged within a message.
b) All messages begin with a Standard Message Header segment which has the
segment code MHD. All messages must end with the Standard Message
Trailer segment which has the segment code MTR.
c) A transmission can consist of one message or any number of messages.
d) A transmission containing one message can therefore be depicted as:
┌─── STX segment
April 1995 Section A Page 22
│ ┌── MHD segment
│ │ <
│ │ >
│ │ data
│ │ <
│ │ >
│ └── MTR segment
└─── END segment
e) A transmission containing more than one message can be depicted as:
┌─── STX segment
│ ┌── MHD segment )
│ │ < )
│ > )
│ │ data ) Repeated for each message
│ │ < )
│ │ > )
│ └── MTR segment )
└─── END segment
2.6.5 Message Header Segment (MHD)
a) The MHD segment contains two mandatory data elements:
- A Message Reference
This can be any unique reference allocated by the sender. In
TRADACOMS messages this takes the form of a consecutive count of
messages within a transmission.
- A Message Type
This consists of two sub-elements, the message type itself and a number
to distinguish the different versions of a message which can arise due to
amendments to the message specification.
b) An example of an MHD segment is:
MHD = 12 + ORDERS:4'
This identifies a data message of type ORDERS, that contains data relating to
the fourth version of the specification for ORDERS, and that it is the 12th
message in the transmission.
April 1995 Section A Page 23
2.6.6 Message Trailer Segment
a) This segment contains one mandatory data element, which is a count of the
number of segments comprising the message.
b) The count includes both the MHD and MTR segments and data segments
included in the message.
eg. MTR = 7' indicates that a message consists of 7 segments
2.6.7 Formats for the Standard Segments
The standard formats for segments MHD and MTR are illustrated in all the message
formats in Volumes 2 and 3. The segments STX and END do not appear in messages.
Their standard formats are shown in Figure A.5 and at the beginning of Volume 2.
2.7 Repeated and Nested Data
2.7.1 Introduction
a) A common requirement of many types of message is the need to repeat data
elements, or groups of data elements eg. an invoice could contain a number of
items, each item containing a product number, quantity, price, etc. A particular
data element must not be repeated within a data segment, but a data segment can
be repeated within a message.
b) Sometimes a data element or group of data elements may repeat within an
already repeating group, for example an invoice can cover goods supplied under
several orders, and there may be many invoice item lines to each order. The data
elements for an invoice line item form what is called a 'nested' repeating group.
The data elements for a line item are grouped together in one repeating data
segment while the details for each order are grouped in another repeating
segment. The repeating segments are numbered and sequenced according to the
following rules:
2.7.2 Repeating Segments
a) A sequence number data element is specified as part of a repeating data
segment. The sequence number starts at 1 for the first transmitted repeating
segment and is increased by 1 for each subsequent occurrence of this segment
within the message.
eg. ODD = 1 + .....'
ODD = 2 + .....'
ODD = 3 + .....'
etc. │
order sequence number/count within invoice message
b) The sequence number reverts to one at the start of each message.
April 1995 Section A Page 24
2.7.3 Nested Segments
a) The principle of using sequence numbers is extended so that there is one
sequence number for each level of nesting. In this case, however, the sequence
numbers must indicate the hierarchical order of the data segments:-
eg. ODD = 1 + .....' 1st level (highest or `parent' level)
ILD = 1 + 1 + .....' 2nd level (first invoice line sequence in first
ILD = 1 + 2 + .....'
ODD = 2 + .....' 1st level
ILD = 2 + 1 + .....' 2nd level
ILD = 2 + 2 + .....'
└───────────┐ │
1st level ─┘ └─ 2nd level
Sequence number Sequence number
b) Where necessary, the technique can be extended to cover more complicated
nesting situations:-
eg. AAA = 1 + ..........'
AAB = 1 + 1 + ..........'
AAB = 1 + 2 + ..........'
AAC = 1 + 2 + 1 + ..........'
AAC = 1 + 2 + 2 + ..........'
AAD = 1 + 2 + 2 + 1 + ..........'
AAC = 1 + 2 + 3 + ..........'
AAB = 1 + 3 + ..........'
AAC = 1 + 3 + 1 + ..........'
AAB = 1 + 4 + ..........'
AAA = 2 + ..........'
2.7.4 Sequence Numbers
a) On nested repeated segments the highest level sequence number must come first,
followed by the next highest and so on.
b) Segments must be transmitted in the hierarchical sequence indicated in the above
2.8 Batching of Messages
2.8.1 Batching of Messages within a Transmission (BAT and EOB)
a) A transmission can be divided into a number of batches if such a facility is
required in a particular application. Batching is a conditional feature of the
syntax rules as it will not be a requirement of all interchanges.
April 1995 Section A Page 25
b) The facility must only be used, therefore, where the participants in an
interchange agree this in advance.
c) A batch of data within a transmission begins with a Batch Header segment
which has the segment code BAT. A Batch is terminated by a Batch Trailer
segment which has the segment code EOB.
d) A transmission consisting of a single batch of messages can be depicted as:-
┌──── STX segment
│ ┌─── BAT segment
│ │
│ │ ┌── MHD segment )
│ │ │ < )
│ │ │ > ) Repeated for each message
│ │ │ data )
│ │ │ < )
│ │ │ > )
│ │ └── MTR segment
│ │
│ └─── EOB segment
└──── END segment
e) A transmission consisting of more than 1 batch of messages can be depicted as:-
┌──── STX segment
│ ┌─── BAT segment )
│ │ )
│ │ ┌── MHD segment ) Repeated ) Repeated
│ │ │ < ) for each ) for batch
│ │ │ > ) message ) within a
│ │ data ) within a ) transmission
│ │ │ < ) batch )
│ │ │ > ) )
│ │ └── MTR segment )
│ │ )
│ └─── EOB segment )
└──── END segment
2.8.2 Batch Header Segment (BAT)
a) This contains a reference allocated by the sender to the batch.
eg. BAT = 77421' identifies a batch with the reference 77421
2.8.3 Batch Trailer Segment (EOB)
a) This contains a count of the number of messages in a batch, including any
control messages.
eg. EOB = 29' indicates that a batch consists of 29
April 1995 Section A Page 27
The UNGTDI syntax rules do not restrict the number and type of messages and files
which may be exchanged. However to simplify processing, particularly for the
recipient, the following TRADACOMS conventions have been established.
When other conventions are to be used in EDI communications, these need to be agreed
with trading partners, to ensure that the combinations of files and messages can be
processed correctly.
2.9.1 Single File Interchanges
A TRADACOMS File normally consists of a Header Message, one or more Detail
Messages, followed by a Trailer Message. This convention is illustrated in the diagram
below. For those messages which contain VAT information there is also a VAT Trailer
Message before the File Trailer Message.
When several orders are being transmitted in one interchange to a supplier it is the usual
practice to send all the Order Detail Messages within the same Header/Trailer Messages,
rather than repeating the Header and Trailer Messages for each Detail Message. This
improves the efficiency of the transmission.
It is recommended that there is one file for one recipient sent in each interchange
transmission. This permits control of the files transmitted and end to end audit trails
(see Volume 1 Section A Paragraph 8 Controls).
It is also recommended that there is one type of file in each interchange transmission as
this allows recipients to sort and select files for different applications using the
application reference in STX.
April 1995 Section A Page 28
3.1 Applicability of the Syntax Rules to Various Interchange Environments
3.1.1 Introduction
In the following paragraphs the applicability of the rules to various types of interchange
environments is discussed:-
- computer (or intelligent terminal) to computer (or intelligent terminal)
- computer to unintelligent terminal (including facsimile and telex)
- unintelligent terminal to computer
For the purpose of this discussion:-
- a computer is any equipment used to construct messages in accordance with the
syntax rules (whether data is input manually or held on in-house computer
records), or any equipment used to translate messages structured in accordance
with the rules to meet in-house computer record or print layout requirements.
for instance, it can add separators, terminators, segment codes etc., to data at the
sender's end of a transmission and remove them at the recipient's end.
- an unintelligent terminal is any equipment which cannot be, or is not, used to
construct and translate messages. It includes facsimile, telex and message
switching systems where data has to be manually prepared or interpreted.
3.1.2 Computer (or Intelligent Terminal) to Computer (or Intelligent Terminal)
This includes the interchange of data over telecommunications links and by a physical
medium, such as magnetic tape, where messages have been constructed by the sender's
computer and are translated by the recipient's computer.
The syntax rules are primarily intended for this form of interchange. They act as a
bridge between the internal requirements of the various interchange partners. Methods
of data capture by senders of messages and methods of output of data by recipients are
outside the scope of the syntax rules in this environment.
In this environment, errors caused by missing or wrongly used separators, or by other
incorrect use of the syntax rules, are likely to be minimal once trials have been
completed. It is strongly recommended that interchange partners carry out trials prior to
implementing an interchange system, not only to ensure that data has been correctly
formatted but also to ensure that the computers are compatible as far as the interchange
medium is concerned.
Unless economy of transmission is vital, errors should be corrected by re-transmitting
complete messages. This is the simplest form of correction. This subject is treated in
detail in paragraph 9 of Section C in Volume 1.
April 1995 Section A Page 29
3.1.3 Carriage Return and Line Feed Characters
These will not normally be included in computer-to-computer environments but it may
not be possible to assume that such a transmission will not contain these characters, eg.
the sender of the transmission may receive data which included these characters from
another organisation and pass the data to the recipient without editing the data. In
interchange systems where this could arise, participants could agree that senders of
messages would remove all such characters prior to computer-to-computer interchange.
3.1.4 Computer to Unintelligent Terminal (Including Facsimile and Telex)
The TRADACOMS system is based on computer-computer transfers of data. When an
unintelligent terminal is used to print or display messages the recipient will need a copy
of the message specification.
Intelligibility is aided by the use of segment codes and the graphic separators = + :' but
messages in syntax rules format are not designed primarily for human interpretation.
Carriage Return and Line Feed characters would need to be transmitted on telex. These
are not separator characters and can be used freely to improve the readability of
messages, eg. after each line of a name and address.
3.1.5 Unintelligent Terminal to Computer
The main difference between data prepared by computers and data which is manually
prepared is the likely increase in the incidence of errors, as neither data nor formats are
validated by computer prior to interchange.
Recipients should be tolerant of 'extra' spaces if any data might be manually prepared.
eg. MHD = 12 + ORDHDR :3'
Data input manually to the telex network or a message switching system will contain
fewer errors if input forms specially designed for each message are used.
3.2 Advantages of the Syntax Rules over Conventional Computer Records for
Interchange Systems
The conventional layouts in most in-house systems, in which each data element begins
in a fixed position within the character string comprising a record, have a number of
drawbacks for interchange systems. These paragraphs illustrate how the syntax rules
overcome these drawbacks, using progressive changes to conventional record layouts.
April 1995 Section A Page 30
3.2.1 Drawbacks of Conventional Layouts for Interchange Purposes
Conventional records are rarely directly intelligible to people without considerable
computer processing experience. There are no segment codes or data element separators
to aid the identification of each data element and, unless special arrangements are made
to include a version number in a message, recipients cannot be certain that the necessary
amendments have been made by senders.
Media Space
Utilisation of media space may be poor, as data elements are usually padded to their
maximum length with leading zeros or trailing spaces. While this may not be critical on
magnetic tape, it could be critical over telecommunication links.
There is no data independence in conventional layouts. Any change to a data element
length affects the position of all subsequent data elements within a message. A fully
detailed record layout needs to be agreed by all interchange partners even though some
individual participants may not require a particular data element. This makes
maintenance difficult.
Machine Dependence
Different makes of computers may set varying constraints on logical records and block
sizes. Conventions for variable length records on magnetic tape may differ.
3.2.2 How Syntax Rules Overcome these Disadvantages
(a) Conventional Layout
Figure A.6 illustrates a conventional record layout which might be used for a
message based on part of an order. Each element begins in a fixed position and
is padded to its maximum length. In this example six elements/sub-elements are
not required, leaving spaces in the record layout. Only part of one order line is
shown; a full order could contain over a thousand lines.
April 1995 Section A Page 31
Figure A.6 Conventional Layout for Part of an Order Record
Record Layout
810303 810313 USE GATE NO.6
0 6 12
1 5012345678900
52 56 69
12345A 5012345101019
77 90
105 113 117
125 131 136 144 150
Earliest delivery date, Latest delivery
date, Delivery instructions narrative.
Order line sequence no., Supplier's EAN
Trade Unit Code
Supplier's item no./code,
Supplier's EAN consumer unit code,
Retailer's own Brand no. (blank)
Retailer's item no. (blank), Consumer
units in trade unit, Ordering measure
Measure indicator (blank), No. of trade
units ordered, Total measure ordered
(blank), Measure indicator (blank), etc.
(b) Segments
(i) The first improvement that the Syntax Rules make to this conventional
layout is to divide one record for the whole order into shorter sub-records
or, as they are called in the standards, segments.
For example the delivery dates and instructions could be included in a
segment called DIN. The order line details could form part of a segment
called OLD. (Figure A.7.)
Figure A.7
DIN 810303 810313 USE GATE NO.6
0 3 9 15
OLD 1 5012345678900 12345A etc
0 3 7 20 28
(ii) This technique gives three advantages:-
- Better use can be made of media space. If there is no data in an
entire segment, then it can be omitted from the interchange
- Segment codes make a message more intelligible.
- It is more flexible, as additional segments can be inserted without
April 1995 Section A Page 32
(iii) However, there are some disadvantages:-
- A data element which is blank in a segment containing some
non-blank data elements still takes up media space eg. allowing
for orders by trade unit or measure in the OLD segment.
- Data elements are identified solely by their position within the
segment. A change in the length of one element would
necessitate changing the position of all subsequent elements in
the segment. Data independence is therefore limited.
- Another disadvantage is that each segment would need to start on
a computer record boundary, as there is no other easy way of
distinguishing the segment code. To complicate matters, each
type of segment could have a different length and some
computers cannot cope with variable length records: alternatively
all segments would need to be padded out to a common length
which would be wasteful of media space.
(c) Separator Characters
(i) The above difficulties are overcome in the Syntax Rules by the inclusion
of special characters to separate one data element from another, to
terminate a segment, to separate a segment code from the data and to
split a composite data element, where required, into its component parts.
Figure A.8 contains the same data as shown in the conventional record
layout in Figure A.6 but formatted according to the Syntax Rules.
Figure A.8 Syntax Rules Layout for Part of an Order Record
DIN=810303+810313++USE GATE NO.6'
In Figure A.8:-
- A plus (+) is used to terminate each data element.
- An apostrophe (') - or single quote - is used to terminate a
- A colon (:) is used to separate one sub-element from another.
- An equals sign (=) is used to separate a segment code from the
- A plus (++) is not used to terminate the last data element of a
segment as the apostrophe fulfils the purpose.
(ii) Padding can be omitted by incorporating separator characters. This
April 1995 Section A Page 33
improves the use of media space. Figure A.8 uses 83 characters against
the 150 used in Figure A.6.
(iii) Separators help to make the message more intelligible.
(iv) Data element lengths can be altered without affecting the identification
of subsequent data elements.
(v) Segments need not begin on a computer record boundary as the use of
separators clearly distinguishes the segment code. Message and segment
lengths, therefore, need not be dictated by such constraints as
input/output block sizes, particular conventions on the use of variable
length records, the physical characteristics of punched cards,
telecommunications, protocols etc. Anyone interchanging data on a
variety of media or between machines using different conventions needs
to be free of such restraints.
3.2.3 Absence of Data
In many messages some of the data will be mandatory (ie. it must always be present) and
some will be conditional (ie. it might or might not be present depending upon the
sender, mode of transport, type of goods etc.). The absence of data can be indicated
efficiently in three ways using the syntax rules:-
- Where no data need be transmitted for an entire segment, the segment need not
be transmitted at all (ie. where all the data elements are conditional).
- Where one or more data elements at the end of a segment are absent, the
segment may be truncated, eg. if there are five data elements in a segment and
data is only required for the first two A and B, this can be represented by:-
segment code = data for A + data for B'
- Where no data is required for an element which precedes another element for
which data is required in a segment, the absence of data can be indicated by the
data element separator character. For example, if there is no data for element B
in the sequence of elements A, B, C this can be represented by:-
segment code = data for A ++ data for C'
3.2.4 Conclusion
One point should be re-emphasised - it is not proposed that conventional, in-house
record layouts or databases as used by application programs should be replaced by ones
structured according to the syntax rules. The rules are used to structure messages at the
point of interchange as a "bridge" between differing systems. The sender converts from
his internal record layouts and the recipient converts into his internal record layouts.
The fact that the sender may have conventional files and the recipient a database will not
affect the success of the syntax rules as a bridge for the transfer of data between the two
systems. The syntax rules are also being used to transfer data between different parts of
the same company.
April 1995 Section B Page 1
Page No.
2.1 Identifier 3
2.2 Data Element Name 3
2.3 Used in Segment(s) 3
2.4 M/C 3
2.5 F/V 3
2.6 Picture 3
2.7 General Remarks 3
April 1995 Section B Page 2
All current ANA TRADACOMS data elements which appear (or have appeared) in
published messages are listed here, with their standard names and identifier codes. The
directory contains the full definition of each data element, with sub-elements for
composite data elements. The data segments in which the elements are used is indicated
in the following table. The standard messages and files in which the segments appear
can be found in the Segment Directory in Section C.
To achieve uniformity across all message formats, the definitions given here are
replicated within the segments and messages in which they are included. However there
may be additional specific General Remarks in particular file formats given in Volumes
2 and 3 of the manual.
The Directory is in alphabetical order of the Identifier codes. There is also a list of
elements in Data Element Name order, to aid users wishing to find a particular data type.
The Reference Numbers given in the previous edition of the manual are also listed.
These reference numbers were used to group the data elements into the following
The Categories of Data Elements
1 Start of Transmission, End of Transmission, Message Header, Message Trailer.
2 File Identification Details.
3 Customer and Supplier Details.
4 Codes, Special Indicators/Identifiers, Counts, Sequence Numbers.
5 References, Dates, Units, Quantities.
6 Cost Details, Discount Amounts/Totals, Percentages.
7 Amounts, Sub-Totals.
8 Totals, Hash Totals.
9 General Descriptive Text/Narrative.
April 1995 Section B Page 3
2.1 Identifier
The unique 4-alpha identifier allocated to the data element. This is used as a data
element name in high level programming.
2.2 Data Element Name
The standard name allocated by the ANA. Names indented indicate the sub-elements of
a composite data element.
2.3 Used in Segments
The segment, or segments, in which the data element is used. Reference to the Segment
Directory in Section C of this manual will indicate the standard messages and files in
which the segments are used. (Any subsequent amendments to the data elements can
thus be traced through to all the documentation and programs affected).
2.4 M/C
Indicates whether the data element is mandatory (M) or conditional (C) in each segment
in which it is used. Also whether the sub-elements are mandatory or conditional within
a composite data element.
2.5 F/V
Indicates whether the data element, or sub-element, is of fixed (F) or variable (V) length.
2.6 Picture
Indicates the number of numeric (9) digits or alphanumeric (X) characters allowed in the
data field. If the field is numeric, this excludes any minus sign or the decimal point.
The decimal point is implied and its position within the data field is indicate by V.
2.7 General Remarks
These are the remarks that are appropriate to the data element, or sub-element, in all
contexts in which it is used. In any particular message format these remarks may be
supplemented by message-specific remarks and/or reformulated to particularise their
meaning in that message.
April 1995 Section B Page 4
This lists the data elements in name order
April 1995 Section B Page 73
Name Cat.Ref. Ident. Sub-Element
ANA Code for Garment Maker 11.004 GMAK 1
ANA Credit Reason Code 4.015 CRRE 1
Accept/Reject Indicator .000 ACRE
Account Identifier 3.205 ACID
Account Identifier REFF
Account Name 3.205 ACID 2
Account Number 3.205 ACID 1
Account Reference MARF
Accumulation Rules .000 ACCR
Acknowledged Unit Cost Price 6.020 AUCT
Acknowledgement Code ACDE
Acknowledgement Date ACDT
Action ACTN
Action Code ACTN 1
Action Comment ACTN 2
Actual Adjustment .000 AADJ
Actual/Proposed Status Indicator 4.230 APIN
Adjustment Amount .000 AADJ 2
Adjustment Factor .000 ADJF
Adjustment Factor Code .000 ADJF 1
Adjustment Factor Value .000 ADJF 2
Adjustment Percentage .000 AADJ 1
Adjustment Type Indicator .000 ADJT
Advice Note Date 11.021 ADVN 2
Advice Note Details 11.021 ADVN
Advice Note Number 11.021 ADVN 1
Advised Lengths .000 ADLG
Advised Quantity .000 AQTY
Advised Units .000 ADUN
Advised Weights .000 ADWT
Allowance/Charge Indicator .000 AOCI
Alphanumeric VAT Registration No. 3.080 VATN 2
April 1995 Section B Page 74
Alphanumeric VAT Registration No. 3.081 VATR 2
Amended Invoice Reference .000 VDAA 4
Amount Payable .000 AMPA
Amount Payable 7.140 AMPY
ANMW Multiple Group Member CUSG
Application Reference 1.070 APRF
Application Text 9.130 RTEX 2
Application Text 9.130 RTEX 4
Application Text 9.130 RTEX 6
Application Text 9.130 RTEX 8
Area of Exception Condition 9.200 AEXC
Area of Exception Condition 9.200 AEXC 1
Area Manager MAMN
Association Indicator MUNE 1
Attribute Code DATT 1
Attribute Code TIME 1
Authentication Result 8.300 AUTR
Authentication Result 1 8.300 AUTR 1
Authentication Result 2 8.300 AUTR 2
Authentication Result 3 8.300 AUTR 3
Authorisation .000 AUTT
Authorisation 3.092 LEVC 2
Authority Reference 5.405 AUTH
Availability Reference/Series No. 5.400 AREF
Back Order Indicator 4.420 DIND 2
Balance Brought Forward .000 BABF
Balance Brought Forward .000 BABF 1
Balance Date 5.650 OUBA 2
Balance of Outstanding Prepayments Received PAYB
Bank Identity Code 4.515 BKIC
Bank Information 12.000 BKIN
Bank Name 3.220 BNAM
Bank/Branch Identifier 3.210 BBID
Barcode as Printed on Cover .000 IBCM
Base Price per Unit .000 BPRI
Batch ID .000 REPN 1
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 75
Batch Number .000 BATN
Bill File Total Amount before VAT .000 FASU
Bill File Total Amount before VAT .000 FASU 1
Bill File Total Payable inc. VAT .000 FPSU
Bill File Total Payable inc. VAT .000 FPSU 1
Bill File Total VAT Amount .000 UVAT
Bill File Total VAT Amount .000 UVAT 1
Bill Frequency Code .000 BIFR
Bill Total VAT Amount Payable .000 UTVA
Bill Total VAT Amount Payable .000 UTVA 1
Bill Type Code .000 BTCD
Blend/Merge Number .000 BLND
Booking In Necessity 3.015 BINN
Branch Claim Quantity 10.095 BCMQ
Branch Claims File Total 10.025 BCFT
Branch Claims Total 10.140 BCMT
Calorific Value .000 CLVM 1
Calorific Value in Specified Units .000 CLVM
Carrier Details .000 CARD
Carrier Sortation Data CSOR
Carrier's EAN Location Number .000 CARD 1
Carrier's Identity Allocated by Cus .000 CARD 2
Carrier's Name 11.022 CARN
Cash Back Amount .000 AMPA 2
Cash Settlement Discount Identifier 4.080 CSDI
Charge End Date .000 CEDT
Charge Start Date .000 CSDT
Charge Type Code .000 CCDE
Chargeable Storage Medium Indicator .000 CSTI
Claim Note Date 10.045 CLDT
Claim Note Number 10.040 CLNN
Claims End Date CEDD
Claims End Date .000 ICSE
Claims Start Date CSTD
Claims Start Date .000 ICSD
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 76
Classification System RCAT 1
Closing Stock for the Period 5.410 CLSK
Code ACDE 1
Code .000 AUTT 2
Code 1.020 FROM 1
Code 1.030 UNTO 1
Code Table Number 9.140 DNAC 1
Code Value 9.140 DNAC 2
Code Value LATT 2
Code Value LATT 4
Code Value LATT 6
Code Value LATT 8
Code for Replaced Item 3.100 CORI
Code for Unit Contained 3.110 UCON
Collection Method .000 REPN 2
Collection Note Date 5.046 CNDT
Collection Note Number 5.043 CNNR
Colourway Description .000 COLW 2
Colourway Number .000 COLW 1
Colourway References .000 COLW
Comment ACDE 2
Company Identifier (non-EAN) COTN 3
Company Trade Name COTN
Company Trading Name Code COTN 1
Company Trading Name Title COTN 2
Composition 11.011 COMP
Consumer Units in Traded Unit 5.120 UNOR 1
Consumption (Adjusted Units) .000 CONA
Consumption (Base Units) .000 CONB
Consumption (Billing Units) .000 CONS
Consumption/Charge Indicator .000 CCDE 1
Contact Details CONT
Contact Fax Number CONT 3
Contact Name CONT 1
Contact Name 3.165 CTNM
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 77
Contact Name at Customers 11.007 CCON
Contact Name at Dyers/Suppliers 11.006 DCON
Contact Telephone Number CONT 2
Contract Number 5.550 SCRF 2
Contruction/Yarn Type 11.010 CNST
Copies Claimed COPC
Copies Rejected CREJ
Cost Price 6.010 OUCT 1
Cost Price (before VAT) 6.020 AUCT 1
Country Code .000 REPN 5
Country of Origin CUDA 2
Cover ID Format .000 IDCI 2
Cover Identification .000 IDCI 1
Cover Identification and Format .000 IDCI
Cover Price In Pence .000 IRCP
Credit Discount Value 06.051 CDSV
Credit Indicator .000 BABF 2
Credit Indicator .000 CTOT 2
Credit Indicator .000 FASU 2
Credit Indicator .000 FBAB 2
Credit Indicator .000 FPSU 2
Credit Indicator .000 FTOP 2
Credit Indicator .000 MVAL 2
Credit Indicator .000 PTOT 2
Credit Indicator .000 TBTL 2
Credit Indicator .000 USDI 2
Credit Indicator .000 UTVA 2
Credit Indicator .000 UVLT 2
Credit Indicator .000 UVTT 2
Credit Indicator .000 VTVC 2
Credit Line Indicator 4.060 CRLI
Credit Line Indicator .000 PPAM 2
Credit Line Indicator .000 UCSI 2
Credit Line Indicator .000 UPSI 2
Credit Line Indicator .000 UVAT 2
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 78
Credit Line Indicator .000 UVLA 2
Credit Note Date 5.106 CRDT
Credit Note Number 5.036 CRNR
Credit Reason Description 4.015 CRRE 3
Credit Value (before VAT) 6.026 UCRV 1
Currency .000 QPER 5
Currency Indicator .000 CUIN
Current Price Schedule Reference .000 CPSC
Customer Card Number .000 PANN 1
Customer Classification RCAT
Customer Group EAN Number CUSL 1
Customer Group Location CUSL
Customer Group Name CUSN
Customer Price After Discount 6.130 ACPR
Customer Price Before Discount 6.120 BCPR
Customer Telephone Number CTEL
Customer's Address 3.032 CADD
Customer's Address Line 1 3.032 CADD 1
Customer's Address Line 2 3.032 CADD 2
Customer's Address Line 3 3.032 CADD 3
Customer's Address Line 4 3.032 CADD 4
Customer’s Allowance CALL
Customer's Code for Order Office 3.155 OLOC 2
Customer's Code for Transmission Re 3.024 ITRA 2
Customer's EAN Location Number 3.020 CIDN 1
Customer's EAN Location Number 3.000 CLOC 1
Customer's ID Allocated by Supplier 3.020 CIDN 2
Customer's Identity 3.020 CIDN
Customer's Instruction Number 5.610 INRF 1
Customer's Invoice Location Code 3.022 ILOC 2
Customer's Item Code 3.040 CPRO 2
Customer's Item Code 3.046 CPRS 2
Customer's Item Code 3.110 UCON 5
Customer's Item Code 3.100 CORI 5
Customer's Location 3.000 CLOC
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 79
Customer's Name 3.030 CNAM
Customer's Order Number 5.010 ORNO 1
Customer's Own Brand EAN Number 3.100 CORI 4
Customer's Own Brand EAN Number 3.040 CPRO 1
Customer's Own Brand EAN Number 3.046 CPRS 1
Customer’s Own Group Code CUSL 2
Customer's Own Location Code 3.000 CLOC 2
Customer's Own Location Code 3.029 CLOE 2
Customer's Own Location Code 3.028 CLOS 2
Customer's Post Code 3.032 CADD 5
Customer's Product Number 3.040 CPRO
Customer’s Reference REFF 2
Customer's Region Code 3.009 REGC
Customer's Statement Location Code 3.026 SLOC 2
Customer's Substituted Product Code 3.046 CPRS
Customer's VAT Registration Number 3.081 VATR
Customers Price List 5.660 PLND 2
Customer's Own Brand EAN Number 3.110 UCON 4
Customs Information CUDA
Customs Form Type Indicator CUDA 3
DUN-14 Code 3.110 UCON 3
DUN-14 Code for Traded Unit 3.070 SPRO 3
DUN-14 Code for the Traded Unit 3.076 SPRS 3
DUN-14 Code of Replaced Item. 3.100 CORI 3
Data Lines 10.517 STLD
Data Narrative Code 9.140 DNAC
Date Attributes DATT
Date Goods Delivered to Customer 5.050 PODN 2
Date Goods Uplifted from Customer 5.580 POUN 2
Date Instruction Recv'd by Supplier 5.610 INRF 4
Date Instruction Placed by Customer 5.610 INRF 3
Date Order Received by Supplier 5.010 ORNO 4
Date Order Placed by Customer 5.010 ORNO 3
Date Range 5.116 DARA
Date and Time of Transmission 1.040 TRDT
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 80
Date at End of Period 10.522 RTRS 4
Date of Bill Withdrawn .000 VDAA 2
Date of Delivery/Uplift Units 5.038 UPLN 2
Date of Document 5.040 DELN 2
Date of First Entry 10.522 RTRS 1
Date of Invoice 5.100 IVDT
Date of Message 5.310 MEDT 1
Date of Transmission 1.040 TRDT 1
Date of Change 5.113 DACH
Date Relating to Message 5.705 DATE
Daytime Number CTEL 1
Debit Line Indicator 04.065 DRLI
Debit Note Date 5.103 DNDT
Debit Note Number 5.033 DNNR
Deleted Issue Indicator 10.000 IDEL
Deliver To 3.012 DELT
Delivery Address Line 1 .000 DADD 1
Delivery Address Line 2 .000 DADD 2
Delivery Address Line 3 .000 DADD 3
Delivery Address Line 4 .000 DADD 4
Delivery Condition 4.200 DELC
Delivery Confirmation Action 4.390 DUAC 2
Delivery Indicators 4.420 DIND
Delivery Instruction Narrative 9.020 DINS
Delivery Instruction Number 5.560 DINN
Delivery Instructn Narrative Line 1 9.020 DINS 1
Delivery Instructn Narrative Line 2 9.020 DINS 2
Delivery Instructn Narrative Line 3 9.020 DINS 3
Delivery Instructn Narrative Line 4 9.020 DINS 4
Delivery Lead time 5.672 DLED
Delivery Note Details 5.040 DELN
Delivery Note Number 5.040 DELN 1
Delivery Period End Date 5.090 DVED
Delivery Post Code .000 DADD 5
Delivery Quantity 5.165 DELQ
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 81
Delivery Round Code CSOR 4
Delivery Volume 5.137 DEVL
Delivery Weights 5.135 DEWT
Delivery to Address .000 DADD
Delivery to Location .000 ELOC
Delivery to Name .000 DNAM
Delivery/Uplift Action 4.390 DUAC
Department .000 DEPT
Depot Code CSOR 3
Depot Code 4.330 DEPO
Depot Name CSOR 2
Design Description .000 DESN 2
Design Number .000 DESN 1
Design References .000 DESN
Despatch From 3.017 DESF
Despatch Location 3.150 DLOC
Direct to Customer Indicator DCUS
Discount Amount for Invoice Quanty. 6.060 QYDA
Discount Amount for Invoice Value 6.070 VLDA
Discount Applicability Dates 5.676 DAPD
Discount Percentage 6.100 DSCP
Discount Reclaimed for Credit Qty 6.066 QYCA
Discount Reclaimed for Credit Value 6.076 VLCA
Discount Type 4.231 DTYP
Discount Value 6.050 DSCV
Discount Value Graduations 5.678 DVGD
Dye Lot/Shade Order Number/Sort No. .000 LOTN
Dyeing Instructions .000 DYEI
Dyeing Instructions Line 1 .000 DYEI 1
Dyeing Instructions Line 2 .000 DYEI 2
Dyeing Instructions Line 3 .000 DYEI 3
Dyeing Instructions Line 4 .000 DYEI 4
EAN Article Number 11.003 YAGT 1
EAN Article Number 11.002 YSUP 1
EAN Location No of Dept/Person 3.120 METO 1
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 82
EAN Location Number 3.029 CLOE 1
EAN Location Number 3.028 CLOS 1
EAN Location Number .000 ELOC 1
EAN Location Number 11.005 FCUS 1
EAN Location Number 11.001 GSUP 1
EAN Location Number 3.022 ILOC 1
EAN Location Number 3.024 ITRA 1
EAN Location Number PARL 1
EAN Location Number PLOC 1
EAN Location Number .000 REPN 3
EAN Location Number 3.026 SLOC 1
EAN Location Number 3.152 TLOC 1
EAN-13 Article Number 11.009 QLTF 3
EAN-13 Article No for Unit of Trade 3.076 SPRS 1
EAN-13 Article No.for Unit of Trade 3.070 SPRO 1
EAN-13 Article Number .000 CCDE 2
EAN/ISSN Number .000 IDID
EFTPOS Transaction Type .000 EFTT
Earliest Delivery Date 5.060 EDAT
Earliest Time 5.075 RATM 1
Earliest Time RTHD 1
Earliest Uplift Date 5.620 EUDT
Electronic Transmission From/To 3.019 ETFT
End Customer's Location Identity 3.029 CLOE
End Date 5.676 DAPD 2
End Date 5.116 DARA 2
End Date DATT 3
End Date 5.674 PAPD 2
End Date .000 SUMO 2
End Date TRDD 3
End of Range PROD 3
End Time LUHR 2
End Time TIME 3
End Use of Fabric/Yarn .000 ENDU
EPOS Till Indicator EPTI
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 83
Evening Number CTEL 2
Exception Code 5.715 ECOD
Exception Text 9.205 ETXT
Expected Delivery Date 5.655 XDAT
Expiry Date .000 PANN 2
Extended Line Cost (before VAT) 6.030 LEXC
Extended Sub-Total Amount (after sd 7.060 ASDA
Extended Sub-Total Amount before sd 7.040 EVLA
Fax Number FAXN
File (Reel) Identification 2.040 FLID
File Creation Date 2.030 FLDT
File Generation Number 2.010 FLGN
File Sub-Total Amount (after sd) 7.100 VSDI
File Sub-Total Amount (before sd) 7.090 VSDE
File Sub-Total Payable (after sd) 7.130 VPSI
File Sub-Total Payable (before sd) 7.120 VPSE
File Tot No of Picking Instructions 4.350 FTPC
File Total Amount (after sd, no VAT 8.110 FASI
File Total Amount (before VAT & sd 8.100 FASE
File Total Balance Brought Forward .000 FBAB
File Total Balance Brought Forward .000 FBAB 1
File Total No of Report Messages 10.520 FTSR
File Total No. of Invoices/Credit 4.117 FTNI
File Total Number of Acknowlegments 4.400 FTAK
File Total Number of Adjustments 4.380 FTNA
File Total Number of Confirmations 4.320 FTCO
File Total Number of Debit Advices 8.330 FTND
File Total Number of Deliveries 4.112 FTDE
File Total Number of EFT Messages .000 FTEM
File Total Number of Hot Messages .000 FTNH
File Total Number of Orders 4.100 FTOR
File Total Number of Payment Msgs 8.305 FTNP
File Total Number of Snapshots 4.310 FTNS
File Total Number of Uplifts 4.370 FTUP
File Total Payable after sett disc 8.140 FPSI
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 84
File Total Payable before sett disc 8.130 FPSE
File Total VAT Amount 8.120 FVAT
File Total VAT for VAT Category .000 VTVC
File Total VAT for VAT Category .000 VTVC 1
File Total for VAT Cat (before VAT) .000 USDI
File Total for VAT Cat (before VAT) .000 USDI 1
File Total for VAT Category (incVAT .000 UPSI
File Total for VAT Category (incVAT .000 UPSI 1
File Total of Availability Reports 4.360 FTAR
File Total of Payment Details .000 FTOP
File Total of Payment Details .000 FTOP 1
File Total of Credit Advice Msgs 8.320 FTNC
File Total of Debit Advice Msgs 8.330 FTND 1
File Total of Exception Reports 8.310 FTNE
File VAT Sub-Total 7.110 VVAT
File Version Number 2.020 FLVN
Final Customer 11.005 FCUS
Finished Markings .000 MARK 2
Finished Quality 11.009 QLTF
Finished Quality Code 11.009 QLTF 1
Finished Quality Description 11.009 QLTF 2
Finished Quantity for Shade .000 TSHD 2
Finished Width in cms. .000 FWID
Finishing Instructions .000 FINI
Finishing Instructions Line 1 .000 FINI 1
Finishing Instructions Line 2 .000 FINI 2
Finishing Instructions Line 3 .000 FINI 3
Finishing Instructions Line 4 .000 FINI 4
First Attribute Code Table LATT 1
First Class Code/Value RCAT 2
First Level Sequence Number 4.141 SEQA
First Name MAMN 2
First Name MANA 2
First Name PROP 2
First Registered Application Code 9.130 RTEX 1
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 85
Fourth Attribute Code Table LATT 7
Fourth Class Code/Value RCAT 5
Fourth Level Sequence Number 4.144 SEQD
Fourth Registered Application Code 9.130 RTEX 7
Frequency of Publication .000 IDFE
Frequency/Schedule DATT 4
From 5.678 DVGD 1
From 6.685 PVGD 1
Full Title (Publisher) .000 IDFT
Fully SOR Indicator .000 IPFS
Garment Maker 11.004 GMAK
General Narrative 9.040 GNAR
General Narrative Line 1 9.040 GNAR 1
General Narrative Line 2 9.040 GNAR 2
General Narrative Line 3 9.040 GNAR 3
General Narrative Line 4 9.040 GNAR 4
Grade MGRD
Graduated Price 6.160 GRPR 1
Graduated Scale Price 6.160 GRPR
Graduation Type 4.432 GTYP
Grey Markings .000 MARK 1
Grey Quality 11.008 QLTG
Grey Quality Code 11.008 QLTG 1
Grey Quality Description 11.008 QLTG 2
Grey Width in cms 11.015 GWID
Grey Supplier 11.001 GSUP
Gross Length .000 ADLG 1
Gross Weight .000 ADWT 1
Gross Weight of Storage Medium .000 UGST
Gross Weight of Unit 5.230 UGWT
Growth Allowance 10.065 GRAL
Hash Total of Variable Measures 8.170 WTVT
Height of Storage Medium .000 UHST
Height of Unit 5.260 UHYT
Home Delivery Indicator HOMD
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 86
Hours 5.672 DLED 2
House Over File Total 10.030 HSFT
House Over Quantity 10.100 HSOQ
House Over Total 10.145 HSOT
ID of Transmission Recipient 1.030 UNTO
ID of Transmission Sender 1.020 FROM
Identifier 1.010 STDS 1
Identity Allocated by Customer 11.003 YAGT 2
Identity Allocated by Customer 11.005 FCUS 2
Identity Allocated by Customer 11.004 GMAK 2
Identity Allocated by Customer 11.001 GSUP 2
Indentity Allocated by Customer 11.002 YSUP 2
Initial Supply File Total 10.001 INFT
Initial Supply Quantity 10.070 INSQ
Initial Supply Total 10.115 INST
Installation Date .000 INSD
Instruction References 5.610 INRF
Invoice Location 3.022 ILOC
Invoice Number 5.030 INVN
Invoice Period End Date 5.080 IVED
Invoice System EAN Location Number 3.180 INLO 1
Invoice System Location Details 3.180 INLO
Invoice System Supplier's Own Code 3.180 INLO 2
Invoice To 3.013 INVT
Invoice To Address 3.175 IADD
Invoice To Address Line 1 3.175 IADD 1
Invoice To Address Line 2 3.175 IADD 2
Invoice To Address Line 3 3.175 IADD 3
Invoice To Address Line 4 3.175 IADD 4
Invoice Transmission Recipient 3.024 ITRA
Issue Number 10.055 ISNO
Issue Number .000 PANN 4
Issue Period To .000 IPTO
Issue Period from .000 IPFR
Item Group Identifier 4.070 IGPI
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 87
Journey Reference 5.510 JORF
Labels Per Package LPCK
Last Date for Order .000 ISOD
Last Issue Indicator .000 ILST
Latest Delivery Date 5.070 LDAT
Latest Time 5.075 RATM 2
Latest Time RTHD 2
Latest Uplift Date 5.625 LUDT
Layers Per Pallet 5.220 LPAL
Length of Storage Medium .000 ULST
Length of Unit 5.240 ULTH
Level Code 3.092 LEVC 1
Level References 3.092 LEVC
Line Document Amount Payable 6.180 LIDA
Line Document Date 5.055 LIDR 2
Line Document Discount Taken 6.210 LIDD
Line Document Number 5.055 LIDR 1
Line Document Reference 5.055 LIDR
Line Document Total (Exc. VAT & sd. 6.190 LIDT
Line Document VAT 6.200 LIDV
Lines Acknowledged 4.395 LACK
Lines Confirmed 4.093 LCON
Lines Delivered 4.095 LDEL
Lines Ordered 4.090 LORD
Lines Sub-Total (before sett. disc. 7.030 LVLA
Lines Total Amount (before sett dis 8.010 LVLT
Lines Uplifted 4.097 LUPL
Location Activity Indicator 10.525 LOCA
Location Address 3.004 LADD
Location Address Line 1 3.004 LADD 1
Location Address Line 2 3.004 LADD 2
Location Address Line 3 3.004 LADD 3
Location Address Line 4 3.004 LADD 4
Location Attributes LATT
Location Code LOCO
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 88
Location Name 3.002 LNAM
Location Post Code 3.004 LADD 5
Location Telephone Number 3.006 LTEL
Location Telex Number 3.007 LTLX
Location Values/Measurements LVAL
Lot & Shade Details Ordered .000 NLSD
Lot & Shade Line Details Ordered .000 NLLD
Lunch Hour LUHR
Manager/Contact MANA
Manufacturer's EAN-13 Article Numbr 3.100 CORI 1
Manufacturer's EAN-13 Article No. 3.110 UCON 1
Manufacturer's Recom. Selling Price 6.140 SPRI 1
Manufacturers recommended selling 6.141 MSPR 1
Marked Price 6.141 MSPR 3
Marked Price 6.140 SPRI 2
Marked Price 6.141 MSPR 2
Markings .000 MARK
Master File Total No. of Hot Card .000 FTNM
Maximum Ordering Value 5.675 MOVL 2
Maximum Ordering quantity 5.670 MOQY 2
Maximum Storage Temperature 5.290 TMAX
Measure LVAL 3
Measure From .000 PQGD 2
Measure Indicator .000 AQTY 3
Measure Indicator 5.410 CLSK 3
Measure Indicator 5.165 DELQ 3
Measure Indicator 5.677 DQGD 3
Measure Indicator 5.677 DQGD 6
Measure Indicator LVAL 4
Measure Indicator 5.670 MOQY 4
Measure Indicator 5.140 OQTY 3
Measure Indicator 6.010 OUCT 2
Measure Indicator .000 PQGD 6
Measure Indicator 5.190 QADJ 3
Measure Indicator .000 QPER 3
Name Cat.Ref. Ident. Sub-Element
April 1995 Section B Page 89
Measure Indicator 5.194 QPRO 3
Measure Indicator 5.180 QTYC 3
Measure Indicator 5.150 QTYI 3
Measure Indicator 5.192 QTYP 3
Measure Indicator 5.175 QTYR 3
Measure Indicator 5.170 QUTF 3
Measure Indicator 5.595 RQTY 3
Measure Indicator 5.185 SQTY 3
Measure Indicator 6.026 UCRV 2
Measure Indicator 5.120 UNOR 3
Measure Indicator 5.167 UPLQ 3
Measure Indicator .000 XQTY 3
Measure Indicator 6.020 AUCT 2
Measure Indicator .000 PQGD 3
Measure of Weight WGHT 1
Message Date and Time 5.310 MEDT
Message Reference 1.090 MSRF
Message To 3.120 METO
Message Total .000 TVTP
Meter Location .000 MLOC
Meter Number .000 MTNR
Meter Sub-address MSAD
Method .000 AUTT 1
Minimum Ordering Value 5.675 MOVL 1
Minimum Ordering Quantity 5.670 MOQY 1
Minimum Storage Temperature 5.280 TMIN
Mixed VAT Rate Product Indicator 4.028 MIXI
Modifier Category .000 MCAT
Modifier Code .000 MCDE
Modifier Value .000 MVAL
Modifier Value .000 MVAL 1
Monthly Charge Deferred Value .000 MCDV
Multiple Newsagent MUNE