850 Purchase Order

Functional Group ID=

PO

Introduction:
This standard provides the format and establishes the data contents of a purchase order transaction set. The purchase
order transaction set provides for customary and established business and industry practice relative to the placement
of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes
or purchase order acknowledgment information.
Pos.
No.
005

Seg.
ID
ISA

Name
Interchange Control Header

Req.
Des.
O

008

GS

Functional Group Header

010

ST

Transaction Set Header

020

BEG

Beginning Segment for Purchase Order

030

NTE

Note/Special Instruction

100

080

FOB

F.O.B. Related Instructions

120

ITA

Allowance, Charge or Service

10

130

ITD

Terms of Sale/Deferred Terms of Sale

230

TD5

Carrier Details (Routing Sequence/Transit

Time)
LOOP ID - N1

12

Max.Use
1

200

290

N1

Name

300

N2

Additional Name Information

310

N3

Address Information

320

N4

Geographic Location

340

PER

Administrative Communications Contact

410

PO1

Purchase Order Baseline Item Data

420

CUR

Currency

440

CTP

Pricing Information

25

450

PID

Product/Item Description

1000

460

MEA

Measurements

40

480

PKG

Marking, Packaging, Loading

25

500

REF

Reference Numbers

12

530

ITA

Allowance, Charge or Service

10

620

SCH

Line Item Schedule

104

860

CTT

Transaction Totals

880

SE

Transaction Set Trailer

890

GE

Functional Group Trailer

900

IEA

Interchange Control Trailer

LOOP ID - PO1
M

Loop
Repeat

100000

Notes and
Comments

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
ISA01

ISA02

ISA03

ISA04

ISA05

ISA06

ISA07

ISA08

ISA09
ISA10

ISA Interchange Control Header

005

Optional
1
To start and identify an interchange of one or more functional groups and
interchange-related control segments

ISA*00*
*00*
*09*00507047988
961212*1204*U*00200*963471204*0*P*\@

*ZZ*X0000X0

Data Element Summary

Data
Element Name
Attributes
I01
Authorization Information Qualifier
M ID 2/2
Code to identify the type of information in the Authorization Information.
00
No Authorization Information Present (No Meaningful
Information in I02)
I02
Authorization Information
M AN 10/10
Information used for additional identification or authorization of the sender or
the data in the interchange. The type of information is set by the Authorization
Information Qualifier.
I03
Security Information Qualifier
M ID 2/2
Code to identify the type of information in the Security Information.
00
No Security Information Present (No Meaningful
Information in I04)
I04
Security Information
M AN 10/10
This is used for identifying the security information about the sender or the
data in the interchange. The type of information is set by the Security
Information Qualifier.
I05
Interchange ID Qualifier
M ID 2/2
Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified.
09
X.121 (CCITT)
I06
Interchange Sender ID
M AN 15/15
Identification code published by the sender for other parties to use as the
receiver ID to route data to them. The sender always codes this value in the
sender ID element
005070479 = HONDA DUNS CODE +. ff = HONDA FACILITY CODE.
(see APPENDICES)
I05
Interchange ID Qualifier
M ID 2/2
Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified.
ZZ
Mutually Defined
I07
Interchange Receiver ID
M AN 15/15
Identification code published by the receiver of the data. When sending, it is
used by the sender as their sending ID, thus other parties sending to them will
use this as a receiving ID to route data to them.
HONDA ASSIGNED SUPPLIER CODE.
I08
Interchange Date
M DT 6/6
Date of the interchange.
I09
Interchange Time
M TM 4/4
Time of the interchange.

ISA11

I10

ISA12

I11

ISA13

I12

ISA14

I13

ISA15

I14

ISA16

I15

Interchange Control Standards Identifier

M ID 1/1
Code to identify the agency responsible for the control standard used by the
message that is enclosed by the interchange header and trailer.
U
U.S. EDI Community of ASC X12, TDCC, and UCS
Interchange Control Version Number
M ID 5/5
This version number covers the interchange control segments and the
functional group control segments.
00200
Standard Issued as ANSI X12.5-1987
Interchange Control Number
M N0 9/9
This number uniquely identifies the interchange data to the sender. It is
assigned by the sender. Together with the sender ID it uniquely identifies the
interchange data to the receiver. It is suggested that the sender, receiver, and
all third parties be able to maintain an audit trail of interchanges using this
number.
Acknowledgment Requested
M ID 1/1
Code sent by the sender to request an interchange acknowledgment.
0
No Acknowledgment Requested
Test Indicator
M ID 1/1
Code to indicate whether data enclosed by this interchange envelope is test or
production.
P
Production Data
Subelement Separator
M AN 1/1
This is a field reserved for future expansion in separating data element
subgroups. (In the interest of a migration to international standards, this should
be different from the data element separator).

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
GS01

