PSIST ISO 9735:1996
(Main)Electronic data interchange for administration, commerce and transport (EDIFACT) -- Application level syntax rules
Electronic data interchange for administration, commerce and transport (EDIFACT) -- Application level syntax rules
La présente Norme internationale définit les règles syntaxiques pour la préparation des messages destinés à être échangés entre les intervenants dans les domaines de l'administration, du commerce et du transport. NOTE -- Pour les utilisateurs de la présente Norme internationale, il convient de noter que les règles de syntaxe qui y sont spécifiées font partie du Répertoire pour l'Échange de Données Commerciales des Nations Unies. Elles peuvent être utilisées dans toute application, mais les messages utilisant ces règles de syntaxe ne peuvent être référencés comme des messages EDIFACT que s'ils sont conformes aux quatre règles et répertoires de l'UNTDID (Répertoire pour l'Échange de Données Commerciales des Nations Unies) et s'ils ont été approuvés par la Commission Économique pour l'Europe des Nations Unies (CEE/ONU).
Échange de données informatisées pour l'administration, le commerce et le transport (EDIFACT) -- Règles de syntaxe au niveau de l'application
Računalniško izmenjavanje podatkov v upravi, trgovini in prevozništvu (EDIFACT) - Pravila skladnje na uporabniški ravni
General Information
Relations
Standards Content (Sample)
IS0
INTERNATIONAL STANDARD
9735
First edition
1988-07-l 5
Amended and
reprinted
1990-l l-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION
ORGANISATION INTERNATIONALE DE NORMALISATION
MEXAYHAPOAHAH OPTAHM3AuMfl I-IO CTAHAAPTM3A~MM
Electronic data interchange for administration,
commerce and transport (EDIFACT) - Application
level syntax rules
kbange de don&es informa tisk pour l’administra tion, le commerce et le transport
(EDIFACTI - R&g/es de syn taxe au niveau de l’application
Reference number
IS0 9735 : 1988 (E)
---------------------- Page: 1 ----------------------
ISO9735:1988 EI
Contents
Page
iv
Foreword .
...........................................................
Introduction
1 Scope .
.................................................
2 Normative references
3 Definitions. .
........................................................
4 Syntaxlevels
.......................................................
. 5 Character sets
.............................................
5.1 Level A character set.
..............................................
5.2 Level B character set
6 Structures .
.............................................
6.1 Interchange structure
...........
6.2 Order of segments and groups of segments within a message
6.3 Segment structure .
............................................
6.4 Data element structure
......................................................
7 Compressing.
............................................
7.1 Exclusion of segments
..............................
7.2 Exclusion of data elements by omission
............................
7.3 Exclusion of data elements by truncation
...................
7.4 Exclusion of component data elements by omission
..................
Exclusion of component data elements by truncation
7.5
0 lnternatibnal Organization for Standardization, 1988 0
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISO9735:1988 E)
8 Repeti~on . 6
8.1 Repetition of segments . 6
8.1 .l Explicit indication of repetition . 6
8.1.2 Implicit indication of repetition . 6
8.2 Repetition of data elements . 7
................................................. 7
9 Nesting of segments
7
.......................................
9.1 Explicit indication of nesting
......................................... 9
9.2 Implicit nesting indication
10 Representation of numeric data element values . 9 ’
10.1 Decimal sign . 9
10.2 Triad separator . 9
9
10.3 Sign .
Annexes
A Definitions . 10
B Service segments specifications . 13
C Order of segments and grouts of segments within a message . 19
. . .
III
---------------------- Page: 3 ----------------------
IsOme (El
Foreword
IS0 (the International Organization for Standardization) is a worldwide federation of
national standards bodies (IS0 member bodies). The work of preparing International
Standards is normally carried out through IS0 technical committees. Each member
body interested in a subject for which a technical committee has been established has
the right to be represented on that committee. International organizations, govern-
mental and non-governmental, in liaison with ISO, also take part in the work. IS0
collaborates closely with the International Electrotechnical Commission (IEC) on all
matters of electrotechnical standardization.
Draft International Standards adopted by the technical committees are circulated to
the member bodies for voting. Publication as an International Standard requires
approval by at least 75 % of the member bodies casting a vote.
International Standard IS0 9735 was prepared by UN/ECE Trade Division (as
EDIFACT) and was adopted, under a special “fast-track procedure”, by Technical
Committee ISOITC 154, Documents and data elements in administration, commerce
and industry, in parallel with its approval by the IS0 member bodies.
Annexes A and B form an integral part of this International Standard. Annex C is for
information only.
Amended reprint, 1990
This amended reprint has been prepared to correct two ambiguities in the original text.
These concern segments UNG, SO08, and UNH, SOO9. The convention for assigning
message version number and message release number includes the last two digits of
the year. In order to avoid compression of leading zeroes in these fields, which is a
normal procedure in many computer programs when the data type is specified to be
numeric, and which would consequently distort the data, the data types for message
version number and message release number have been changed from numeric (n) to
alphanumeric (an). Additionally, experience has shown that the footnote which
appeared on page 17 of the 1988 edition has been misunderstood and in order to
provide clarification, the footnote has now been deleted and the status of the message
release number (0054) and controlling agency (0051) has been changed from
conditional to mandatory.
In order to allow time for users to change their systems, and to provide a
specific date for implementation of the changes, this amended and reprinted
first edition will become effective six months after the date of publication, i.e.
1 May 1991.
---------------------- Page: 4 ----------------------
ISO9735:1988 E)
Introduction
This international Standard includes, in a condensed form, the rules on application
level for the structuring of the user data and of the associated service data in the
interchange of messages in an open environment. These rules have been agreed by the
United Nations Economic Commission for Europe (UN/ECE) as syntax rules for
Electronic Data Interchange For Administration, Commerce and Transport (EDIFACT)
and are part of the ECE Trade Data Interchange Directory which also includes Message
Design Guidelines*). The Guidelines should be used in conjunction with this
International Standard.
The service specifications and protocols for Open Systems Interconnection (OSI)
based on the Reference Model in IS0 7498 and issued by ISO, CCITT, CENKENELEC
etc. may be followed for the communication of messages based on this International
Standard. Such specifications and protocols are outside the scope of this International
Standard.
Functional error ind icationkorrection can be handled specia I service messages
bY
following the syntax rules in this International Standard
*) Presently ECE Draft.
---------------------- Page: 5 ----------------------
This page intentionally left blank
---------------------- Page: 6 ----------------------
IS0 9735 : 1988 (E)
INTERNATIONAL STANDARD
Electronic data interchange for administration,
commerce and transport (EDIFACT) - Application
level syntax rules
1 Scope
This International Standard gives syntax rules for the preparation of messages to be interchanged between partners in the fields of
administration, commerce and transport.
NOTE - Users of this International Standard should note that the syntax rules specified herein are part of the United Nations Trade
Data Interchange Directory (UNTDID). They may be used in any application, but messages using these syntax rules may only be re-
ferred to as EDIFACT messages if they comply with other rules and directories in UNTDID and if they have been approved by the United
Nations Economic Commission for Europe (UN/ECE).
2 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this International Standard.
At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based
on this International Standard are encouraged to investigate the possibility of applying the most recent editions of the standards listed
below. Members of IEC and IS0 maintain registers of currently valid International Standards.
IS0 31-O : 1981, General principles concerning quantities, units and symbols.
- IS0 7-bit coded character set for information interchange.
IS0 646 : 1983, Information processing
IS0 2382-l : 1984, Data processing - Vocabulary - Part 01: Fundamental terms.
IS0 2382-4 : 1987, Data processing - Vocabulary - Part 04: Organization of data.
IS0 6523 : 1984, Data interchange - S true tures for the identification of organizations.
IS0 6937-2 : 1983, Information processing - Coded character sets for text communication - Part 2: Latin alphabetic and
non-alphabe tic graphic characters.
IS0 7372 : 1986, Trade data interchange - Trade Data Elements Directory.
I SO 7498 : 1984, lnforma tion processing systems - Open Systems Interconnection - Basic Reference Model.
processing - 8 bit single-byte coded graphic character sets -
IS0 8859 : 1987, Information
1.
Part 7: Latin alphabet No.
2.
Part 2: Latin alphabet No.
---------------------- Page: 7 ----------------------
IS0 9735 : 1988 (E)
3 Definitions
For the purpose of this International Standard, the definitions in annex A apply.
4 Syntax levels
This International Standard specifies syntax levels A and B which are identical in all respects except for the character sets used.
As requirements for additional syntactical features appear, further levels may be added.
level A shall use only the cha set specified in 5.1, and
Unless interchange partners agree to use other or add itional characters
I
level B only the character set specified in 5.2.
the separator and other
The conditional Service String Advice, UNA, (see annex B) provides the capability
characters used in the interchange in case they differ from those in clause 5.
5 Character sets
For the characters in the sets below, the 7-bit codes in the basic code table in IS0 646 shall be used, unless the corresponding 8-bit
codes in IS0 6937 and IS0 8859 or other bit codes are specifically agreed between the interchanging partners. See clause 4.
5.1 Level A character set
Letters, upper case A to Z
Numerals 0 to 9
Space character
Full stop .
Comma
I
Hyphen/minus sign -
Opening parenthesis
(
Closing parenthesis
1
Oblique stroke (slash) I
=
Equals sign
Apostrophe
’ Reserved for use as segment terminator
Plus sign
+ Reserved for use as segment tag and data element separator
Colon
: Reserved for use as component data element separator
Question mark ? Reserved for use as release character
? immediately preceding one of the characters ’ + : ? restores their normal meaning. For example, lo? + 10 = 20 means
10 + 10 = 20. Question mark is represented by ??.
The following characters are part of the level A character set but cannot be used internationally in telex transmissions=
Exclamation mark !
I1
Quotation mark
Percentage sign %
at
Ampersand
*
Asterisk
.
Semicolon
9
<
Less-than sign
>
Greater-than sign
---------------------- Page: 8 ----------------------
IS0 9735 : 1988 (E)
5.2 Level B character set
This character set is not intended for transmission to telex machines.
A to Z
Letters, upper case
a to z
Letters, lower case
Numerals 0 to 9
Space character
Full stop .
Comma
1
Hyphen/minus sign
Opening parenthesis
(
Closing parenthesis
)
Oblique stroke (slash) /
I
Apostrophe
Plus sign +
.
Colon .
=
Equals sign
Question mark ?
Exclamation mark !
II
Quotation mark
Percentage sign %
Ampersand &
*
Asterisk
Semi-colon
;
Less-than sign <
Greater-than sign >
Information separator IS 4 segment terminator
Information separator IS 3 data element separator
Information separator IS 1 component data element separator
6 Structures
6.1 Interchange structure
The Service String Advice, UNA, and the service segments UNB to UNZ shall appear in the order stated below in an interchange. There
may be several functional groups or messages within an interchange and several messages in a functional group. A message consists of
segments. The structures for segments and for data elements therein are shown in 6.2 and 6.3. The contents of the service segments
are shown in annex B. See also figure 1.
An interchange consists of:
Service String Advice UNA Conditional
Interchange Header UNB Mandatory
Functional Group Header UNG Conditional
Message Header UNH Mandatory
As required
User Data Segments
r-
Mandatory
Message Trailer UNT
C
Conditional
Functional Group Trailer UNE
Mandatory
Interchange Trailer UNZ
In addition to the above service segments, the service segment UNS can, when required, be used to divide a message into sections.
See annex B.
---------------------- Page: 9 ----------------------
IS0 9735 : 1988 (El
EXAMPLES illustrating segment sequences:
a) A single message within a functional group: UNA UNB UNG UNH. Data Segments.UNT UNE UNZ
b) A single message without functional grouping: UNA UNB UNH. Data Segments.UNT UNZ
c) A single message without functional grouping and without UNA: UNB UNH . . . Data Segments.UNT UNZ
~-1-m-11--e ~----------~~--~~~~-~----
1 A CONNECTION contains one or more interchanges.
c
c 1
The technical protocols for establishment, main-
1 Establishment ’ CONNECTION : Termination ’
c 1
tenance and termination etc. are not part of this
l-I ---mm JCI -*--1-1--1---1 1 ,,Am---- ----,I
. a
+
*
. International Standard.
*
6
l
w m
& .
6 w
a
*
. w
6 a
. l An INTERCHANGE contains :
e -
6 c
-
l
a
4
*
T - UNA, Service String Advice, if used
- UNB, Interchange Header
Interchange INTERCHANGE Interchange
Either only Functional Groups, if used, or only
-
\
Messages
- UNZ, Interchange Trailer
A FUNCTIONAL GROUP contains:
- UNG, Functional Group Header
Either
or only
UNA UNB ’
- Messages of the same type
FUNCTION GRPS
MESSAGES UNZ ’
.
- UNE, Functional Group Trailer
0 /
A MESSAGE contains :
I I 1
I I I I
- UNH, Message Header
1 UNG 1 ‘1 Message
MESSAGE 1 Message I UNE 1’ 1
- Data Segments
- UNT, Message Trailer
A SEGMENT contains:
t I I I I I I 1
- A segment Tag
t Data DATA Data
UNH UNT ’
Segment SEGMENT Segment
- Simple data elements or
Composite data elements or both as applicable
-
A SEGMENT TAG contains:
SIMPLE
COMPOSITE
Q
- A segment code and, if explicit indication,
TAG + DATA ELEMENT +
DATA ELEMENT
I II I I I I
b repeating and nesting value(s). See 8.1 and
clause 9.
A SIMPLE DATA ELEMENT contains:
- A single data element value
COMPONENT . COMPONENT
Code : Value Value
A COMPOSITE DATA ELEMENT contains:
DATA ELEM. ’ DATA ELEM.
II b
- Component data elements
\ / \ /
A COMPONENT DATA ELEMENT contains:
-
A single data element value
---
means alternative to
UNA, UNB, UNZ, UNG, UNE, UNH and UNT are Service Segments; see 6.1 and
annex B.
In the diagram, the level A separators/terminators have been used; see 5.1.
Figure 1 -
Hierarchical structure of an nterchange
---------------------- Page: 10 ----------------------
IS0 9735 : 1988 (El
6.2 Order of segments and groups of segments within a message
A message structure diagram and the order of the segments following the processing rules in the ECE Message Design Guidelines
is shown in annex C.
6.3 Segment structure
Segment Tag, composed of Mandatory
Segment Code Mandatory component data element
Conditional
Component data element separator
Nesting and repeating indication Conditional component data element(s)
Data element separator Mandatory
Simple or composite data elements Mandatory or conditional as specified in the relevant segments directory; see 6.4
Segment Terminator Mandatory
6.4 Data element structure
Simple Data Element, or Mandatory or conditional as in the relevant
Composite Data Element with segments directory
Component data elements and
Component data element separators Mandatory (see restriction below)
Data element separator Mandatory (see restrict ion below)
There shall be no component data element separator after the last component data element in a composite data element and no data
element separator after the last data element in a segment.
7 Compressing
In data elements for which the Data Elements Directory specifies variable length and there are no other restrictions, insignificant
character positions shall be suppressed. In the case of insignificant characters, leading zeroes and trailing spaces shall be
suppressed.
Note, however, that a single zero before a decimal sign is significant (see 10.1) and that a zero may be significant (e.g. to indicate a
temperature) if so stated in the data elements specification.
When compressing messages, the rules below shall be followed.
In the following examples of the rules, “Tag” represents a segment tag, “DE” a data element and “CE” a component data element. The
separators in level A in 5.1 are used.
7.1 Exclusion of segments
Conditional segments containing no data shall be omitted (including their segment tags).
7.2 Exclusion of data elements by omission
Data elements are identified by their sequential positions within the segment as stated in the Segment Directory. If a conditional data
element is omitted and is followed by another data element, its position shall be indicated by retention of its data element separator.
Tag+DE+DE+++DE+DE+DE ’
@ These two data elements are omitted
---------------------- Page: 11 ----------------------
IS0 9735 : 1988 (El
7.3 Exclusion of data elements by truncation
If one or more conditional data elements at the end of a segment are omitted, the segment may be truncated by the segment
terminator, i.e. contiguous trailing data element separators are not required to be transmitted.
Tag+DE+DE+++DE ’ Using the example from 7.2, the last two data elements have been omitted and the
- segment truncated
7.4 Exclusion of component data elements by omission
Component data elements are identified by their given sequential positions within a composite data element. If a conditional
component data element is omitted and is followed by another component data element, its given position must be represented by
its component data element separator.
Tag+DE+CE:CE+CE : : : CE ’
I Two component data elements omitted in the last composite data element
7.5 Exclusion of component data elements by truncation
One or more conditional component data elements at the end of a composite data element may be excluded by truncation by the
data element separator or, if at the end of a segment, by the segment terminator.
Tag+DE+CE+CE ’ Using the example from 7.4, the last component data element in the first composite data element has
I l
been omitted and also three component data elements in the last composite data element. In both cases
the composite data elements have been truncated, indicated in the first case by the data element
separator and in the second case by the segment terminator.
8 Repetition
8.1 Repetition of segments
es shall be used and this decision shall be taken during
Within a given message type, either explicit or implicit repetition techniqu
message.
message design. The two techniques shall not be mixed within the same
Indication of repetition shall either be explicit as a component data element being part of the segment tag composite data element that
heads a segment (see 8.1 .l and 9.1) or be implicitly understood from the sequence of the segments as stated in the relevant message
specification (see 8.1.2).
Segments at level 0 (see annex C) shall not be repeated and their tags include no repeating indication.
Service segments (see annex B), excluding TXT, shall not be repeated and their tags include no repeating indication.
8.1 .l Explicit indication of repetition
component data
In the segment : tag, the first component data element shall be the segment code and the last of the subsequent
elements shall indicate the incidence of repetition of the segment. See 9.1.
8.1.2 implicit indication of repetition
specification. Therefore it can be implicitly
The segme lnts within a message shall appear in the order stated in the messag
e tYPe
understood which segments are repeated, ide lntif ied by their ordinal positions.
---------------------- Page: 12 ----------------------
IS0 9735 : 1988 (E)
8.2 Repetition of data elements
Data elements (DE) shall not be repeated within a segment more than the number of times prescribed in the relevant segment directory.
If less, the exclusion rules in 7.2 to 7.5 shall apply.
Tag+.+DEl +DEl +++.I
- 2 of prescribed up to 4 repeats of DE1 omitted.
It is, however, sometimes practical to structure repeatable elements as component data elements (CE) in composite elements,
thereby allowing truncation by the data element separator. This may also apply to specified repeatable sequences of data elements,
e.g. the sequence CEI :CE2:CE3.
Tag+.+CEl :CE2:CE3:CEl :CE2:CE3+.’
L Truncation by the data element separator after 2 sequences.
9 Nesting of segments
A segment level in the message structure and consequently be nested in that
on a segment on a higher hierarchical
may
segment.
Within a given message type, either explicit or implicit nesting techniques shall be used and this decision shall be taken during
message design. The two techniques shall not be mixed within the same message.
Indication of nesting shall either be explicit as component data elements being part of the segment tag composite data element that
heads a segment (see 9.1) or be implicitly understood from the sequence of the segments as stated in the relevant message
specification *) (see 9.2).
Service segm ents (see annex B) and other segments at level 0 (see annex C) shall not be nested and their tags include no nesting
indication.
9.1 Explicit indication of nesting
e and followed conditional component
In the segment tag , the first component data element shall be the segment cod be
bY
elements indicating both the level and the incidence of repetitio In of the segment as sta ted in 8.1.1.
The number of component data elements used for this purpose depends upon the hierarchical level in which the segment appears in the
message structure diagram. See annex C. After the segment code, the next component data element (which is for the first control
count) shall be used if the segment appears at level one, the second as well if it appears at level two, the third as well at level 3, etc.
When a conditional segment on a higher level is not used in an application, the level indication shall show component data element
separators for the levels not used and the segment shall appear before segments which include an indication at that level. See examples
below.
l ) See ECE Message Design Guidelines
---------------------- Page: 13 ----------------------
IS0 9735 I 1988 (E)
EXAMPLES of messages using explicit repeating and nesting indication
Level A separators have been used in the examples.
See annex C for further diagram explanations.
EXAMPLE 1. Message with one level of mandatory segment nesting:
Segments Explanations
I I I
1
UNH AAA EEE UNT UNH+data’
Ml Ml
Cl Ml AAA+data’
I
BBB BBB : l+data’ Item 1 of BBB
M2 BBB : 2+data’ Item 2 of BBB
CCC : l+data’ Item 1 of CCC
DDD : 1 : l+data’ Item 1 of DDD in CCC(l)
DDD : 1:2+data’ Item 2 of DDD in CCC(l)
CCC : 2+data’ Item 2 of CCC
DDD : 2 : l+data’ Item 1 of DDD in CCC(2)
EEE+data’
UNT+data’
In string form:
UNH+data ’ AAA+data ’ BBB : l+data ’ BBB : 2+data ’ CCC : l+data ’ DDD : 1 : l+data ’ DDD : 1 : 2+data ’ CCC : 2+data ’
DDD : 2 : l+data ’ EEE+data ’ UNT+data ’
EXAMPLE 2. Message with two levels of conditional segment nesting which could be containers (CCC), boxes (DDD) and
goods items (EEE):
Level Explanations
Message Segments
0 UNH AAA UNT UNH+data’
I I
Ml Ml M 1 AAA+data’
I I
1 BBB ccc BBB : l+data’ Item 1 of BBB
M2 c 1 BBB : 2+data’ Item 2 of BBB
EEE : : : l+data’ Item 1 of EEE without DDD and CCC
I EEE : : : 2+data’ Item 2 of EEE without DDD and CCC
DDD CCC : l+data’ 1st occurrence of CCC
c9 DDD : 1 : l+data’ 1 st occurrence of DDD within CCC( 1)
EEE : 1 : 1 : l+data’ EEE(l) within DDD(l) within CCC(l
)
I EEE : 1 : 1 : 2+data’ EEE(2) within DDD(l) within CCC(1
1
EEE DDD : 1 : 2+data’ DDD(2) within CCC(l)
M9 EEE : 1 : 2 : l+data’ EEE(l) within DDD(2) within CCC(1
CCC : 2+data’ CCC(2)
M 20 EEE : 2 : : l+data’ EEE( 1) within CCC(2) without DDD
UNT+data’
In string form:
UNH+data ’ AAA+data ’ BBB : l+data ’ BBB : 2+data ’ EEE : : : l+data ’ EEE : : : 2+data ’ CCC : l+data ’ DDD : 1 : l+data ’
EEE : 1 : 1 : l+data ’ EEE : 1 : 1 : 2+data ’ DDD : 1 : 2+data ’ EEE : 1 : 2 : l+data ’ CCC : 2+data ’ EEE : 2 : : l+data ’ UNT+data ’
8
---------------------- Page: 14 ----------------------
Is0 9735 : 1988 (El
9.2 implicit nesting indication
The order of the segments specified in the message structure diagram (top to bottom, left to right) sh all be followed strictly. Thereby
the nesting relation between the segments is implicitly evident and no further indication is required fo r processing.
10 Representation of numeric data element values
10.1 Decimal sign
The IS0 representation for a decimal sign is the comma (,I but a point on the line (.I is allowed. See IS0 31-O : 1981. Both these
characters are part of the Level A and B sets in clause 5 and both alternatives are allowed.
When the Service String Advice, UNA, is used, its third character t0 represent
the one character used in the interchange
decimal sign and thus overrides the above alternative use.
The decimal sign shall not be counted as a character of the value when computing the maximu m field length of a data element.
However, allowance has to be made for the character in transmission and reception.
When a decimal sign is transmitted, there shall be at least one digit before a nd after the decimal sign. For values represented by integers
only, neither a decimal
sign nor decimal zeroes are used unless there is a need to indicate the degree of precision.
Preferred: 0,5 and 2 and 2,0 Not allowed: ,5 or .5 or 2, or 2.
Allowed: 0.5 and 2 and 2.0
IO.2 Triad separator
Triad separators shall not be used in interchange.
Allowed: 2500000
Notallowed: 2,500,000 or 2.500.000 or2 500 000
IO.3 Sign
Numeric data element values shall be regarded as positive. Altho ugh conceptually a deduction is n egative, it shall be represented
by a pos itive value and such cases shall be indicated in the data elements directory.
If a value is to be indicated as negative, it shall in transmission be immediately preceded by a minus sign, e.g. -112.
The minussign shall not becounted asacharacterof thevalue when computing the maximum field length of adata element. However,
allowance has to be made for the character in transmission and reception.
9
---------------------- Page: 15 ----------------------
IS0 9735 : 1988 (El
Annex A
(normative)
Definitions
Some terms in this International Standard have been defined in other IS0 standards and have been included for the benefit of the
reader. The responsibility for these terms, indicated by the number of the standard, rests with the committee concerned. In cases
where the definitions pertinent for this standard are restrictions of such terms with a wider concept, the indication “EDIFACT” is
used.
A.1 alphabetic character set: A character set that contains letters and may contain control characters and special characters
but not digits (IS0 2382/4)
A.2 alphanumeric character set: A character set that contains both letters and digits and may contain control characters and
special characters (IS0 2382/4)
A.3
application message type: A basic message type adapted to suit a certain application area
A.4 character set: A finite set of different characters that is considered complete for a given purpose (IS0 2382/4
A.5 common access reference: Key to relate all subsequent transfers of data to the same business file
A.6 component data element: A simple data element which is a subordinate portion of a composite data element and in
interchange identified by its position within the composite data element
ments inacom posite data
A.7 component element separator: A character to separate the corn nt data
pane
element
A.8 composite data element: A data element containing two or more component data elements
A.9 conditional: A statement in a segment or message directory of a condition for the use of a segment, a data element, a
composite data element or a component data element (cf. mandatory)
A.10 connection: An established link for transmission of data
A.1 1 data: A representation of facts, concepts or instructions in a formalized manner suitable for communication’ interpretation
or processing by human beings or by automatic means (IS0 2382/l)
A.1 2 data element: A unit of data which in a certain context is considered indivisible (IS0 2382/4)
EDIFACT: A unit of’data for which the identification’ description and value representation have been specified
data elements specifications as to how
A.13 d.irectory: A listing of identified, n amed and described data element attributes, with
the correspond ing data element values shall be represented
A.14 data element name: One or more words in a natural language identifying a data element concept
A.1 5 data element se
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.