Segment:			ST Transaction Set Header
	Position:			010
	Loop:
	Level:			Heading
	Usage:			Mandatory
	Max Use:			1
	Purpose:			To indicate the start of a transaction set and to assign a control number
	Syntax Notes:
	Semantic Notes:			1			The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

ST01

143

Transaction Set Identifier Code

M

ID 3/3

Code uniquely identifying a Transaction Set

Refer to 004010 Data Element Dictionary for acceptable code values.

>>

ST02

329

Transaction Set Control Number

M

AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

	Segment:			BEG Beginning Segment for Purchase Order
	Position:			020
	Loop:
	Level:			Heading
	Usage:			Mandatory
	Max Use:			1
	Purpose:			To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
	Syntax Notes:
	Semantic Notes:			1			BEG05 is the date assigned by the purchaser to purchase order.
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

BEG01

353

Transaction Set Purpose Code

M

ID 2/2

Code identifying purpose of transaction set

OO ORIGINAL

Refer to 004010 Data Element Dictionary for acceptable code values.

>>

BEG02

92

Purchase Order Type Code

M

ID 2/2

Code specifying the type of Purchase Order

BK BLANKET ORDER (QUALITY FIRM)  NE NEW ORDER  RL RELEASE OR DELIVERY ORDER  RO RUSH ORDER  SA STAND ALONE ORDER  ZZ MUTUALLY DEFINED

Refer to 004010 Data Element Dictionary for acceptable code values.

>>

BEG03

324

Purchase Order Number

M

AN 1/22

Identifying number for Purchase Order assigned by the orderer/purchaser

>>

BEG05

373

Date

M

DT 8/8

Date expressed as CCYYMMDD

BEG06

367

Contract Number

O

AN 1/30

Contract number

	Segment:			CUR Currency
	Position:			040
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			1
	Purpose:			To specify the currency (dollars, pounds, francs, etc.) used in a transaction
	Syntax Notes:			1			If CUR08 is present, then CUR07 is required.
				2			If CUR09 is present, then CUR07 is required.
				3			If CUR10 is present, then at least one of CUR11 or CUR12 is required.
				4			If CUR11 is present, then CUR10 is required.
				5			If CUR12 is present, then CUR10 is required.
				6			If CUR13 is present, then at least one of CUR14 or CUR15 is required.
				7			If CUR14 is present, then CUR13 is required.
				8			If CUR15 is present, then CUR13 is required.
				9			If CUR16 is present, then at least one of CUR17 or CUR18 is required.
				10			If CUR17 is present, then CUR16 is required.
				11			If CUR18 is present, then CUR16 is required.
				12			If CUR19 is present, then at least one of CUR20 or CUR21 is required.
				13			If CUR20 is present, then CUR19 is required.
				14			If CUR21 is present, then CUR19 is required.
	Semantic Notes:
	Comments:			1			See Figures Appendix for examples detailing the use of the CUR segment.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

CUR01

98

Entity Identifier Code

M

ID 2/3

Code identifying an organizational entity, a physical location, property or an individual

BY BUYING PARTY (PURCHASER)  SE SELLING PARTY

Refer to 004010 Data Element Dictionary for acceptable code values.

>>

CUR02

100

Currency Code

M

ID 3/3

Code (Standard ISO) for country in whose currency the charges are specified

	Segment:			REF Reference Identification
	Position:			050
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			>1
	Purpose:			To specify identifying information
	Syntax Notes:			1			At least one of REF02 or REF03 is required.
				2			If either C04003 or C04004 is present, then the other is required.
				3			If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:			1			REF04 contains data relating to the value cited in REF02.
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

REF01

128

Reference Identification Qualifier

M

ID 2/3

Code qualifying the Reference Identification

CT CONTRACT NUMBER  IA INTERNAL VENDOR NUMBER  PR PRICE QUOTE NUMBER  RE RELEASE NUMBER

Refer to 004010 Data Element Dictionary for acceptable code values.

REF02

127

Reference Identification

X

AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

	Segment:			FOB F.O.B. Related Instructions
	Position:			080
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			>1
	Purpose:			To specify transportation instructions relating to shipment
	Syntax Notes:			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.
				4			If FOB08 is present, then FOB09 is required.
	Semantic Notes:			1			FOB01 indicates which party will pay the carrier.
				2			FOB02 is the code specifying transportation responsibility location.
				3			FOB06 is the code specifying the title passage location.
				4			FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07.
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

FOB01

146

Shipment Method of Payment

M

ID 2/2

Code identifying payment terms for transportation charges