GS02

GS03

GS04
GS05

GS06
GS07

GS08

GS Functional Group Header

008

Optional
1
To indicate the beginning of a functional group and to provide control information

A functional group of related transaction sets, within the scope of X12 standards,
consists of a collection of similar transaction sets enclosed by a functional group
header and a functional group trailer.
GS*PO*88*X0000X0*961212*1418*963470001*X*002003@
Data Element Summary
Data
Element Name
Attributes
479
Functional Identifier Code
M ID 2/2
Code identifying a group of application related transaction sets
PO
Purchase Order
142
Application Sender's Code
M ID 2/12
Code identifying party sending transmission.
ff = HONDA SENDING FACILITY CODE.
(SEE APPENDIX).
124
Application Receiver's Code
M ID 2/12
Code identifying party receiving transmission.
HONDA ASSIGNED SUPPLIER CODE.
29
Data Interchange Date
M DT 6/6
Date sender generated a functional group of transaction sets.
30
Data Interchange Time
M TM 4/4
Time (HHMM) when the sender generated a functional group of transaction
sets (local time at sender's location).
28
Data Interchange Control Number
M N0 1/9
Assigned number originated and maintained by the sender
455
Responsible Agency Code
M ID 1/2
Code used in conjunction with the version data element to identify the issuer of
the standard.
X
Accredited Standards Committee X12
480
Version / Release / Industry Identifier Code
M ID 1/12
Code indicating the version, release, and industry ID of the EDI standard being
used. Positions 1 - 3, Major Version Number; Positions 4 - 6, Release Level of
Version; Positions 7 - 12, Industry or Trade Association ID (optionally
assigned by user)
002003

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
ST01

ST02

ST Transaction Set Header

010

Mandatory
1
To indicate the start of a transaction set and to assign a control number

The transaction set identifier (ST01) is intended for use by the translation routines of
the interchange partners to select the appropriate transaction set definition (e.g., 810
selects the invoice transaction set).
ST*850*0001@
Data Element Summary
Data
Element Name
Attributes
143
Transaction Set Identifier Code
M ID 3/3
Code uniquely identifying a Transaction Set
850
X12.1 Purchase Order
329
Transaction Set Control Number
M AN 4/9
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
BEG01

BEG02

BEG03
BEG05
BEG06

BEG Beginning Segment for Purchase Order

020

Mandatory
1
To indicate the beginning of the Purchase Order Transaction Set and transmit identifying
numbers and dates

BEG*00*RL*GAHB59011**961205*IEL@
Data Element Summary
Data
Element Name
Attributes
353
Transaction Set Purpose Code
M ID 2/2
Code identifying purpose of transaction set
00
Original
05
Replace
18
Reissue
92
Purchase Order Type Code
M ID 2/2
Code specifying the type of Purchase Order
BK
Blanket Order (Quantity Firm)
RL
Release (Blanket Order)
An order for goods and services placed against a
pre-existing contract or blanket order
SA
Stand-alone Order
324
Purchase Order Number
M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
323
Purchase Order Date
M DT 6/6
Date assigned by the purchaser to Purchase Order
326
Request Reference Number
O AN 1/45
Reference number or RFQ number to use to identify a particular transaction set
and query (additional reference number or description which can be used with
contract number)
IEL = INVOICE ELECTRONICALLY
(SEND AN 810).
INR = INVOICE NOT REQUIRED.
IBM = INVOICE BY MAIL

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
NTE01

NTE02

NTE Note/Special Instruction

030

Floating
100
To transmit information in a free-form format, if necessary, for comment or special
instruction

The NTE segment permits free-form information/data which, under ANSI X12
standard implementations, is not machine processable. The use of the NTE segment
should therefore be avoided, if at all possible, in an automated environment.
NTE*DEL*DELIVERY TO ARRIVE WITHIN 04 WORK DAYS PRIOR TO DUE
DATE@
Data Element Summary
Data
Element Name
Attributes
363
Note Reference Code
O ID 3/3
Code identifying the functional area or purpose for which the note applies.
Also see: Free Form Message (3).
DEL
Delivery
GEN
Entire Transaction Set
ORI
Order Instructions
PAY
Payables
PUR
Purchasing
TRA
Transportation
3
Free Form Message
M AN 1/60
Free-form text

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:

Notes:

Ref.
Des.
FOB01

FOB04

FOB05

FOB06

FOB07

FOB F.O.B. Related Instructions

080

Optional
1
To specify transportation instructions relating to shipment
1 If FOB03 is present, then FOB02 is required.
2 If FOB04 is present, then FOB05 is required.
3 If FOB07 is present, then FOB06 is required.
1 FOB01 indicates which party will pay the carrier.
2 FOB02 is the code specifying transportation responsibility location.
3 FOB06 is the code specifying title passage location.
FOB*ZZ***01*FOB*AC*AURORA, IL@
Data Element Summary
Data
Element Name
Attributes
146
Shipment Method of Payment
M ID 2/2
Code identifying payment terms for transportation charges
DF
Defined by Buyer and Seller
334
Transportation Terms Qualifier Code
O ID 2/2
Code identifying the source of the transportation terms
01
Incoterms
335
Transportation Terms Code
C ID 3/6
Code identifying the trade terms which apply to the shipment transportation
responsibility. Six digit codes represent INCOTERMS.
309
Location Qualifier
C ID 1/2
Code identifying type of Location Identifier (310) used.
AC
City and State
ZZ
Mutually Defined
352
Description
O AN 1/80
A free-form description to clarify the related data elements and their content

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:
Notes:

Ref.
Des.
ITA01

ITA02

ITA03

ITA04
ITA06

ITA08

ITA09

ITA11

ITA13

ITA Allowance, Charge or Service

120

Optional
10
To specify allowances, charges, or services
1 If ITA02 is present, then at least one of ITA03 or ITA13 is required.
2 Only one of ITA06 ITA07 or ITA08 may be present.
3 If ITA08 is present, then ITA09 is required.
4 If ITA10 is present, then ITA11 is required.
1 ITA12 is the quantity of free goods.
ITA*C*AX*TX*06****Z*5.00****SALES TAX@
Data Element Summary
Data
Element Name
Attributes
248
Allowance or Charge Indicator
M ID 1/1
Code which indicates an allowance or charge for the service specified
A
Allowance
C
Charge
559
Agency Qualifier Code
O ID 2/2
Code identifying the agency assigning the code values
AX
ANSI X12
560
Special Services Code
C ID 2/10
Code identifying the special service
(SEE APPENDIX)
331
Allowance or Charge Method of Handling Code
M ID 2/2
Code indicating method of handling for an allowance or charge
359
Allowance or Charge Rate
C R 1/9
Allowance or Charge Rate per Unit
USED WHEN A PRICE IS SPECIFIED.
378
Allowance/Charge Percent Qualifier
C ID 1/1
Code indicating on what basis allowance or charge percent is calculated
Z
Mutually Defined
332
Allowance or Charge Percent
C R 1/6
Allowance or charge expressed as a percent.
USED WHEN PERCENT IS SPECIFIED IN THE PO.
355
Unit or Basis for Measurement Code
C ID 2/2
Code identifying the basic unit of measurement.
(SEE APPENDIX)
352
Description
C AN 1/80
A free-form description to clarify the related data elements and their content
DESCRIPTION OF THE ALLOWANCE OR CHARGE.

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:

Notes:

Ref.
Des.
ITD01

ITD02

ITD03

ITD04
ITD12

ITD Terms of Sale/Deferred Terms of Sale

130

Optional
5
To specify terms of sale
1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required.
2 If ITD08 is present, then at least one of ITD04 or ITD05 is required.
3 If ITD09 is present, then ITD10 is required.
1

If ITD01 equals 04 - ITD10 is required and either ITD11 or ITD12 is required. If

ITD01 equals 05 - ITD06 or ITD07 is required. If ITD01 does not equal 04 or 05 ITD03 or ITD08 is required.
ITD*08*3*0.00*961229********STANDARD SETTLEMENT SCHEDULE@
Data Element Summary
Data
Element Name
Attributes
336
Terms Type Code
O ID 2/2
Code identifying type of payment terms
08
Basic Discount Offered
333
Terms Basis Date Code
M ID 1/2
Code identifying the beginning of the terms period
3
Invoice Date
338
Terms Discount Percent
C R 1/6
Terms discount percentage, expressed as a percent, available to the purchaser if
an invoice is paid on or before the Terms Discount Due Date
2.50 = NET
370
Terms Discount Due Date
C DT 6/6
Date payment is due if discount is to be earned
352
Description
C AN 1/80
A free-form description to clarify the related data elements and their content

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:

Notes:

Ref.
Des.
TD501

TD505

TD507

TD508

TD5 Carrier Details (Routing Sequence/Transit Time)

230

Optional
12
To specify the carrier and sequence of routing and provide transit time information
1 At least one of TD502 TD504 or TD505 is required.
2 If TD502 is present, then TD503 is required.
3 If TD507 is present, then TD508 is required.
4 If TD510 is present, then TD511 is required.
1

When specifying a routing sequence to be used for the shipment movement in lieu of
specifying each carrier within the movement, use TD502 to identify the party
responsible for defining the routing sequence, and use TD503 to identify the actual
routing sequence, specified by the party identified in TD502.
TD5*O****AURORA FAST FREIGHT, INC.**OR*DETROIT, MI 46975@
Data Element Summary
Data
Element Name
Attributes
133
Routing Sequence Code
O ID 1/2
Code describing the relationship of a carrier to a specific shipment movement
1
1st Carrier after Origin Carrier
2
2nd Carrier after Origin Carrier
3
3rd Carrier after Origin Carrier
O
Origin Carrier (Air, Motor, or Ocean)
387
Routing
C AN 1/35
Free-form description of the routing or requested routing for shipment, or the
originating carrier's identity
CARRIER TO BE USED IN THE SEQUENCE SPECIFIED
309
Location Qualifier
O ID 1/2
Code identifying type of Location Identifier (310) used.
OR
Origin (Shipping Point)
310
Location Identifier
C AN 1/25
Code which identifies a specific location
SHIPPING POINT

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
N101

N102
N103

N104

N1 Name
290
N1

Optional

Optional
1
To identify a party by type of organization, name, and code
1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
1

This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104) must
provide a key to the table maintained by the transaction processing party.
N1*PN*LAFAYETTE*92*88@
Data Element Summary
Data
Element Name
Attributes
98
Entity Identifier Code
M ID 2/2
Code identifying an organizational entity or a physical location.
BT
Party to be Billed For Other Than Freight(Bill To)
BY
Buying Party (Purchaser)
PJ
Party to Receive Correspondence
PN
Party to Receive Shipping Notice
ST
Ship To
SU
Supplier/Manufacturer
93
Name
C AN 1/35
Free-form name
66
Identification Code Qualifier
C ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
92
Assigned by Buyer
67
Identification Code
C ID 2/17
Code identifying a party.
IF N101 = ST THEN ID CODE = HONDA DELIVER TO CODE.
IF N101 = SU THEN ID CODE = HONDA ASSIGNED SUPPLIER
CODE.
IF N101 = BY THEN ID CODE = HONDA FACILITY CODE.
IF N101 = PN THEN ID CODE = HONDA ASN FAC CODE.
IF N101 = PJ THEN ID CODE = ORIGINAL SUPPLIER CODE.
IF N101 = BT THEN ID CODE = BILL TO.

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
N201
N202

