850 - Purchase Order |
Purpose
This document provides the format and establishes the data contents of a purchase order transaction set.
This transaction set should not be used to convey purchase order changes or purchase order acknowledgement information.
Segment Map
Segment | Name | Req | Max Use |
---|---|---|---|
ST | Transaction Set Header | M | |
BEG | Beginning Segment for PO | M | |
DTM | Date/Time Reference | M | |
N9 | Notes/Comments | O | |
N1 | Name | O | 1 |
N3 | Address Information | O | 1 |
N4 | Geographic Location | O | 1 |
PO1 | Purchase Order Baseline Item Data | M | 1 |
REF | Kanban Release ID | M | 1 |
SCH | Delivery Schedule | M | 1 |
CTT | Transaction Totals | M | 1 |
SE | Transaction Set Trailer | M | 1 |
ISA Interchange Control Header
![]() |
---|
Purpose: To start and identify an interchange of one or more functional groups and interchange related control segments. Example: ISA*00**00**01*001413764*ZZ*VEN1234567*990811*1530*U*00401*00000003*0*P*~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
ISA01 | Authorization Information Qualifier | 00 | M | Plan to use 00 (No authorization information present) |
ISA02 | Authorization Information | M | Will contain spaces | |
ISA03 | Security Information Qualifier | 00 | M | Plan to use 00 (No security information present) |
ISA04 | Security Information | M | Will contain spaces | |
ISA05 | Interchange ID Qualifier | 01 | M | Customer supplied qualifier |
ISA06 | Interchange Sender ID | 000000000 | M | Customer’s Sender ID |
ISA07 | Interchange ID Qualifier | 01 | M | Vendor qualifier |
ISA08 | Interchange Receiver ID | 000000000 | M | Vendor receiver ID |
ISA09 | Interchange Date | YYMMDD | M | Will contain the date of the interchange in the YYMMDD format |
ISA10 | Interchange Time | HHMM | M | Will contain the time of the interchange in HHMM format |
ISA11 | Interchange Control Standards ID | U | M | Will contain U (US EDI) |
ISA12 | Interchange Control Version Number | 00401 | M | Y2K compliant version 4010 |
ISA13 | Interchange Control Number | M | Unique sequentially incrementing numbers. | |
ISA14 | Acknowledgement Requested | 0 | M | Plan to use 0 (No TA1 Acknowledgement requested) |
ISA15 | Usage Indicator | T or P | M | Will use T (test) or P (production) to indicate status of data |
ISA16 | Component Element Separator | M | Will contain spaces |
GS Functional Group Header
![]() |
---|
Purpose: To indicate the beginning of a functional group and to provide control information. Example: GS*PO*001413764*VEN1234567*20000315*1530*12*X*00401~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
GS01 | Functional ID Code | PO | M | PO = 850, Purchase Order |
GS02 | Application Sender’s Code | 000000000 | M | Customer’s Sender ID |
GS03 | Application Receiver’s Code | 000000000 | M | Vendor Supplied Code |
GS04 | Date | CCYYMMDD | M | Date that Customer generated the functional group of transaction sets |
GS05 | Time | HHMM | M | Time that Customer generated the functional group of transaction sets |
GS06 | Group Control Number | M | Unique number assigned to the group header by Customer | |
GS07 | Responsible Agency Code | X | M | Will contain X (Accredited Standards Committee X12) |
GS08 | Version /Release ID Code | 004010 | M | Will contain version/release of group being transmitted. |
ST Transaction Set Header
![]() |
---|
Purpose: To indicate the start of a transaction set and to assign a control number. Example: ST*850*00083~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
ST01 | Transaction Set ID Code | 850 | M | 850 = Purchase Order |
ST02 | Transaction Set Control Number | M | Will match the SE02 element |
BEG Beginning Segment for Purchase Order
![]() |
---|
Purpose: To indicate the beginning of the purchase order transaction set and transmit identifying numbers and dates. Example: BEG*00*SA*00047291*20000315~ Standard Order BEG*00*DR*00047291*20000315~ Drop Ship Order |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
BEG01 | Transaction Set Purpose Code | 00 | M | 00 = Original Order |
BEG02 | Purchase Order Type Code | SA DR | M | SA = Stand Alone Order (An N2 and N4 will NOT be included). An SA order is any order that will be shipped directly to a Customer branch. DR = Drop Ship (N3 and N4 are Required for Drop Ship Orders). A drop ship order is any order that will be shipped directly to a job site. |
BEG03 | Purchase Order Number | M | Customer’s Purchase Order Number | |
BEG05 | Date | CCYYMMDD | M | Purchase Order Date in CCYYMMDD format |
DTM Date/Time Reference
![]() |
---|
Purpose: To indicate what date the purchase order is expected to arrive at Customer. Example: DTM*002*20000321~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
DTM01 | Date/Time Qualifier | 002 | M | 002 = Delivery Requested (date the order is expected at Customer) |
DTM02 | Date | CCYYMMDD | M | Delivery Requested Date in CCYYMMDD format |
N9 Reference Identification
![]() |
---|
Purpose: Order notes in a free-form format. The buyer for Customer provides this information. Example: N9*ZZ**1ST STOP – DELIVER ON 3/20/00~ N9*ZZ**WINTER DATING ORDER~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
N901 | Ref ID Qualifier | ZZ | ZZ | |
N903 | Free Form Message | O | Free Form Text |
N1 Name
![]() |
---|
Purpose: To identify a party by type of organization, name and code. Used by Customer to indicate the name of the organization that the order will directly ship to. The N1 segment will only appear for DS (Drop Ship) purchase orders. Example: N1*ST*CLIFTON ASSISTED LIVING*92*0004~ (Drop Ship Order) N1*ST*DARTMOUTH WAREHOUSE*92*0004~ (Regular Order) |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
N101 | Entity ID Code | ST | M | ST = Ship to |
N102 | Name | M | Ship to Store Name OR Drop Ship Location Name | |
N103 | Identification Code Qualifier | 92 | M | 92 = Assigned by Buyer (Customer) |
N104 | Identification Code | 9999 | M | Customer’s Branch Number |
N3 Address Information
![]() |
---|
Purpose: Provides the shipping address of the organization that will be receiving the purchase order. The N2 segment will only appear for DS (Drop Ship) purchase orders. Example: N3*365 WILBUR AVENUE~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
N301 | Address Information | O | Address of Drop Ship location (An N3 segment will only appear for Drop Ship Orders) Min=1 Max=55 | |
N302 | Additional Address Information | O | Second line of address of Drop Ship location (An N3 segment will only appear for Drop Ship Orders) Min=1 Max=55 |
N4 Address Information
![]() |
---|
Purpose: To specify the geographic place of the named organization. The N4 segment will only appear for DS (Drop Ship) purchase orders. Example: N4*SOMERSET*MA*02724~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
N401 | City Name | O | Drop Ship City | |
N402 | State Code | O | Drop Ship State | |
N403 | Postal Code | O | Drop Ship Zip Code |
PO1 Purchase Order Baseline Item Data
![]() |
---|
Purpose: To specify the basic and most frequently used purchase order line item data. Example: P01**460*CN*84000**IN*161310013~ P01**72*PC*2750**IN*161147013S~ P01**5*CN*4580**IN*161456013~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
PO101 | Line Item No | Running Number | ||
PO102 | Quantity Ordered | M | Quantity Ordered | |
PO103 | Unit of Measure Code | EA, CN, PC, RL | M | Will be 2 characters |
PO104 | Unit Price | 0 | Will contain no more than 3 decimal places. | |
PO105 | Current Price | CT | Current Price (Subject to Change) | |
PO106 | Product/Service ID Qualifier | BP | M | BP – means net is customer item number |
PO107 | Product/Service ID | M | Customer’s Item Number | |
PO108 | Product/Service ID Qualifier | VP | M | VP – means next is Vendor's part number |
PO109 | Product/Service ID | M | Vendor's part number |
REF Kanban Release ID
![]() |
---|
Purpose: To specify the Kanban Release ID for the purchase order line item data. Example: REF*LF*JID00018*JOB ID~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
REF01 | Service ID | LF | M | Means Next field is Kanban Release ID |
REF02 | Service ID Qualifier | KCD00000-0001 | M | Kanban Release ID |
REF03 | Service ID Description | RELEASE ID | M | Description of REF02 field |
SCH Line Item Schedule
![]() |
---|
Purpose: To specify the data for scheduling a specific line-item. Example: SCH*6000*EA***002*000930~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
SCH01 | Quantity | Numeric value of quantity | ||
SCH02 | Unit Measurement Code | EA, CN, PC, RL | M | Code identifying the basic unit of measurement |
SCH03 | ||||
SCH04 | ||||
SCH05 | Date/Time Qualifier | 002 | M | Delivery Requested |
SCH06 | Date | CCYYMMDD | M | Requested Ship Date in CCYYMMDD format |
CTT Transaction Totals
![]() |
---|
Purpose: To transmit a hash total for a specific element in the transaction set. Customer will transmit the total number of line items included in the purchase order. Example: CTT*3~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
CTT01 | Number of Line Items | M | Total number of Line Items on Purchase Order |
SE Transaction Set Trailer
![]() |
---|
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments. Example: SE*00083~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
SE01 | Number of Included Segments | M | A count of the number of segments in the transaction | |
SE02 | Transaction Set Control Number | M | Will match the transaction set control number in the ST02 element |
GE Functional Group Trailer
![]() |
---|
Purpose: To indicate the end of a functional group and to provide control information. Example: GE*3*0003~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
GE01 | Number of Transaction Sets Included | M | Number of transactions in functional group | |
GE02 | Group Control Number | M | Control Number |
IEA Interchange Control Trailer
![]() |
---|
Purpose: To define the end of an interchange of one or more functional groups and interchange-related control segments. Example: IEA*4*0003~ |
Element | Description | Values | Req | Comments |
---|---|---|---|---|
IEA01 | Number of Included Functional Groups | M | Number of functional groups in interchange | |
IEA02 | Interchange Control Number | M | Control Number (must match ISA control number) |
ISA*00**00**01*001413764*ZZ*VEN1234567*000304*1530*U*00401*00000000003*0*P*~
GS*PO*001413764*VEN1234567*20000304*2012*12*X*004010~
ST*850*00083~
BEG*00*SA*00051683**20000304~
DTM*002*20000316~
N9*ZZ**--- COMBINE WITH BROCKTON ---~
N9*ZZ**--- FIRST STOP ---~
N1*ST*DARTMOUTH WAREHOUSE*92*0004~
PO1*01*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00018*RELEASE ID~
SCH*6000*EA***002*000930~
PO1*02*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00019*RELEASE ID~
SCH*6000*EA***002*000930~
PO1*03*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00020*RELEASE ID~
SCH*6000*EA***002*000930~
PO1*04*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00021*RELEASE ID~
SCH*6000*EA***002*000930~
CTT*4~
SE*10*00083~
GE*4*0003~
IEA*3*0012~
ISA*00**00**01*001413764*ZZ*VEN1234567*000304*1530*U*00401*00000000003*0*P*~
GS*PO*001413764*VEN1234567*20000304*2012*12*X*004010~
ST*850*00083~
BEG*00*DR*00051683**20000304~
DTM*002*20000316~
N9*ZZ**--- JOBSITE DELIVERY ---~
N9*ZZ**--- 1ST STOP DELIVER ON 3/28/00 ---~
N9*ZZ**--- COMBINE WITH DARTMOUTH ---~
N1*ST*CLIFTON ASSISTED LIVING*92*0004~
N3*500 WILBUR AVENUE~
N4*SOMERSET*MA*02747~
PO1*01*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00018*RELEASE ID~
SCH*6000*EA***002*000930~
PO1*02*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00019*RELEASE ID~
SCH*6000*EA***002*000930~
PO1*03*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00020*RELEASE ID~
SCH*6000*EA***002*000930~
PO1*04*3000*EA*0*CT*BP*456-789*VP*MMBD4XXX~
REF*LF*KCD00021*RELEASE ID~
SCH*6000*EA***002*000930~
SCH*6000*EA***002*000930~
CTT*4~
SE*10*00083~
GE*4*0003~
IEA*3*0012~