Professional Documents
Culture Documents
Implementation Guideline
ORDERS Purchase Order
Example of conventions.............................................................................................................................................10
Segment Clarification................................................................................................................................................11
0. INTRODUCTION
This specification provides the definition of the Purchase order message (ORDERS) to be used in
Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and
transport.
1. SCOPE
A message specifying details for goods or services ordered under conditions agreed between the seller and
the buyer.
The UN Standard Purchase Order Message may be applied for both national and international trade. It is
based on universal commercial practice and is not dependent on the type of business or industry.
1.3 Principles
A purchase order may refer to goods items or services related to one or more delivery schedules, call-offs,
etc.
A purchase order for cross-border transactions may contain additional information for customs and/or
statistical purposes.
A purchase order may contain details for transport and destination as well as delivery patterns.
Status
Definition
A message specifying details for goods or services ordered under conditions agreed between the seller and the
buyer.
Principles
The EANCOM subset of the UNSM Purchase Order is intended to be used in day to day ordering transactions.
The recommended business practice is that one Purchase Order is placed for one delivery in one location at one
time.
It is however possible to request deliveries in several locations, by using Segment Group 33 (LOC-QTY-DTM) in
the detail section. Deliveries of this nature are termed split deliveries. Using the DTM (Date and Time) segment in
the detail section, makes it possible to request deliveries on different dates within the same purchase order. Split
deliveries may also take place to the same location on different dates over a period of time.
The Purchase Order message can be used to send blanket orders followed at a later date by a series of call-offs (both
message types can be identified precisely in the BGM segment with the appropriate coded identifier). The blanket
order specifies a global product quantity per line item to be ordered over a period of time. The subsequent call-offs
referring to the blanket order will request a part of the global quantity with specific delivery dates and locations.
The Purchase Order message can also be used to send rush orders i.e. orders requesting the immediate availability of
goods, using the appropriate coded identifier in the BGM segment.
BASIC
Basic orders are used when a quantity of product is ordered without specific mention of which store
location is to ultimately receive the merchandise. The entire lot is shipped to a distribution facility and will
be distributed to the various stores as needed. A Basic Purchase Order can be identified by an occurrence
of a header level NAD segment with a “BY” qualifier in NAD01 to specify the buying party, and the
absence of an SDQ segment in the Detail Section of the Order. The N1 Segment will identify the
distribution facility location issued in the D-U-N-S + 4 format.
SPREADSHEET
Spreadsheet Orders are those in which the product is ordered for multiple store locations and shipped
directly to those store locations. A Spreadsheet Purchase Order can be identified by the absence of a
header level NAD segment with a “BY” qualifier in NAD01, and the presence of Segment Group 25
(LOC-QTY) in the Detail section of the Purchase Order that specifies the various Store Numbers by their
associated EAN Location code.
CROSS-DOCK
Cross-Dock orders are used when the product ordered is pre-sorted by the vendor by store location, but
shipped to a distribution facility rather than to the store location. A Cross-Dock Purchase Order can be
identified by a NAD Segment with ST in NAD01, and Segment Group 25 (LOC-QTY) in the detail.
1. Every data element on each segment is listed in the Data Element Summary section of the segment
documentation.
2. Every data element has the UN/EDIFACT data element ID noted.
3. Every data element has the UN/EDIFACT data element title noted.
4. Every data element has the UN/EDIFACT data element attributes noted:
4.1 data element requirement designation
• Mandatory (M) This element must be used in either the segment or composite data element in
which it appears. (Mandatory data elements or composites in EDIFACT segments retain their
status in EANCOM and in Wal-Mart guidelines.)
• Conditional (C) This element is optional and may be included in the segment at the option of
the sender.
4.2 data element type and length
• a alphabetic characters
• n numeric characters
• an alpha numeric characters
• a3 3 alphabetic characters, fixed length
• n3 3 numeric characters, fixed length
• an3 3 alpha numeric characters, fixed length
• a..3 up to three alphabetic characters
• n..3 up to three numeric characters
• an..3 up to three alpha numeric characters
In data elements for which the Trade Data Elements Directory specifies variable length and no
other restrictions, non-significant character positions shall be suppressed. In the case of non-
significant characters, leading zeroes and trailing spaces shall be suppressed. “Coded” data
element values must be transmitted precisely as they are shown in the code list where they appear.
For transmission purposes, all numeric data element values shall be regarded as positive. Although
conceptually a deduction is negative, it shall be represented by a positive value. The application
will interpret the meaning of the data. If a value is to be represented as negative, it shall be
immediately preceded by a minus sign, e.g., -112. The minus sign shall not be counted when
computing the maximum field length of a data element.
The representation for a decimal sign is the point on the line (.). The decimal point shall not be
counted as a character when computing the maximum field length of a data element. When a
decimal point is transmitted, there shall be at least one digit before and after the decimal point. For
values represented by integers only, neither decimal point nor decimal zeroes are used unless there
is a need to indicate the degree of precision.
Triad separators shall not be used in an interchange. (Allowed: 2500000; Not allowed:
2,500,000 or 2.500.000 or 2 500 000.)
5. Wal-Mart utilizes EANCOM implementation guidelines, which specify five status types for data elements
with a Conditional (C) EDIFACT status whether for simple, component or composite data elements. The
EANCOM status is listed in the first column (to the left of the Data Element Number Column). The five
conditions are listed in the following table along with the designation that is used in Wal-Mart
implementation guides:
9
8 4
Data Element Summary
1
Data Component
Element Element Name Attributes
R C506 REFERENCE M
2 Identification of a reference.
R 1153 Reference qualifier M an..3
3 Code giving specific meaning to a reference segment or a reference number.
SD Sales department number 4.1
Heading Section:
UNH Message 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 96A 0051 UN
DTM Date/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.
RFF Reference
A segment identifying the reference by its number and where appropriate a line number within a document.
RFF Reference
A segment identifying the reference by its number and where appropriate a line number within a document.
CUX Currencies
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.
DTM Date/Time/Period
A segment giving the specific date/time/period, if needed, of any payments, discounts, instalments etc.
QTY Quantity
A segment identifying the type of quantity and the quantity related to the allowance or charge.
Detail Section:
Segment Group 25: LIN-PIA-IMD-MEA-QTY-PCD-ALI-DTM-MOA-GIN-GIR-QVR-DOC-PAI-FTX-
SG26-SG27-SG28-SG29-SG30-SG33-SG34-SG35-SG39-SG45-SG47-SG48-SG49-SG51-SG52
A group of segments providing details of the individual ordered items. This Segment group may be repeated to give
sub-line details.
QTY Quantity
A segment identifying the product quantities e.g. ordered quantity.
PAC Package
A segment specifying the number of packages and the physical type of packaging for the line item e.g.
pallet type.
QTY Quantity
A segment specifying the quantity to be delivered to the identified location.
QTY Quantity
A segment identifying the type of quantity and the quantity related to the allowance or charge.
Section Control:
UNS Section Control
A service segment placed at the start of the summary section to avoid segment collision.
Summary Section:
MOA Monetary Amount
A segment giving the total amounts for the whole order message.
Heading Section:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
Must Use 0010 UNH Message Header M 1
Must Use 0020 BGM Beginning of Message M 1
Must Use 0030 DTM Date/Time/Period M 35
Must Use 0030 DTM Date/Time/Period M 35
Must Use 0030 DTM Date/Time/Period M 35
Not Used 0040 PAI Payment Instructions C 1
Not Used 0050 ALI Additional Information C 5
Not Used 0060 IMD Item Description C 1
0070 FTX Free Text C 99
0080 Segment Group 1: RFF-DTM C 10
Must Use 0090 RFF Reference M 1
Not Used 0100 DTM Date/Time/Period C 5
Detail Section:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
0930 Segment Group 25: LIN-PIA-IMD-MEA-QTY- C 200000
PCD-ALI-DTM-MOA-GIN-GIR-QVR-DOC-
PAI-FTX-SG26-SG27-SG28-SG29-SG30-
SG33-SG34-SG35-SG39-SG45-SG47-SG48-
SG49-SG51-SG52
Must Use 0940 LIN Line Item M 1
0950 PIA Additional Product Id C 25
0960 IMD Item Description C 99
0960 IMD Item Description C 99
Not Used 0970 MEA Measurements C 5
Section Control:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
Must Use 2090 UNS Section Control M 1
Summary Section:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
2100 MOA Monetary Amount C 12
2110 CNT Control Total C 10
Not Used 2120 Segment Group 54: ALC-ALI-MOA C 10
Not Used 2130 ALC Allowance or Charge M 1
Not Used 2140 ALI Additional Information C 1
Not Used 2150 MOA Monetary Amount M 2
Detail Section:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
0930 Segment Group 25: LIN-PIA-IMD-MEA-QTY- C 200000
PCD-ALI-DTM-MOA-GIN-GIR-QVR-DOC-
PAI-FTX-SG26-SG27-SG28-SG29-SG30-
SG33-SG34-SG35-SG39-SG45-SG47-SG48-
97ORDERS (D.96A.EANCOM) 23 February 2, 1999
SG49-SG51-SG52
Must Use 0940 LIN Line Item M 1
0950 PIA Additional Product Id C 25
0960 IMD Item Description C 99
0960 IMD Item Description C 99
0980 QTY Quantity C 10
1080 FTX Free Text C 99
Section Control:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
Must Use 2090 UNS Section Control M 1
Summary Section:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
2100 MOA Monetary Amount C 12
2110 CNT Control Total C 10
DE’s 0065, 0052, 0054, and 0051: Indicate that the message is an UNSM Purchase
Order based on the D.96Adirectory under the control of the United Nations.
DE 0057: Indicates that the message is the EANCOM version 008 of the UNSM
Purchase Order.
Example :
UNH+ME000001+ORDERS:D:96A:UN:EAN008’
All references other than the document number DE 1004 are in the RFF segment.
DE 1225: The message function, coded is a critical data element in this segment. It
applies to all data indicated inthe message. The following definitions apply for the
restricted codes:
Example :
BGM+220+128576+9’
Dependency Notes :
DE 3055: Code for EAN ’9’ should be used when DE 1001 contains the values 22E,
50E and 23B. These are EANspecific codes and must be qualified as such by using
DE 3055.
DE 4343: This DE is used if the order issuer wishes to explicitly indicate whether an
acknowledgement is requiredor not.
Example :
DTM+137:19930830:102’
DTM+2:19931001:102’
DTM+63:199310181430:203’
This example requests that the latest date/time for the delivery is 2:30pm on the
18th of October 1993.
Example :
DTM+137:19930830:102’
DTM+2:19931001:102’
DTM+63:199310181430:203’
This example requests that the latest date/time for the delivery is 2:30pm on the
18th of October 1993.
Example :
DTM+137:19930830:102’
DTM+2:19931001:102’
DTM+63:199310181430:203’
This example requests that the latest date/time for the delivery is 2:30pm on the
18th of October 1993.
Use of this segment in free form is not recommended since it may inhibit automatic
processing of the Order. Coded references to standard texts is an available
functionality which enables automatic processing and reduces transmission and
processing overheads. Standard texts should be mutually defined among trading
partners and can be used to cover legal and other requirements.
Example :
FTX+ZZZ+1+001::91’
Dependency Notes :
DE C107: This composite is only used when trading partners have agreed to use
mutually defined code values.
DE 3453: The language code is only used to indicate the free text language. It is only
used if composite C108 is used.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0090 RFF Reference M 1
Example :
RFF+CT:652744’
RFF+PL:AUG1993’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0090 RFF Reference M 1
Example :
RFF+CT:652744’
RFF+PL:AUG1993’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0090 RFF Reference M 1
Example :
RFF+CT:652744’
RFF+PL:AUG1993’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0120 NAD Name and Address M 1
The delivery address given in NAD at header level is the main delivery address for
all line items. It can however be overridden at line level by the use of Segment
Group 32 LOC/QTY/DTM to indicate split deliveries.
Example :
NAD+BY+5412345000010::9’
NAD+SU+4012345500000::9’
NAD+DP+5412345000010::9’
Dependency Notes :
The following composites and data elements are only used when a coded name and
address can not be used or there is a requirement to furnish the full name and
address for the trading party. The affected composites and data elements are as
follows:
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0120 NAD Name and Address M 1
The delivery address given in NAD at header level is the main delivery address for
all line items. It can however be overridden at line level by the use of Segment
Group 32 LOC/QTY/DTM to indicate split deliveries.
Example :
NAD+BY+5412345000010::9’
NAD+SU+4012345500000::9’
NAD+DP+5412345000010::9’
Dependency Notes :
The following composites and data elements are only used when a coded name and
address can not be used or there is a requirement to furnish the full name and
address for the trading party. The affected composites and data elements are as
follows:
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0120 NAD Name and Address M 1
0150 Segment Group 3: Reference C 10
The delivery address given in NAD at header level is the main delivery address for
all line items. It can however be overridden at line level by the use of Segment
Group 32 LOC/QTY/DTM to indicate split deliveries.
Example :
NAD+BY+5412345000010::9’
NAD+SU+4012345500000::9’
NAD+DP+5412345000010::9’
Dependency Notes :
The following composites and data elements are only used when a coded name and
address can not be used or there is a requirement to furnish the full name and
address for the trading party. The affected composites and data elements are as
follows:
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0160 RFF Reference M 1
Example :
RFF+VA:87765432’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0120 NAD Name and Address M 1
The delivery address given in NAD at header level is the main delivery address for
all line items. It can however be overridden at line level by the use of Segment
Group 32 LOC/QTY/DTM to indicate split deliveries.
Example :
NAD+BY+5412345000010::9’
NAD+SU+4012345500000::9’
NAD+DP+5412345000010::9’
Dependency Notes :
The following composites and data elements are only used when a coded name and
address can not be used or there is a requirement to furnish the full name and
address for the trading party. The affected composites and data elements are as
follows:
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0120 NAD Name and Address M 1
The delivery address given in NAD at header level is the main delivery address for
all line items. It can however be overridden at line level by the use of Segment
Group 32 LOC/QTY/DTM to indicate split deliveries.
Example :
NAD+BY+5412345000010::9’
NAD+SU+4012345500000::9’
NAD+DP+5412345000010::9’
Dependency Notes :
The following composites and data elements are only used when a coded name and
address can not be used or there is a requirement to furnish the full name and
address for the trading party. The affected composites and data elements are as
follows:
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0120 NAD Name and Address M 1
The delivery address given in NAD at header level is the main delivery address for
all line items. It can however be overridden at line level by the use of Segment
Group 32 LOC/QTY/DTM to indicate split deliveries.
Example :
NAD+BY+5412345000010::9’
NAD+SU+4012345500000::9’
NAD+DP+5412345000010::9’
Dependency Notes :
The following composites and data elements are only used when a coded name and
address can not be used or there is a requirement to furnish the full name and
address for the trading party. The affected composites and data elements are as
follows:
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0290 CUX Currencies M 1
When specifying Reference and Target Currencies for international trade, one
occurrence of CUX is all that is required. The reference currency is identified in the
first occurrence of composite C504, with the target currency specified in the second
occurrence of C504. The rate of exchange between the two is detailed in DE 5402.
Example :
CUX+2:GBP:9’
CUX+2:GBP:9+3:BEF:4+48.50’
Indicates that the order currency is Pounds Sterling and the invoicing currency is
Belgian Francs with a rate of exchange of 48.50 Belgian Francs to 1 Pound Sterling.
Dependency Notes :
DE C504: the second occurrence of this composite is only used if a target currency is
being specified.
DE 5402: The rate of exchange is only used if a target currency has been identified
in the second occurrence of C504.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0330 PAT Payment Terms Basis M 1
0340 DTM Date/Time/Period C 5
Example :
PAT+22++5:3:D:20’
This example indicates discount payment terms with payment due 20 days after the
reference date which in this case is the invoice date.
This occurrence of the PAT-MOA segment group will be used to transmit net
payment terms information. There will be a separate occurrence of the PAT-MOA
segment group if there are any discounted payment terms applicable.
Example :
DTM+13:19940331:102’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0330 PAT Payment Terms Basis M 1
0340 DTM Date/Time/Period C 5
0350 PCD Percentage Details C 1
Example :
PAT+22++5:3:D:20’
This example indicates discount payment terms with payment due 20 days after the
reference date which in this case is the invoice date.
This instance of the PAT-MOA segment group will be used to transmit discount
terms, if any.
Example :
DTM+13:19940331:102’
Example :
PCD+15:2.5:13’
A penalty percentage of 2.5% of the invoice value will be charged if the invoice is
not paid according to terms.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0380 TDT Details of Transport M 1
Example :
TDT+20++30+31’
Dependency Notes :
Data Elements 8179 and 8178 are only used when the type of transport must be
specifically identified, that is, a generic description such as road transport is
unsuitable.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0430 TOD Terms of Delivery or Transport M 1
Example :
TOD+3++CIF’
Dependency Notes :
Data elements 1131 and 3055 are only used if specific terms of delivery codes, which
are outside those recommended by EDIFACT, are being used.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0700 ALC Allowance or Charge M 1
0730 Segment Group 19: Quantity C 1
0760 Segment Group 20: Percentage Details C 1
0790 Segment Group 21: Monetary Amount C 2
0820 Segment Group 22: Rate Details C 1
As the calculation price type (data element 5125 PRI segment) used in the purchase
order is always a net price,allowances and/or charges specified in the ALC segment
are for information purposes only.
If the various allowances and/or charges are applied against a fluctuating price
(constantly because of theapplication of other allowances and/or charges) then the
sequence of calculation is indicated using this data element.
Example :
ALC+A+++1’
Dependency Notes :
DE 1227: If the allowance or charge is not to be applied against a fixed price then
the calculation sequenceindicator must be included.
DE C214: This composite is only used if the buyer knows the type of allowance or
charge.
DE 3055: This data element is only used if an EAN code is used in data element
7161.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0740 QTY Quantity M 1
As an order normally will include many different products it is not expected that
the QTY allowance or chargesegment will be used.
Example :
QTY+1:14’
Dependency Notes :
DE 6411: This data element is only used if the current product is of variable
quantity.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0770 PCD Percentage Details M 1
Example :
PCD+3:1.25’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0800 MOA Monetary Amount M 1
Example :
MOA+23:500’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0830 RTE Rate Details M 1
Example :
RTE+2:5.5’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 0940 LIN Line Item M 1
0950 PIA Additional Product Id C 25
0960 IMD Item Description C 99
0960 IMD Item Description C 99
0980 QTY Quantity C 10
1080 FTX Free Text C 99
1180 Segment Group 28: Price Details C 25
1270 Segment Group 30: Package C 10
1270 Segment Group 30: Package C 10
1400 Segment Group 33: Place/Location Identification C 9999
1600 Segment Group 39: Allowance or Charge C 99
Example :
LIN+1++5412345111115:EN’
Dependency Notes :
DE C212: This composite will only be used for the identification of EAN/UPC codes.
If another coding structure is required, e.g. HIBC, then this composite will not be
used and the code will be detailed in the PIA segment.
Data elements 5495 and 7083 are only used when sub-lines are required.
DE 4347: Product Id function coded has the following restricted coded functions:
An alternative identification which may be used instead of the main article number
provided in the LIN segment, e.g., a buyers article number, an HIBC code, etc.
9 - No substitution accepted - The buyer will not accept any other product code than
the one specified in the LIN segment. The code specified in the LIN segment is
repeated in the PIA segment to confirm the only code acceptable.
Examples :
PIA+1+ABC1234:BP’
PIA+2+4000862141664:EN’
In this example the PIA segment is used to provide an article number identification
for substitution. The product identified in the LIN segment by the EAN article
number 5412345111115 can be substituted by the product identified in the PIA
segment by the EAN article number 4000862141664 in case the former is not
available.
PIA+5+5410738251028:EN’
This example details the EAN article number 5410738251028 which is of equal
importance or significance to the EAN article number 5412345111115 identified in
97ORDERS (D.96A.EANCOM) 97 February 2, 1999
the LIN segment.
PIA+9+5412345111115:EN’
This example details the situation where the buyer explicitly specifies that no other
product is acceptable but the one specified in the LIN segment. The PIA re-specifies
the product code from the LIN segment.
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.
If both free-form and coded descriptions are required then the IMD segment must
be repeated.
Example :
IMD+C++TU’
IMD+F++:::CORN CRISPIES:CASE’
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.
If both free-form and coded descriptions are required then the IMD segment must
be repeated.
Example :
IMD+C++TU’
IMD+F++:::CORN CRISPIES:CASE’
If split deliveries are being used, the quantities for the split delivery are specified in
segment group 32. The totals for all quantities expressed in the QTY’s at segment
group level must equal the value in this QTY segment.
Example :
QTY+21:48:KGM’
Dependency Notes :
DE 6411: This DE is only used if the product ordered is a variable quantity product.
Use of this segment in free form is not recommended since it may inhibit automatic
processing of the Order. Coded references to standard texts is an available
functionality which enables automatic processing and reduces transmission and
processing overheads. Standard texts should be mutually defined among trading
partners and can be used to cover legal and other requirements.
Example :
FTX+ZZZ+1+001::92’
Dependency Notes :
DE C107: This composite is only used when trading partners have agreed to use
mutually defined code values.
DE 3453: The language code is only used to indicate the free text language. It is only
used if composite C108 is used.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1190 PRI Price Details M 1
Example :
PRI+AAA:14.58:CT:AAE’
Dependency Notes :
Data elements 5284 and 6411 are only used to indicate that the price is for a
variable quantity product.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1280 PAC Package M 1
Example :
PAC+4++CS’
Applying this example to the first line item, the instruction is to pack the 48 units
ordered in the QTY at LIN level into 4 cases, i.e. into despatch units containing 12
ordered units each.
Dependency Notes :
Composite C532 is only used where the packaging being described is returnable.
This composite identifies who is responsible for the payment of its return.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1280 PAC Package M 1
Example :
PAC+4++CS’
Applying this example to the first line item, the instruction is to pack the 48 units
ordered in the QTY at LIN level into 4 cases, i.e. into despatch units containing 12
ordered units each.
Dependency Notes :
Composite C532 is only used where the packaging being described is returnable.
This composite identifies who is responsible for the payment of its return.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1410 LOC Place/Location Identification M 1
1420 QTY Quantity C 1
Example :
LOC+7+4012345500000::9’
Example :
QTY+11:14’
Dependency Notes :
DE 6411: This DE is only used if the product being ordered is a variable quantity
product.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1610 ALC Allowance or Charge M 1
1640 Segment Group 40: Quantity C 1
1670 Segment Group 41: Percentage Details C 1
1700 Segment Group 42: Monetary Amount C 2
1730 Segment Group 43: Rate Details C 1
As the calculation price type (data element 5125 PRI segment) used in the purchase
order is always a net price, allowances and/or charges specified in the ALC segment
are for information purposes only.
If the various allowances and/or charges are applied against a fluctuating price
(constantly because of the application of other allowances and/or charges) then the
sequence of calculation is indicated using this data element.
Example :
ALC+A+++1’
Dependency Notes :
DE 4471: This data element is only used is the value in data element is ’C’, charge.
DE 1227: If the allowance or charge is not to be applied against a fixed price then
the calculation sequence indicator must be included.
DE C214: This composite is only used if the buyer knows the type of allowance or
charge.
DE 3055: This data element is only used if the code value ’DAE’ is used in data
element 7161.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1650 QTY Quantity M 1
Example :
QTY+1:14’
Dependency Notes :
DE 6411: This data element is only used if the current product is of variable
quantity.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1680 PCD Percentage Details M 1
Example :
PCD+1:1.25’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1710 MOA Monetary Amount M 1
Example :
MOA+23:500’
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
Must Use 1740 RTE Rate Details M 1
Example :
RTE+2:5.5’
Example :
UNS+S’
Example :
MOA+79:15000’
MOA+259:400’
MOA+260:1800’
Assuming that the currency of the order is pounds sterling, the total value of the
line items identified in the message is 15000 pounds, with the total value of charges
and allowances equalling 400 and 1800 pounds respectively.
Example :
CNT+2:4’
Example :
UNT+48+ME000001’