N2 Additional Name Information

300
N1

Optional

Optional
2
To specify additional names or those longer than 35 characters in length

N2*LAFAYETTE PLANT@
Data Element Summary
Data
Element Name
93
Name
Free-form name
93
Name
Free-form name

Attributes
M AN 1/35
O

AN 1/35

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
N301
N302

N3 Address Information
310
N1

Optional

Optional
2
To specify the location of the named party

N3*3701 STATE ROAD 26 EAST@

Data Element Summary
Data
Element Name
166
Address Information
Free-form field for address information.
166
Address Information
Free-form field for address information.

Attributes
M AN 1/35
O

AN 1/35

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:

Notes:

Ref.
Des.
N401
N402
N403

N404

N4 Geographic Location
320
N1

Optional

Optional
1
To specify the geographic place of the named party
1 At least one of N401 or N405 is required.
2 If N401 is present, then N402 is required.
3 If either N405 or N406 is present, then the other is required.
1

A combination of either N401 through N404, or N405 and N406 may be adequate to
specify a location.
2 N402 is required only if city name (N401) is in the USA or Canada.
N4*LAFAYETTE*IN*47905@
Data Element Summary
Data
Element Name
Attributes
19
City Name
C AN 2/19
Free-form text for city name
156
State or Province Code
C ID 2/2
Code (Standard State/Province) as defined by appropriate government agency
116
Postal Code
O ID 5/9
Code defining international postal zone code excluding punctuation and blanks
(zip code for United States)
26
Country Code
O ID 2/2
Code identifying the country

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
PER01