BP PAID BY BUYER - THE BUYER AGREES TO THE TRANSPORTATION PAYMENT TERM REQUIRING THE BUYER TO PAY TRANSPORTATION CHARGES TO A SPECIFIED LOCATION (ORIGIN OR DESTINATION LOCATION).  CC COLLECT  PC PREPAID BUT CHARGED TO CUSTOMER  PP PREPAID (BY SELLER)  PU PICKUP

Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:			CSH Sales Requirements
	Position:			110
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			5
	Purpose:			To specify general conditions or requirements of the sale
	Syntax Notes:			1			If CSH02 is present, then CSH03 is required.
				2			If either CSH06 or CSH07 is present, then the other is required.
				3			If either CSH09 or CSH10 is present, then the other is required.
	Semantic Notes:			1			CSH03 is the maximum monetary amount value which the order must not exceed.
				2			CSH04 is the account number to which the purchase amount is charged.
				3			CSH05 is the date specified by the sender to be shown on the invoice.
				4			CSH06 identifies the source of the code value in CSH07.
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

CSH01

563

Sales Requirement Code

O

ID 1/2

Code to identify a specific requirement or agreement of sale

CODE TO IDENTIFY A SPECIFIC REQUIREMENT OR AGREEMENT OF SALE.  ANY ASC X12 APPROVED CODE MAY BE USED. SUGGESTED CODES FOR THE AFTERMARKET:  BK SHIP PARTIAL - BALANCE BACK ORDER  N NO BACK ORDER  SC SHIP COMPLETE  SP SHIP PARTIAL, BALANCE CANCEL  Y BACK ORDER IF OUT OF STOCK

Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:			SAC Service, Promotion, Allowance, or Charge Information
	Position:			120
	Loop:			SAC Optional
	Level:			Heading
	Usage:			Optional
	Max Use:			1
	Purpose:			To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
	Syntax Notes:			1			At least one of SAC02 or SAC03 is required.
				2			If either SAC03 or SAC04 is present, then the other is required.
				3			If either SAC06 or SAC07 is present, then the other is required.
				4			If either SAC09 or SAC10 is present, then the other is required.
				5			If SAC11 is present, then SAC10 is required.
				6			If SAC13 is present, then at least one of SAC02 or SAC04 is required.
				7			If SAC14 is present, then SAC13 is required.
				8			If SAC16 is present, then SAC15 is required.
	Semantic Notes:			1			If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
				2			SAC05 is the total amount for the service, promotion, allowance, or charge.
							If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
				3			SAC08 is the allowance or charge rate per unit.
				4			SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
							SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
				5			SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
				6			SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.
				7			SAC16 is used to identify the language being used in SAC15.
	Comments:			1			SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02.
				2			In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

SAC01

248

Allowance or Charge Indicator

M

ID 1/1

Code which indicates an allowance or charge for the service specified

A ALLOWANCE  C CHARGE  N NO ALLOWANCE OR CHARGE  R ALLOWANCE REQUEST

Refer to 004010 Data Element Dictionary for acceptable code values.

SAC02

1300

Service, Promotion, Allowance, or Charge Code

X

ID 4/4

Code identifying the service, promotion, allowance, or charge

C580 EMERGENCY SERVICE  D820 INSIDE DELIVERY   F190 PALLETIZING

Refer to 004010 Data Element Dictionary for acceptable code values.

SAC03

559

Agency Qualifier Code

X

ID 2/2

Code identifying the agency assigning the code values

ZZ

Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:			DTM Date/Time Reference
	Position:			150
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			10
	Purpose:			To specify pertinent dates and times
	Syntax Notes:			1			At least one of DTM02 DTM03 or DTM05 is required.
				2			If DTM04 is present, then DTM03 is required.
				3			If either DTM05 or DTM06 is present, then the other is required.
	Semantic Notes:
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

DTM01

374

Date/Time Qualifier

M

ID 3/3

Code specifying type of date or time, or both date and time

001 CANCEL AFTER  010 REQUESTED SHIP  071 REQUESTED FOR DELIVERY (AFTER AND INCLUDING)  074 REQUESTED FOR DELIVERY (PRIOR TO AND INCLUDING)  077 REQUESTED FOR DELIVERY (WEEK OF)  081 REQUESTED FOR SHIPMENT (AFTER AND INCLUDING)  084 REQUESTED FOR SHIPMENT (PRIOR TO AND INCLUDING)  087 REQUESTED FOR SHIPMENT (WEEK OF)  106 REQUIRED BY  112 BUYERS DOCK

Refer to 004010 Data Element Dictionary for acceptable code values.

DTM02

373

Date

X

DT 8/8

Date expressed as CCYYMMDD

	Segment:			TD5 Carrier Details (Routing Sequence/Transit Time)
	Position:			240
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			12
	Purpose:			To specify the carrier and sequence of routing and provide transit time information
	Syntax Notes:			1			At least one of TD502 TD504 TD505 TD506 or TD512 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.
				5			If TD513 is present, then TD512 is required.
				6			If TD514 is present, then TD513 is required.
				7			If TD515 is present, then TD512 is required.
	Semantic Notes:			1			TD515 is the country where the service is to be performed.
	Comments:			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.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

