ORDERS
Purchase Order
‘APEX Profile’
Message Implementation Guidelines
Version
Description of updates
Date
V1.3 F
Update for ATICA RUSSIA FAX ORDERS
25th June 2008
V1.1 D
UNB - DE 0026- application reference - value changed for
SUPAPEXORV11. Group 5 Segment CTA & COM are added to
implement the FAX for APEX countries.
Also Added SERES Comment concerning FAX.
4
thJune 2008
V1.0 F
First version. This MIG is the ECR RUSSIA Purchase Order based
on EANCOM 2002 S3 Version 1.10
ORDERS - APEX profile for suppliers
Level 0 Level 1 Level 2 Level 3UNA
C 1 1UNB
M 1 2UNH
M 1 3BGM
M 1 4DTM
M 4 5FTX
C 1 9SG1
C 1RFF
M 1 10SG2
C 99NAD
M 1 11SG3
C 99RFF
M 1 12SG5
C 1CTA
M 1 13COM
C 5 14SG7
M 1CUX
M 1 20 1ORDERS - APEX profile for suppliers
MIG Ref. : ORDERS V13F SUP;D01B;MBC; D01B; APEX based on ORDERS / EANCOM® 2002 S3; D.01B Page 4 Level 0 Level 1 Level 2 1
SG28
C 200000LIN
M 1 21IMD
M 99 22QTY
M 99 23SG32
C 25PRI
M 1 25SG34
C 99PAC
M 1 26UNS
M 1 27CNT
C 10 28UNT
M 1 29UNZ
M 1 30ORDERS - APEX profile for suppliers
Segment:
UNA
Seq. No.: 1 Status: C Level: Max. Occ.: 01Service string advice
To define the characters selected for use as delimiters and indicators in the rest of the interchange that follows.
Name: Description of segment: Service string advice
EDIFACT Application
Name St Format User Fmt. Use / Comments
UNA
UNA1 Component data element separator
M an1 M an1 : = Component data element separator
UNA2 Data element separator M an1 M an1 + = Data element separator
UNA3 Decimal notation M an1 M an1 . = Decimal separator
UNA4 Release indicator M an1 M an1 ? = Release indicator
UNA5 Reserved for future use M an1 M an1
UNA6 Segment terminator M an1 M an1 ' = Segment terminator
Comment: Example:
ORDERS - APEX profile for suppliers
Segment:
UNB
Seq. No.: 2 Status: M Level: Max. Occ.: 01Interchange header
To start, identify and specify an interchange.
Name: Description of segment: Interchange header
EDIFACT Application
Name St Format User Fmt. Use / Comments
UNB
S001 Syntax identifier M M
0001 Syntax identifier M a4 M a4 UNOA = UN/ECE level A
UNOC = UN/ECE level C - Danish, Dutch, English, Faeroese,
Finnish, French, German, Icelandic, Irish, Italian, Norwegian, Portuguese, Spanish, Swedish
UNOD = UN/ECE level D - Albanian, Czech, English,
Hungarian, Polish, Romanian, Serbo-Croatian, Slovak, Slovene
UNOE = UN/ECE level E - Bulgarian, Byelorussian, English,
Macedonian, Russian, Serbo-Croatian, Ukrainian
UNOF = UN/ECE level F - Greek UNOK = UN/ECE level K - Turkish
0002 Syntax version number M n1 M n1 3 = Version 3
S002 Interchange sender M M
0004 Sender identification M an..35 M an..35 Global location number - EAN 13 0007 Partner identification code
qualifier
C an..4 C an..4 14 = EAN International
0008 C N S003 Interchange recipient M M
0010 Recipient identification M an..35 M an..35 Global location number - EAN 13 0007 Partner identification code
qualifier
C an..4 C an..4 14 = EAN International
0014 C N S004 Date/time of preparation M M
0017 Date of preparation M n6 M n6 Date of preparation - format is YYMMDD 0019 Time of preparation M n4 M n4 Time of preparation - format is HHMM
0020 Interchange control reference M an..14 M an..14 Unique reference for a couple (sender, recipient) assigned by the sender of the interchange
S005 C N 0022 M N 0025 C N
0026 Application reference C an..14 M an..14 SUPAPEXORV13MB 0029 C N
0031 Acknowledgement request C n1 M n1 1 = Requested
The acknowledgement is requested for all trading partners EDI and Web-EDI through "EDI CONNECT"
0032 C N
0035 Test indicator C n1 C n1 1 = Interchange is a test
Could be generated after agreement with the trading partners during test phase
Comment:
DE's 0026: Indicates the application reference managed by Carrefour.
The application reference of the interchange is "SUPAPEXORV13MB"
2 Examples: The first one is for Russia with test indicator. The second is for Romania without test indicator.
UNB+UNOE:3+4680001859997:14+4670001659017:14+080430:1446+CAR000001++SUPAPEXORV13MB++1++1' UNB+UNOD:3+4680001859997:14+4670001659017:14+080430:1446+CAR000001++SUPAPEXORV13MB++1'
ORDERS - APEX profile for suppliers
Segment:
UNH
Seq. No.: 3 Status: M Level: Max. Occ.: 01Message header
A service segment starting and uniquely identifying a message. The message type code for the Purchase order message is ORDERS.
Note:
Purchase order messages conforming to this document must contain the following data in segment UNH, composite S009:
Data element 0065 ORDERS 0052 D
0054 01B 0051 UN
Name: Description of segment: Message header
EDIFACT Application
Name St Format User Fmt. Use / Comments
UNH
0062 Message reference number M an..14 M an..14 Sender's unique message reference. Sequence number of the message in the interchange. DE 0062 in the UNT will be exactly the same. Sender generated
S009 Message identifier M M
0065 Message type M an..6 M an..6 ORDERS = Purchase order message
0052 Message version number M an..3 M an..3 D = Draft version/UN/EDIFACT Directory
0054 Message release number M an..3 M an..3 01B = Release 2001 - B
0051 Controlling agency M an..2 M an..2 UN = UN/CEFACT
0057 Association assigned code C an..6 M an..6 EAN010 = EAN version control number (EAN Code)
Indicate that the message is the EANCOM version 010 of the UNSM Purchase Order.
0068 C N S010 C N 0070 M N 0073 C N
Comment:
This segment is used to head, identify and specify a message.
DE's 0065, 0052, 0054, and 0051: Indicate that the message is an UNSM Purchase Order based on the D.01B directory under the control of the United Nations.
Example:
UNH+123456789+ORDERS:D:01B:UN:EAN010'
This is an order message from Eancom subset, D01B version. Related message number in the interchange is 123456789
ORDERS - APEX profile for suppliers
Segment:
BGM
Seq. No.: 4 Status: M Level: Max. Occ.: 01Beginning of message
A segment by which the sender must uniquely identify the order by means of its name and number and when necessary its function.
Name: Description of segment: Beginning of message
EDIFACT Application
Name St Format User Fmt. Use / Comments
BGM
C002 Document/message name C M
1001 Document name code C an..3 M an..3 220 = Order
All references other than the document number DE1004 are in the RFF segment
1131 C N 3055 C N
1000 Document name C an..35 M an..35 ORDERS C106 Document/message identification C M
1004 Document identifier C an..35 M an..35 Order Number assigned by document sender. 1056 C N
1060 C N
1225 Message function code C an..3 M an..3 9 = Original
An original transmission of a purchase order.
4343 C N
Comment:
This segment is used to indicate the type and function of a message and to transmit the identifying number.
All references other than the document number DE 1004 are to be put in the RFF segment.
DE 1000 : Document name is "ORDERS" .
DE 1004: It is recommended that the length of the document number be restricted to a maximum of 17 characters. Theorder number is assigned by the sender.
DE 1225: The message function, coded is a critical data element in this segment. It applies to all data indicated in the message. The following definition apply for the restricted code:
9 = Original - An original transmission of an inventory report.
Example:
BGM+220:::ORDERS+12345678+9'
ORDERS - APEX profile for suppliers
Segment:
DTM
Seq. No.: 5 Status: M Level: Max. Occ.: 14Date/time/period
A segment specifying general dates and, when relevant, times related to the whole message. The segment must be specified at least once to identify the order date.
Examples of the use of this DTM segment are: Lead times that apply to the whole of the Order and, if no schedule is to be specified, the delivery date.
The Date/time/period segment within other Segment group should be used whenever the date/ time/period requires to be logically related to another specified data item. e.g. Payment due date is specified within the PAT Segment group.
Name: Description of segment: Date/time/period
EDIFACT Application
Name St Format User Fmt. Use / Comments
DTM
C507 Date/time/period M M 2005 Date or time or period function
code qualifier
M an..3 M an..3 137 = Document/message date/time 2 = Delivery date/time, requested 63 = Delivery date/time, latest 64 = Delivery date/time, earliest
2380 Date or time or period value C an..35 M an..35 Document/message date/time Delivery date/time, requested Delivery date/time, latest Delivery date/time, earliest 2379 Date or time or period format
code
C an..3 M an..3 102 = CCYYMMDD 203 = CCYYMMDDHHMM
Comment:
This segment is used to specify the document date, the delivery date, the earliest delivey date and the latest delivery date of the Order.
DE 2005: Identification of the 'Document/message date/time' (code value 137) is mandatory in an EANCOM message.
At least one of the 3 delivery date/time is mandatory. For EDI DTM+137 is used with DTM+2
For FAX DTM+137 is used with DTM+64 and DTM+63
Example:
ORDERS - APEX profile for suppliers
Segment:
FTX
Seq. No.: 9 Status: C Level: Max. Occ.: 11Free text
A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer
exchanges such text will normally require the receiver to process this segment manually.
Name: Description of segment: Free text
EDIFACT Application
Name St Format User Fmt. Use / Comments
FTX
4451 Text subject code qualifier M an..3 M an..3 PUR = Purchasing information
4453 Free text function code C an..3 M an..3 1 = Text for subsequent use
C107 C N 4441 M N 1131 C N 3055 C N C108 Text literal C D
4440 Free text value M an..512 M an..512 Free text Comments 4440 C N 4440 C N 4440 C N 4440 C N 3453 C N 4447 C N Comment:
This conditional segment is used to provide free form or coded text information for the entire purchase order.
Example:
FTX+PUR+1++Confirmation of the august 23rd order done by phone'
ORDERS - APEX profile for suppliers
Group: SG1 Status: C Max. Occ.: 1 RFF
Segment:
RFF
Seq. No.: 10 Status: M Level: Max. Occ.: 11Reference
A segment identifying the reference by its number and where appropriate a line number within a document.
Name: Description of segment: Reference
EDIFACT Application
Name St Format User Fmt. Use / Comments
RFF
C506 Reference M M
1153 Reference code qualifier M an..3 M an..3 ACD = Additional reference number
1154 Reference identifier C an..70 M an..70 Buyer reference number 1156 C N
4000 C N 1060 C N
Comment:
This segment is used to allow the correlation of the ORDER with the APERAK message.
Example:
RFF+ACD:26862'
ORDERS - APEX profile for suppliers
Group: SG2 Status: C Max. Occ.: 99 NAD-SG3-SG5
Segment:
NAD
Seq. No.: 11 Status: M Level: Max. Occ.: 11Name and address
A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the order. Identification of the seller and buyer parties is mandatory for the order message. It is recommended that where possible only the coded form of the party ID should be specified e.g. The Buyer and Seller are known to each other, thus only the coded ID is required, but the Consignee or Delivery address may vary and would have to be clearly specified, preferably in structured format.
Name: Description of segment: Name and address
EDIFACT Application
Name St Format User Fmt. Use / Comments
NAD
3035 Party function code qualifier M an..3 M an..3 BY = Buyer DP = Delivery party IV = Invoicee SU = Supplier
C082 Party identification details C C
3039 Party identifier M an..35 M an..35 Supplier GLN -Format n13 Internal supplier code 1131 C N
3055 Code list responsible agency code
C an..3 M an..3 9 = EAN (International Article Numbering association)
92 = Assigned by buyer or buyer's agent
C058 C N 3124 M N 3124 C N 3124 C N 3124 C N 3124 C N C080 Party name C C
3036 Party name M an..35 M an..35 Party identifier name 3036 C N 3036 C N 3036 C N 3036 C N 3045 C N C059 Street C C
3042 Street and number or post office box identifier
M an..35 M an..35 Party identifier address 3042 C N
3042 C N 3042 C N
3164 City name C an..35 C an..35 Party identifier City name C819 C N
3229 C N 1131 C N 3055 C N 3228 C N
ORDERS - APEX profile for suppliers
Segment:
NAD
Seq. No.: 11 Status: M Level: Max. Occ.: 11Name and address
EDIFACT Application
Name St Format User Fmt. Use / Comments
3207 C N
Comment:
This segment is used to identify the trading partners involved in the Order process. Identification of the buyer and supplier of goods and services is mandatory using DE's 3035 and C082. Additionally, the invoicee and/or delivery party should be specified if different to the buyer.
The delivery address given in NAD at header level is the main delivery address for all line items.
NAD+DP will be followed by segment RFF+YC1 to identify the store code and the RFF+ACD to identify the Establishment code.
Example for DP qualifier :
NAD+DP+4607077429992::9++CARREFOUR MOSCOW+101 BOL NIKITSKAYA ULITSA:ADDITIONAL INFORMATION+MOSCOW++24024'
RFF+YC1:12987' RFF+ACD:01'
NAD+SU will be followed by segment RFF+VA to identify the VAT registration number and both segment CTA+IC and segment COM to identify the fax number.
First example for SU qualifier:
NAD+SU+4607077429992::9++SUPPLIER1 MOSCOU+24 BOL NIKITSKULITSA+MOSCOU++103009' RFF+VA:RU87765432'
CTA+IC'
COM+0033169479417:FX'
Second example for SU qualifier (without GLN) :
NAD+SU+0012345::92++SUPPLIER1 MOSCOU+24 BOL NIKITSKULITSA+MOSCOU++103009' RFF+VA:RU87765432'
CTA+IC'
COM+0033169479417:FX'
NAD+BY will be followed by segment RFF+SD to identify the Order section.
Example for BY qualifier : NAD+BY+4607077429994::9' RFF+SD:10'
Example:
NAD+SU+4607077429992::9++SUPPLIER1 MOSCOU+24 BOL NIKITSKAYA ULITSA+MOSCOU++103009'
ORDERS - APEX profile for suppliers
Group: SG2 Status: C Max. Occ.: 99 NAD-SG3-SG5
Group: SG3 Status: C Max. Occ.: 99 RFF
Segment:
RFF
Seq. No.: 12 Status: M Level: Max. Occ.: 21Reference
A segment identifying the reference by its number and where appropriate a line number within a document.
Name: Description of segment: Reference
EDIFACT Application
Name St Format User Fmt. Use / Comments
RFF
C506 Reference M M
1153 Reference code qualifier M an..3 M an..3 VA = VAT registration number ACD = Additional reference number
YC1 = Additional party identification (EAN Code) SD = Sales department number
1154 Reference identifier C an..70 M an..70 Supplier fiscal number Establishment code Internal store code Sales department number 1156 C N
4000 C N 1060 C N
Comment:
This segment is used to specify reference numbers related to the party specified in the previous NAD segment.
Example for store code : RFF+YC1:1298'
Example for sales department : RFF+SD:10'
Example for Establishment code : RFF+ACD:01'
Example:
RFF+VA:RU56225432'
ORDERS - APEX profile for suppliers
Group: SG2 Status: C Max. Occ.: 99 NAD-SG3-SG5
Group: SG5 Status: C Max. Occ.: 1 CTA-COM
This Group is used to specify the Contact information and Fax number when the ORDERS is sent by FAX. It must be associed with the Supplier (SU Qualifier) NAD segment
Segment:
CTA
Seq. No.: 13 Status: M Level: Max. Occ.: 21Contact information
A segment to identify a person or department, and their function, to whom communications should be directed.
Name: Description of segment: Contact information
EDIFACT Application
Name St Format User Fmt. Use / Comments
CTA
3139 Contact function code C an..3 M an..3 IC = Information contact
C056 C N 3413 C N 3412 C N Comment: Example: CTA+IC'
ORDERS - APEX profile for suppliers
Group: SG2 Status: C Max. Occ.: 99 NAD-SG3-SG5
Group: SG5 Status: C Max. Occ.: 1 CTA-COM
This Group is used to specify the Contact information and Fax number when the ORDERS is sent by FAX. It must be associed with the Supplier (SU Qualifier) NAD segment
Segment:
COM
Seq. No.: 14 Status: C Level: Max. Occ.: 35Communication contact
A segment to identify a communications type and number for the contact specified in the CTA segment.
Name: Description of segment: Communication contact
EDIFACT Application
Name St Format User Fmt. Use / Comments
COM
C076 Communication contact M M
3148 Communication address identifier M an..512 M an..512 Fax number 3155 Communication address code
qualifier
M an..3 M an..3 FX = Fax
Comment:
This Segment is used to specify the Fax number of the supplier
Example:
COM+0033169479417:FX'
ORDERS - APEX profile for suppliers
Group: SG7 Status: M Max. Occ.: 1 CUX
Segment:
CUX
Seq. No.: 20 Status: M Level: Max. Occ.: 11Currencies
A segment identifying the currencies required in the order e.g. the order currency. A rate of exchange may be given to convert a reference currency into a target currency.
Name: Description of segment: Currencies
EDIFACT Application
Name St Format User Fmt. Use / Comments
CUX
C504 Currency details C M
6347 Currency usage code qualifier M an..3 M an..3 2 = Reference currency
6345 Currency identification code C an..3 M an..3 ISO 4217 three alpha.
Examples: EUR – USD – RUB – RON 6343 Currency type code qualifier C an..3 M an..3 9 = Order currency
6348 C N C504 C N 6347 M N 6345 C N 6343 C N 6348 C N 5402 C N 6341 C N Comment:
This segment is used to specify currency information for the complete order.
Example:
CUX+2:RUB:9' CUX+2:RON:9’
Currency is RUB – Russian ruble Currency is RON – Romanian New Leu Etc…
ORDERS - APEX profile for suppliers
Group: SG28 Status: C Max. Occ.: 200000 LIN-IMD-QTY-SG32-SG34
Segment:
LIN
Seq. No.: 21 Status: M Level: Max. Occ.: 11Line item
A segment identifying the line item by the line number and configuration level, and additionally, identifying the product or service ordered. Other product identification numbers e.g. Buyer product number, etc. can be specified within the following PIA segment.
Name: Description of segment: Line item
EDIFACT Application
Name St Format User Fmt. Use / Comments
LIN
1082 Line item identifier C an..6 M an..6 Application generated number of the count of the order lines.
1229 C N C212 Item number identification C M
7140 Item identifier C an..35 M an..35 Format n..14
GTIN - this is the number of the article being ordered.
7143 Item type identification code C an..3 M an..3 SRV = EAN.UCC Global Trade Item Number
1131 C N 3055 C N C829 C N 5495 C N 1082 C N 1222 C N 7083 C N Comment:
This segment is used to identify the item being ordered. Global Trade Item Numbers are mandatory in the LIN segment.
The detail section of the Purchase Order is formed by a repeating group of segments, always starting with the LIN segment.
Example:
LIN+1++4602345111115:SRV'
ORDERS - APEX profile for suppliers
Group: SG28 Status: C Max. Occ.: 200000 LIN-IMD-QTY-SG32-SG34
Segment:
IMD
Seq. No.: 22 Status: M Level: Max. Occ.: 299Item description
A segment for describing the product or service being ordered as well as product characteristic. This segment should be used for products or services that cannot be fully identified by a product code or article number.
Name: Description of segment: Item description
EDIFACT Application
Name St Format User Fmt. Use / Comments
IMD
7077 Description format code C an..3 M an..3 F = Free-form
C272 Item characteristic C M
7081 Item characteristic code C an..3 M an..3 ANM = Article name (EAN Code)
1131 C N 3055 C N C273 Item description C M 7009 C N 1131 C N 3055 C N
7008 Item description C an..256 M an..256 Item description 7008 C N
3453 C N 7383 C N
Comment:
This segment is used to describe the current line item.
It is recommended that this segment only be used for coded descriptions. Data element 7008 in clear text should only be used when no product code is available or when free-form descriptions are required by trading partners.
Example:
IMD+F+ANM+:::white paper A4 format'
ORDERS - APEX profile for suppliers
Group: SG28 Status: C Max. Occ.: 200000 LIN-IMD-QTY-SG32-SG34
Segment:
QTY
Seq. No.: 23 Status: M Level: Max. Occ.: 299Quantity
A segment identifying the product quantities e.g. ordered quantity.
Name: Description of segment: Quantity
EDIFACT Application
Name St Format User Fmt. Use / Comments
QTY
C186 Quantity details M M
6063 Quantity type code qualifier M an..3 M an..3 21 = Ordered quantity
59 = Number of consumer units in the traded unit
6060 Quantity M an..35 M an..35 Ordered quantity
Number of consumer units in the traded unit 6411 C N
Comment:
This segment is used to specify the total quantity ordered for the current line identified in the LIN segment.
Example: QTY+59:100'
There is 100 consumer unit in the traded unit
Example:
QTY+21:500'
ORDERS - APEX profile for suppliers
Group: SG28 Status: C Max. Occ.: 200000 LIN-IMD-QTY-SG32-SG34
Group: SG32 Status: C Max. Occ.: 25 PRI
Segment:
PRI
Seq. No.: 25 Status: M Level: Max. Occ.: 21Price details
A segment to specify the price type and amount. The price used in the calculation of the line amount will be identified as 'price'.
Name: Description of segment: Price details
EDIFACT Application
Name St Format User Fmt. Use / Comments
PRI
C509 Price information C M
5125 Price code qualifier M an..3 M an..3 AAA = Calculation net
5118 Price amount C n..15 M n..15 Net unit price 5375 C N
5387 Price specification code C an..3 M an..3 NTP = Net unit price
5284 C N 6411 C N 5213 C N
Comment:
This segment is mandatory, it will precise the net unit price of the item identified in the LIN segment.
The calculation price detailed in the Purchase Order will always be the Net Unit Price, i.e., Gross Price + Charges - Allowances.
The currency code for this price can be found in the CUX segment at header level.
Example:
PRI+AAA:65.50::NTP'
ORDERS - APEX profile for suppliers
Group: SG28 Status: C Max. Occ.: 200000 LIN-IMD-QTY-SG32-SG34
Group: SG34 Status: C Max. Occ.: 99 PAC
Segment:
PAC
Seq. No.: 26 Status: M Level: Max. Occ.: 21Package
A segment specifying the number of packages and the physical type of packaging for the line item e.g. pallet type.
Name: Description of segment: Package
EDIFACT Application
Name St Format User Fmt. Use / Comments
PAC
7224 Package quantity C n..8 M n..8 Number of packages for ordered item C531 C N
7075 C N 7233 C N 7073 C N C202 Package type C C
7065 Package type description code C an..17 C an..17 CT = Carton PX = Pallet 1131 C N 3055 C N 7064 C N C402 C N 7077 M N 7064 M N 7143 C N 7064 C N 7143 C N C532 C N 8395 C N 8393 C N Comment:
A segment specifying the number of packages and the physical type of despatch unit for the line item such as pallet or carton.
Example:
PAC+100++CT'
ORDERS - APEX profile for suppliers
Segment:
UNS
Seq. No.: 27 Status: M Level: Max. Occ.: 01Section control
A service segment placed at the start of the summary section to avoid segment collision.
Name: Description of segment: Section control
EDIFACT Application
Name St Format User Fmt. Use / Comments
UNS
0081 Section identification M a1 M a1 S = Detail/summary section separation
Comment:
This segment is used to separate the detail and summary sections of the message.
Example:
UNS+S'
ORDERS - APEX profile for suppliers
Segment:
CNT
Seq. No.: 28 Status: C Level: Max. Occ.: 110Control total
A segment by which control totals may be provided by the sender for checking by the receiver.
Name: Description of segment: Control total
EDIFACT Application
Name St Format User Fmt. Use / Comments
CNT
C270 Control M M
6069 Control total type code qualifier M an..3 M an..3 2 = Number of line items in message
6066 Control total value M n..18 M n..18 Number of line items in message 6411 C N
Comment:
This segment is used to provide message control totals.
Example:
CNT+2:1'
ORDERS - APEX profile for suppliers
Segment:
UNT
Seq. No.: 29 Status: M Level: Max. Occ.: 01Message trailer
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
Name: Description of segment: Message trailer
EDIFACT Application
Name St Format User Fmt. Use / Comments
UNT
0074 Number of segments in the message
M n..6 M n..6 The total number of segments in the message is detailed here.
0062 Message reference number M an..14 M an..14 The message reference number detailed here should
equal the one specified in the UNH segment.
Comment:
This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message.
Example:
UNT+27+123456789'
ORDERS - APEX profile for suppliers
Segment:
UNZ
Seq. No.: 30 Status: M Level: Max. Occ.: 01Interchange trailer
To end and check the completeness of an interchange.
Name: Description of segment: Interchange trailer
EDIFACT Application
Name St Format User Fmt. Use / Comments
UNZ
0036 Interchange control count M n..6 M n..6 Number of messages in the interchange
0020 Interchange control reference M an..14 M an..14 Unique reference assigned by a sender to an interchange (for the related recipient)
Comment: Example:
UNZ+1+CAR000001'