PER02

PER03

PER04

PER05

PER Administrative Communications Contact

340
N1

Optional

Optional
3
To identify a person or office to whom administrative communications should be directed
1 If PER03 is present, then PER04 is required.
1

This segment is used to specify who is to be contacted on various conditions related

to the transaction. The term "Communication" in the title and purpose relates to
interpersonal communications, not network or telecommunications contacts.
PER*BD*JOHN SPERRY*TE*3176759175*BE95@
Data Element Summary
Data
Element Name
Attributes
366
Contact Function Code
M ID 2/2
Code identifying the major duty or responsibility of the person or group named
BD
Buyer Name or Department
OC
Order Contact
RD
Receiving Dock
SR
Sales Representative or Department
93
Name
O AN 1/35
Free-form name
NAME OF CONTRACT, OFFICE OR LOCATION.
365
Communication Number Qualifier
O ID 2/2
Code identifying the type of communication number
EM
Electronic Mail
FX
Facsimile
TE
Telephone
364
Communication Number
C AN 7/21
Complete communications number including country or area code when
applicable. Also see: Communications Number Qualifier (365).
326
Request Reference Number
O AN 1/45
Reference number or RFQ number to use to identify a particular transaction set
and query (additional reference number or description which can be used with
contract number)
CONTAINS HONDA BUYER.
CODE WHERE APPLICABLE.

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:

