X12 855 Purchase Order Acknowledgment
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- PR
- Purchase Order Acknowledgement (855)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 855
- Purchase Order Acknowledgment
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
If an order is accepted in its entirety, the BAK segment is the only required segment.
Code identifying purpose of transaction set
- 01
- Cancellation
- 04
- Change
- 06
- Confirmation
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
Detail is required if there are changes to the order.
- AT
- Accepted
- RD
- Reject with Detail
Detail is required if there are changes to the order.
Identifying number for Purchase Order assigned by the orderer/purchaser
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
Code identifying a party or other code
- 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.
O’Reilly Store Number
Name
To identify a party by type of organization, name, and code
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Quantity ordered
Quantity Originally Ordered
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Unit of measure provided on original PO.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
BP as provided on original PO.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
VP as provided on original PO (if provided).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO
- Purchase Order Number
Item Identification
To specify basic item identification data
If an item is replaced or substituted with a different item, an LIN segment is required showing the new item number and a CTP segment is required showing the price of the new item.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- RR
- Replacement Product Number
Pricing Information
To specify pricing information
If an item is replaced or substituted with a different item, an LIN segment is required showing the new item number and a CTP segment is required showing the price of the new item.
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Price of replacement item.
Date/Time Reference
To specify pertinent dates and times
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Code specifying the action taken by the seller on a line item requested by the buyer
- AR
- Item Accepted and Released for Shipment
- BP
- Item Accepted - Partial Shipment, Balance Backordered
If this code is provided, the following DTM segment is mandatory.
- IA
- Item Accepted
- IB
- Item Backordered
If this code is provided, the following DTM segment is mandatory.
- IR
- Item Rejected
- IS
- Item Accepted - Substitution Made
- R1
- Item Rejected, Not a Contract Item
- R2
- Item Rejected, Invalid Item Product Number
- R3
- Item Rejected, Invalid Unit of Issue
- R4
- Item Rejected, Contract Item not Available
- SP
- Item Accepted - Schedule Date Pending
Numeric value of quantity
Should be the quantity that will be shipped immediately (if the item is on backorder or has been rejected, this quantity should be zero.
Date/Time Reference
To specify pertinent dates and times
If an item is back ordered, you must include a DTM segment showing the expected availability date.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample showing a back ordered item
GS*PR*SENDERGS*RECEIVERGS*20240430*160855*000000001*X*004010~
ST*855*8650001~
BAK*04*AC*992097S02068*20150601~
N1*SU*Supplier Name~
N1*BY* OReilly 2068~
PO1**1*EA***BP*A12345*VP*A-12345*PO*992097S02068~
DTM*004*20150601~
ACK*IB*0*EA~
DTM*169*20150701~
CTT*1~
SE*10*8650001~
GE*1*000000001~
IEA*1*000000001~
Sample showing a cancelled item
GS*PR*SENDERGS*RECEIVERGS*20240430*161022*000000001*X*004010~
ST*855*8650003~
BAK*01*AC*991825S02201*20150601~
N1*SU*Supplier Name~
N1*BY* OReilly 2201~
PO1**1*EA***BP*662593A*VP*662593-A*PO*991825S02201~
DTM*004*20150601~
ACK*IR*0*EA~
CTT*1~
SE*9*8650003~
GE*1*000000001~
IEA*1*000000001~
Sample showing a replacement/substituted item
GS*PR*SENDERGS*RECEIVERGS*20240430*161609*000000001*X*004010~
ST*855*8650002~
BAK*04*AC*991545S00930*20150601~
N1*SU*Supplier Name~
N1*BY* OReilly 930*94*930~
PO1**1*EA***BP*DW551*VP*DW-551*PO*99145S00930~
LIN**RR*DW-551-1~
CTP***99.99~
DTM*004*20150601~
ACK*IS*0*EA~
CTT*1~
SE*11*8650002~
GE*1*000000001~
IEA*1*000000001~
Sample showing an accepted order
GS*PR*SENDERGS*RECEIVERGS*20240430*161014*000000001*X*004010~
ST*855*8650002~
BAK*06*AT*888888S04444*20150601~
SE*3*8650002~
GE*1*000000001~
IEA*1*000000001~
Sample showing multiple items
GS*PR*SENDERGS*RECEIVERGS*20240430*161922*000000001*X*004010~
ST*855*8650003~
BAK*04*AC*777777S03334*20150101~
N1*SU*Supplier·Name~
N1*BY*·OReilly···3334~
PO1**1*EA***BP*123456*VP*12345-6*PO*777777S03334~
LIN**RR*654321~
CTP***999.99~
DTM*004*20150101~
ACK*IS*0*EA~
PO1**1*EA***BP*6565*VP*656-5*PO*777777S03334~
DTM*004*20150101~
ACK*IA*1*EA~
CTT*2~
SE*14*8650003~
GE*1*000000001~
IEA*1*000000001~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.