TD502

66

Identification Code Qualifier

X

ID 1/2

Code designating the system/method of code structure used for Identification Code (67)

SUGGESTED CODE FOR THE AFTERMARKET. ANY ASC X12 APPROVED CODE MAY BE USED.    2 STANDARD CARRIER ALPHA CODE (SCAC)

Refer to 004010 Data Element Dictionary for acceptable code values.

TD503

67

Identification Code

X

AN 2/80

Code identifying a party or other code

TD504

91

Transportation Method/Type Code

X

ID 1/2

Code specifying the method or type of transportation for the shipment

A AIR  AE AIR EXPRESS  D PARCEL POST  H CUSTOMER PICKUP  M MOTOR (COMMON CARRIER)  R RAIL  S OCEAN  U PRIVATE PARCEL SERVICE

Refer to 004010 Data Element Dictionary for acceptable code values.

TD505

387

Routing

X

AN 1/35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

TD510

732

Transit Time Direction Qualifier

O

ID 2/2

Code specifying the value of time used to measure the transit time

CODE SPECIFYING THE VALUE OT TIME USED TO MEASURE THE TRANSIT TIME. SUGGESTED CODE FOR THE AFTERMARKET USAGE. ANY ASC X12 APPROVED CODE MAY BE USED:    AA AIR HOURS  AD AIR DAYS  CD CALENDAR DAYS  SD SURFACE DAYS  SH SURFACE HOURS  WD WORKING DAYS (EXCLUDES WEEKENDS AND HOLIDAYS)

Refer to 004010 Data Element Dictionary for acceptable code values.

TD511

733

Transit Time

X

R 1/4

The numeric amount of transit time

	Segment:			N9 Reference Identification
	Position:			250
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			1
	Purpose:			To transmit identifying information as specified by the Reference Identification Qualifier
	Syntax Notes:			1			At least one of N902 or N903 is required.
				2			If N906 is present, then N905 is required.
				3			If either C04003 or C04004 is present, then the other is required.
				4			If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:			1			N906 reflects the time zone which the time reflects.
				2			N907 contains data relating to the value cited in N902.
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

N901

128

Reference Identification Qualifier

M

ID 2/3

Code qualifying the Reference Identification

SUGGESTED CODES FOR THE AFTERMARKET USAGE. ANY ASC X12 APPROVED CODES MAY BE USED.    ZZ MUTUALLY DEFINED

Refer to 004010 Data Element Dictionary for acceptable code values.

N903

369

Free-form Description

X

AN 1/45

Free-form descriptive text

GEN ENTIRE TRANSACTION SET

	Segment:			MSG Message Text
	Position:			270
	Loop:
	Level:			Heading
	Usage:			Optional
	Max Use:			1
	Purpose:			To provide a free-form format that allows the transmission of text information
	Syntax Notes:			1			If MSG03 is present, then MSG02 is required.
	Semantic Notes:			1			MSG03 is the number of lines to advance before printing.
	Comments:			1			MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.
				2			If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

MSG01

933

Free-Form Message Text

M

AN 1/264

Free-form message text

	Segment:			N1 Name
	Position:			310
	Loop:			N1 Optional
	Level:			Heading
	Usage:			Optional
	Max Use:			1
	Purpose:			To identify a party by type of organization, name, and code
	Syntax Notes:			1			At least one of N102 or N103 is required.
				2			If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:			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.
				2			N105 and N106 further define the type of entity in N101.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

N101

98

Entity Identifier Code

M

ID 2/3

Code identifying an organizational entity, a physical location, property or an individual

BT PARTY TO BE BILLED FOR OTHER THAN FREIGHT (BILL TO)  BY BUYING PARTY (PURCHASER)  EN END USER  ST SHIP TO

Refer to 004010 Data Element Dictionary for acceptable code values.

N103

66

Identification Code Qualifier

X

ID 1/2

Code designating the system/method of code structure used for Identification Code (67)

1 D-U-N-S NUMBER, DUN & BRADSTREET  9 D-U-N-S+4, D-U-N-S NUMBER WITH FOUR CHARACTER SUFFIX  91 ASSIGNED BY SELLER OR SELLER'S AGENT  92 ASSIGNED BY BUYER OR BUYER'S AGENT

Refer to 004010 Data Element Dictionary for acceptable code values.

	Segment:			N3 Address Information
	Position:			330
	Loop:			N1 Optional
	Level:			Heading
	Usage:			Optional
	Max Use:			2
	Purpose:			To specify the location of the named party
	Syntax Notes:
	Semantic Notes:
	Comments:

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

N301

166

Address Information