Notes:

Ref.
Des.
PO101
PO102

PO103

PO104

PO105

PO106

PO1 Purchase Order Baseline Item Data

410
PO1

Mandatory

Mandatory
1
To specify basic and most frequently used purchase order line item data
1 If PO105 is present, then PO104 is required.
2 If PO106 is present, then PO107 is required.
3 If PO108 is present, then PO109 is required.
4 If PO110 is present, then PO111 is required.
5 If PO112 is present, then PO113 is required.
6 If PO114 is present, then PO115 is required.
7 If PO116 is present, then PO117 is required.
8 If PO118 is present, then PO119 is required.
9 If PO120 is present, then PO121 is required.
10 If PO122 is present, then PO123 is required.
11 If PO124 is present, then PO125 is required.
1
2
3

See the Data Dictionary for a complete list of ID's.

PO101 is the line item identification.
PO106 through PO125 provide for ten (10) different product/service ID's per each
item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No.,
SKU.
PO1*1*0*PC*0*AP*BP*4W3500*EC*00*CG*F*DR*1A@
Data Element Summary
Data
Element Name
Attributes
350
Assigned Identification
O AN 1/6
Alphanumeric characters assigned for differentiation within a transaction set
330
Quantity Ordered
M R 1/9
Quantity ordered
O = INDEFINITE QUANTITY SPECIFIED.
355
Unit or Basis for Measurement Code
M ID 2/2
Code identifying the basic unit of measurement.
( REF. APPENDIX.)
Refer to 002003 Data Element Dictionary for acceptable code values.
212
Unit Price
C R 1/14
Price per unit of product, service, commodity, etc.
0.0 = IF SPECIFIC PRICE NOT GIVEN IN THIS ELEMENT,
REFRENCE P0105 FOR ADDITIONAL INFORMATION.
( ie. P0105 = 'AP' PRICE WOULD BE 'ADVISE')
639
Basis of Unit Price Code
O ID 2/2
Code identifying the type of unit price for an item
(REF. APPENDIX .)
235
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
P0106 AND P0107 CAN OCCUR A MAXIMUM OF 6 TIMES IN ANY
ONE SEGMENT. THE DATA CAN BE IN ANY OF THE
OCCURRENCES.
BP
Buyer's Part Number
CG
Commodity Grouping
DR
Drawing Revision Number
EC
Engineering Change Level

PO107

234

PO108

235

PO109

234

PO110

235

PO111

234

PO112

235

PO113

234

PO114

235

PO115

234

PO116

235

PO117

234

ON
Customer Order Number
PD
Part Number Description
VP
Vendor's (Seller's) Part Number
Product/Service ID
C AN 1/30
Identifying number for a product or service
VARIES WITH THE PREVIOUS IDENTIFICATION QUALIFIER.
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
Product/Service ID
C AN 1/30
Identifying number for a product or service
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
Product/Service ID
C AN 1/30
Identifying number for a product or service
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
Product/Service ID
C AN 1/30
Identifying number for a product or service
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
Product/Service ID
C AN 1/30
Identifying number for a product or service
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
Product/Service ID
C AN 1/30
Identifying number for a product or service

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:

Notes:

CUR Currency
420
PO1

Mandatory

Optional
1
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
1 If CUR08 is present, then CUR07 is required.
2 If CUR09 is present, then CUR07 is required.
3 If CUR11 is present, then CUR10 is required.
4 If CUR12 is present, then CUR10 is required.
5 If CUR14 is present, then CUR13 is required.
6 If CUR15 is present, then CUR13 is required.
7 If CUR17 is present, then CUR16 is required.
8 If CUR18 is present, then CUR16 is required.
9 If CUR20 is present, then CUR19 is required.
10 If CUR21 is present, then CUR19 is required.
1

Monetary values are assumed to be expressed in the currency of the country of the
transaction originator unless the optional CUR segment is used to specify a different
currency. The CUR segment also permits the transaction originator to indicate a
specific exchange rate, foreign exchange location and date/time as the basis for a
currency conversion. Example 1. Assuming the currency of the transaction
originator is U.S. dollars, the following CUR segment, when used in the heading area
of a transaction, would indicate that all monetary values appearing in the transaction
are expressed in Canadian Dollars (CAD). (In this example the exchange rate is at
the discretion of the receiver). CUR*BY*CAD* N/L Example 2. Assuming the
currency of the transaction originator is U.S. dollars, the following CUR segment,
when used in the detail area of a transaction, describes a currency conversion for that
particular item from U.S. dollars to Canadian dollars. It also indicates that a specific
exchange rate, at a specified foreign exchange location on a given date/time be used
as the basis for the currency conversion. Notes below the diagram describe the
meaning of the element values.
CUR*BY*USD*1.20*SE*CAD*NY*007*840821*1400 N/L
1 2
3
4 1. Identifies the buyer's (BY) currency as U.S. dollars (USD). 2. The multiplier
(1.20) is the exchange rate factor for the conversion. 3. Identifies the seller's (SE)
currency as Canadian dollars (CAD). 4. Indicates the basis for the exchange rate as
the New York Foreign Exchange (NY) and the effective date/time (007) as August
21, 1984 (840821) at 2:00 P.M. (1400). The value for this item is to be converted to
Canadian dollars (CAD) at the exchange rate of 1.20, based on the New York
Foreign Exchange (NY) at 2:00 P.M. (1400) on August 21, 1984. The actual unit
price conversion for the item would be: The unit price value 7.50 (U.S. dollars)
multiplied by the exchange rate (1.20) equals 9.00 Canadian dollars (7.50 X 1.20 =
9.00) CUR07 through CUR21 provide for five (5) dates/times relating to the
currency conversion, i.e., effective date, expiration date, etc.
CUR*BY*USD@
THE CUR SEGMENT IS ALWAYS PRESENT EVEN IF THE PURCHASE
ORDER IS PAID FOR IN U.S. DOLLARS.

Ref.
Des.
CUR01

CUR02

Data Element Summary

Data
Element Name
Attributes
98
Entity Identifier Code
M ID 2/2
Code identifying an organizational entity or a physical location.
BY
Buying Party (Purchaser)
100
Currency Code
M ID 3/3
Code (Standard ISO) for country in whose currency the charges are specified

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:

Notes:

Ref.
Des.
CTP02

CTP03
CTP05

CTP07

CTP Pricing Information

440
PO1

Mandatory

Optional
25
To specify pricing information
1 If CTP02 is present, then CTP03 is required.
2 If CTP04 is present, then CTP05 is required.
3 If CTP06 is present, then CTP07 is required.
1

Example of use of CTP03 and CTP04. PRICE QUANTITY RANGE 1.00

0
to 999 0.75
1000 to 4999 0.50
5000 to 9999 0.25
10000 and above
CTP03 CTP04 1.00
0 0.75
1000 0.50
5000 0.25
10000
2 Example of use of CTP03, CTP04 and CTP07. CTP03 CTP04 CTP07 1.00
0
0.90 0.75
1000
0.90 0.50
5000
0.90 0.25
10000 0.90
3 CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of 90
would be the factor if a 10% discount is given.
CTP**DSC*12.45****.985@
CTP**INV*12.59**PC@

Data Element Summary

Data
Element Name
Attributes
236
Price Qualifier
O ID 3/3
Code identifying pricing specification
DSC
Discount Amount Allowed
INV
Invoice Billing Price
212
Unit Price
C R 1/14
Price per unit of product, service, commodity, etc.
355
Unit or Basis for Measurement Code
C ID 2/2
Code identifying the basic unit of measurement.
( SEE APPENDIX .)
649
Multiplier
C R 1/10
Value, identified by price multiplier qualifier, to be used to multiply price to
obtain a new value.

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
PID01

PID05

PID Product/Item Description

450
PO1

Mandatory

Optional
1000
To describe a product or process in coded or free-form format
1 If PID03 is present, then PID04 is required.
2 At least one of PID04 or PID05 is required.
1
2
3