M

AN 1/55

Address information

N302

166

Address Information

O

AN 1/55

Address information

	Segment:			N4 Geographic Location
	Position:			340
	Loop:			N1 Optional
	Level:			Heading
	Usage:			Optional
	Max Use:			>1
	Purpose:			To specify the geographic place of the named party
	Syntax Notes:			1			If N406 is present, then N405 is required.
	Semantic Notes:
	Comments:			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 U.S. or Canada.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

N401

19

City Name

O

AN 2/30

Free-form text for city name

N402

156

State or Province Code

O

ID 2/2

Code (Standard State/Province) as defined by appropriate government agency

N403

116

Postal Code

O

ID 3/15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N404

26

Country Code

O

ID 2/3

Code identifying the country

	Segment:			PO1 Baseline Item Data
	Position:			010
	Loop:			PO1 Mandatory
	Level:			Detail
	Usage:			Mandatory
	Max Use:			1
	Purpose:			To specify basic and most frequently used line item data
	Syntax Notes:			1			If PO103 is present, then PO102 is required.
				2			If PO105 is present, then PO104 is required.
				3			If either PO106 or PO107 is present, then the other is required.
				4			If either PO108 or PO109 is present, then the other is required.
				5			If either PO110 or PO111 is present, then the other is required.
				6			If either PO112 or PO113 is present, then the other is required.
				7			If either PO114 or PO115 is present, then the other is required.
				8			If either PO116 or PO117 is present, then the other is required.
				9			If either PO118 or PO119 is present, then the other is required.
				10			If either PO120 or PO121 is present, then the other is required.
				11			If either PO122 or PO123 is present, then the other is required.
				12			If either PO124 or PO125 is present, then the other is required.
	Semantic Notes:
	Comments:			1			See the Data Element Dictionary for a complete list of IDs.
				2			PO101 is the line item identification.
				3			PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

PO101

350

Assigned Identification

O

AN 1/20

Alphanumeric characters assigned for differentiation within a transaction set

PO102

330

Quantity Ordered

X

R 1/15

Quantity ordered

PO103

355

Unit or Basis for Measurement Code

O

ID 2/2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

SUGGESTED CODES FOR AFTERMARKET USAGE. ANY ASC X12 APPROVED CODE MAY BE USED.  CA CASE  EA EACH  FT FOOT  MR METER  P4 FOUR-PACK  P6 SIX PACK  P8 EIGHT PACK

Refer to 004010 Data Element Dictionary for acceptable code values.

PO104

212

Unit Price

X

R 1/17

Price per unit of product, service, commodity, etc.

PO105

639

Basis of Unit Price Code

O

ID 2/2

Code identifying the type of unit price for an item

CA CATALOG  CT CONTACT  NT NET  PR PROMOTION

Refer to 004010 Data Element Dictionary for acceptable code values.

PO106

235

Product/Service ID Qualifier

X

ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

SUGGESTED CODES FOR THE AFTERMARKET USAGE. ANY ASC X12 APPROVED CODE MAY BE USED.    BL BRAND/LABEL  BP BUYER'S PART NUMBER  MF MANUFACTURER  MG MANUFACTURER'S PART NUMBER  UP U.P.C. COMSUMER PACKAGE CODE (1-5-5-1)  VN VENDOR'S (SELLER'S) ITEM NUMBER  VP VENDOR'S (SELLER'S) PART NUMBER

Refer to 004010 Data Element Dictionary for acceptable code values.

PO107

234

Product/Service ID

X

AN 1/48

Identifying number for a product or service

	Segment:			CTT Transaction Totals
	Position:			010
	Loop:			CTT Optional
	Level:			Summary
	Usage:			Optional
	Max Use:			1
	Purpose:			To transmit a hash total for a specific element in the transaction set
	Syntax Notes:			1			If either CTT03 or CTT04 is present, then the other is required.
				2			If either CTT05 or CTT06 is present, then the other is required.
	Semantic Notes:
	Comments:			1			This segment is intended to provide hash totals to validate transaction completeness and correctness.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

CTT01

354

Number of Line Items

M

N0 1/6

Total number of line items in the transaction set

CTT02

347

Hash Total

O

R 1/10

Sum of values of the specified 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 left most 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.

	Segment:			SE Transaction Set Trailer
	Position:			030
	Loop:
	Level:			Summary
	Usage:			Mandatory
	Max Use:			1
	Purpose:			To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
	Syntax Notes:
	Semantic Notes:
	Comments:			1			SE is the last segment of each transaction set.

 
Data Element Summary 

Ref.

Data

Des.

Element

Name

Attributes

>>

SE01

96

Number of Included Segments

M

N0 1/10

Total number of segments included in a transaction set including ST and SE segments

>>

SE02

329

Transaction Set Control Number

M

AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set