Use PID03 to indicate the organization that publishes the code list being referred to.
PID04 should be used for industry-specific product description codes.
Use PID06 when necessary to refer to the product surface or layer being described in
the segment.
PID*F****WASHER/BOLT@
Data Element Summary
Data
Element Name
Attributes
349
Item Description Type
M ID 1/1
Code indicating the format of a description
F
Free-form
352
Description
C AN 1/80
A free-form description to clarify the related data elements and their content

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
MEA01

MEA02

MEA03

MEA Measurements
460
PO1

Mandatory

Optional
40
To specify physical measurements, including dimension tolerances, weights and counts.

When citing dimensional tolerances, any measurement requiring a sign (+ or -), or

any measurement where a positive (+) value cannot be assumed, use MEA05 as the
negative (-) value and MEA06 as the positive (+) value.
MEA*WT*U*1250.145*LB@
Data Element Summary
Data
Element Name
Attributes
737
Measurement Reference ID Code
O ID 2/2
Code specifying the application of physical measurement cited.
WT
Weights
738
Measurement Qualifier
O ID 1/3
Code identifying the type of measurement.
U
Weight per Unit
739
Measurement Value
C R 1/10
The value of the measurement
WEIGHT AS PER MEA02.
THE MEA03 IS THE WEIGHT OF EACH ORDER UNIT
AS PER "P0103" SEGMENT.

MEA04

355

Unit or Basis for Measurement Code

Code identifying the basic unit of measurement.
(SEE APPENDIX)

ID 2/2

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
PKG01

PKG05

PKG Marking, Packaging, Loading

480
PO1

Mandatory

Optional
25
To describe marking, packaging, loading, and unloading requirements
1 If PKG03 is present, then PKG04 is required.
2 At least one of PKG04 or PKG05 is required.
1

Use the MEA (Measurements) Segment to define dimensions, tolerances, weights,

counts, physical restrictions, etc.
2 Use PKG03 to indicate the organization that publishes the code list being referred to.
3 PKG04 should be used for industry-specific packaging description codes.
4 Special marking or tagging data can be given in PKG05 (description).
PKG*F****PACKAGING INSTRUCTIONS@
Data Element Summary
Data
Element Name
Attributes
349
Item Description Type
M ID 1/1
Code indicating the format of a description
F
Free-form
352
Description
C AN 1/80
A free-form description to clarify the related data elements and their content

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
REF01

REF02

REF Reference Numbers

500
PO1

Mandatory

Optional
12
To specify identifying numbers.
1 At least one of REF02 or REF03 is required.

REF*PG*1E2345@
Data Element Summary
Data
Element Name
Attributes
128
Reference Number Qualifier
M ID 2/2
Code qualifying the Reference Number.
GC
Government Contract Number
GP
Government Priority Number
PC
Production Code
PG
Product Group
127
Reference Number
C AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier. Also see
Reference Number Qualifier, (128).

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

Semantic Notes:
Comments:
Notes:

Ref.
Des.
ITA01

ITA02

ITA03

ITA04

ITA06

ITA08

ITA09

ITA11

ITA13

ITA Allowance, Charge or Service

530
PO1

Mandatory

Optional
10
To specify allowances, charges, or services
1 If ITA02 is present, then at least one of ITA03 or ITA13 is required.
2 Only one of ITA06 ITA07 or ITA08 may be present.
3 If ITA08 is present, then ITA09 is required.
4 If ITA10 is present, then ITA11 is required.
1 ITA12 is the quantity of free goods.
ITA*A*AX*FA*ZZ**0.00*******FULL FREIGHT ALLOWED@
ITA*C*AX*S0030*06**500.00000*****LO**OTO CHARGE@
ITA*C*AX*TX*06****Z*5.00****TAX ON MATERIAL@
Data Element Summary
Data
Element Name
Attributes
248
Allowance or Charge Indicator
M ID 1/1
Code which indicates an allowance or charge for the service specified
A
Allowance
C
Charge
559
Agency Qualifier Code
O ID 2/2
Code identifying the agency assigning the code values
AX
ANSI X12
560
Special Services Code
C ID 2/10
Code identifying the special service
(SEE APPENDIX)
331
Allowance or Charge Method of Handling Code
M ID 2/2
Code indicating method of handling for an allowance or charge
04
Credit Customer Account
06
Charge to be Paid by Customer
ZZ
Mutually Defined
359
Allowance or Charge Rate
C R 1/9
Allowance or Charge Rate per Unit
USED WHEN A PRICE IS SPECIFIED.
378
Allowance/Charge Percent Qualifier
C ID 1/1
Code indicating on what basis allowance or charge percent is calculated
Z
Mutually Defined
332
Allowance or Charge Percent
C R 1/6
Allowance or charge expressed as a percent.
USED WHEN A PERCENT IS SPECIFIED IN THE PO.
355
Unit or Basis for Measurement Code
C ID 2/2
Code identifying the basic unit of measurement.
(SEE APPENDIX)
352
Description
C AN 1/80
A free-form description to clarify the related data elements and their content
DESCRIPTION OF THE ALLOWANCE OR CHARGE.

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
SCH01
SCH02

SCH06

SCH07

SCH Line Item Schedule

620
PO1

Mandatory

Optional
104
To specify the data for scheduling a specific line-item
1 If SCH04 is present, then SCH05 is required.
2 If SCH10 is present, then SCH09 is required.
1 SCH06 specifies the interpretation to be used for SCH07 and SCH08.
SCH*100*PC****002*961224@
Data Element Summary
Data
Element Name
Attributes
380
Quantity
M R 1/10
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
355
Unit or Basis for Measurement Code
M ID 2/2
Code identifying the basic unit of measurement.
( REF. APPENDIX.)
374
Date/Time Qualifier
M ID 3/3
Code specifying type of date or time, or both date and time
002
Delivery Requested
010
Requested Ship
373
Date
M DT 6/6
Date (YYMMDD)
VARIES WITH PREVIOUS QUALIFIER.

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
CTT01

CTT02

CTT Transaction Totals

860

Mandatory
1
To transmit a hash total for a specific element in the transaction set
1 If CTT03 is present, then CTT04 is required.
2 If CTT05 is present, then CTT06 is required.
1

This segment is intended to provide hash totals to validate transaction completeness

and correctness.
CTT*1*100@
Data Element Summary
Data
Element Name
Attributes
354
Number of Line Items
M N0 1/6
Total number of line items in the transaction set
NUMBER OF P01 SEGMENTS.
347
Hash Total
O R 1/10
Sum of values of the specific data element. All values in the data element will
be summed without regard to decimal points (explicit or implicit) or signs.
Truncation will occur on the leftmost digits if the sum is greater than the
maximum size of the hash total of the data element. Example: -.0018 First
occurrence of value being hashed. .18 Second occurrence of value being
hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth occurrence
of value being hashed. ------- 1855 Hash total prior to truncation. 855 Hash
total after truncation to three digit field.
SUM OF THE QUANTITY FIELDS IN THE ' P01 ' RECORD FIELD P0102.

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
SE01

SE02

SE Transaction Set Trailer

880

Mandatory
1
To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments).

1 SE is the last segment of each transaction set.

SE*78*0001@
Data Element Summary
Data
Element Name
Attributes
96
Number of Included Segments
M N0 1/6
Total number of segments included in a transaction set including ST and SE
segments
ACCUMULATED TOTAL NUMBER OF SEGMENTS FROM PREVIOUS
"ST" SEGMENT,
INCLUDING THE "ST" AND "SE" SEGMENTS.
329
Transaction Set Control Number
M AN 4/9
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
SAME CONTROL NUMBER AS THE ONE USED IN THE PREVIOUS
"ST" SEGMENT (ST02) .

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Notes:

Ref.
Des.
GE01

GE02

GE Functional Group Trailer

890

Optional
1
To indicate the end of a functional group and to provide control information

The use of identical data interchange control numbers in the associated functional
group header and trailer is designed to maximize functional group integrity. The
control number is the same as that used in the corresponding header.
GE*2*963470001@
Data Element Summary
Data
Element Name
Attributes
97
Number of Transaction Sets Included
M N0 1/6
Total number of transaction sets included in the functional group or
interchange (transmission) group terminated by the trailer containing this data
element
ACCUMULATED TOTAL NUMBER OF "ST" SEGMENTS INCLUDED IN
THIS FUNCTIONAL GROUP.
28
Data Interchange Control Number
M N0 1/9
Assigned number originated and maintained by the sender
SAME CONTROL NUMBER USED IN THE PREVIOUS "GS" SEGMENT
(GS06) .

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
IEA01

IEA02

IEA Interchange Control Trailer

900

Optional
1
To define the end of an interchange of zero or more functional groups and
interchange-related control segments

IEA*1*963471204@
Data Element Summary
Data
Element Name
Attributes
405
Number of Included Functional Groups
M N0 1/5
A count of the number of functional groups included in a single
transmission/interchange group
709
Communications Environment Code
M N0 9/9
To indicate EDI systems media capability