![Balkamp logo](https://public-assets.guides.us.stedi.com/982aeb0c-825c-40e4-af54-a7c4f9b2d5e8/account-config/logo.webp?v=1713886579229)
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
Example: BAK04AEE0123456720130311
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 04
- Change
Code specifying the type of acknowledgment
- AE
- Acknowledge - With Exception Detail Only
- AT
- Accepted
- RD
- Reject with Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
Date/Time Reference
To specify pertinent dates and times
If multiple ship dates at detail this is the 1st date.
Example: DTM06820130401
Name
To identify a party by type of organization, name, and code
Examples:
N1BT**92BALKCENT
N1BT**92TWA
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
- ARC
- Indianapolis, IN West Jordan, UT ARC Nashville, TN
- BALKCENT
- Plainfield, IN West Jordan, UT Nashville, TN
- DIRECT
- Direct
If BEG02 = ‘DS’.
- TWA
- Lithia Springs, GA
- TWP
- Payson, UT
Name
To identify a party by type of organization, name, and code
Example:
When BEG02-PO type = ‘SA’ and is a “Mark-For” order.
N1Z7Brunner’s Auto Store920000158199
Code identifying an organizational entity, a physical location, property or an individual
- Z7
- Mark-for Party
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Mark-for Drop Ship customer’s Identifier.
Address Information
To specify the location of the named party
Example: N3*101 TEST ROAD
Geographic Location
To specify the geographic place of the named party
Example: N4GREENVILLEIL*62246
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Name
To identify a party by type of organization, name, and code
Example: N1SF**92123456789
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Identifier of Shipping Location
Must be the same as PO N104.
Name
To identify a party by type of organization, name, and code
Examples
When BEG02-PO type = ‘SA’.
N1STUS AUTOMOTIVE PARTS GROUP PLAINFIELD92BALKCENT
When BEG02-PO type = ‘DS’.
N1STBRUNNER AUTO SUPPLY 565920000158197
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Identifier for Distribution Center
“BALKCENT” Plainfield, IN
“BALKWEST” West Jordan, UT
“NSH” Nashville, TN
“VISIONSLC“ Packager – Salt Lake City
“ARC” Indianapolis, IN
“ARW” West Jordan, UT
“ARN” ARC Nashville, TN
If BEG02 = ‘DS’ then N104 will contain the drop ship customer’s identifier. These account numbers will change must read the address sent.
Address Information
To specify the location of the named party
Example: N3*1601 WHITAKER ROAD
Geographic Location
To specify the geographic place of the named party
Example: N4PLAINFIELDIN*46168
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Required when a change is being requested for any given item on the order and all items on the order are to be included in the data feed (BAK02 = AE).
Example: PO116EA27.52BP735-4523VC21204
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Vendor Price
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
From PO
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VC
- Vendor's (Seller's) Catalog Number
Product/Item Description
To describe a product or process in coded or free-form format
Example: PIDFBLUE WIDGET
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Examples:
ACKAC
ACKIB12EA06820150215
Code specifying the action taken by the seller on a line item requested by the buyer
IS Substitution made for original item number.
R2 Item Cancelled –
- AC
- Item Accepted and Shipped
- BP
- Item Accepted - Partial Shipment, Balance Backordered
- DR
- Item Accepted - Date Rescheduled
- IB
- Item Backordered
Quantity in ACK02 placed on backorder, ACK05 must contain new expected ship date.
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
ACK02 is the new order quantity.
- IR
- Item Rejected
Bad or Unknown item number.
- IS
- Item Accepted - Substitution Made
Substitute item number present in ACK07 and ACK09. Quantity is shipped as ordered.
- R2
- Item Rejected
Obsolete item or not yet available.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code specifying type of date or time, or both date and time
Only include if ship schedule is different from date in DTM02.
- 068
- Current Schedule Ship
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Only include when ACK01 = 'IS'.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Only include when ACK01 = 'IS'.
- VC
- Vendor's (Seller's) Catalog Number
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.
Example: CTT136
Total number of line items in the transaction set
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.
-.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.
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
ITEM ACCEPTED – PRICE CHANGED
GS*PR*SENDERGS*RECEIVERGS*20240509*163740*000000001*X*004010~
ST*855*0001~
BAK*04*AE*E0574732*20160219~
DTM*068*20160304~
N1*SF**92*123456789~
N1*ST*US AUTOMOTIVE PARTS GROUP SALT LAKE CITY*92*BALKWEST~
N3*8915 SOUTH 4000 WEST~
N4*WEST JORDAN*UT*84088~
PO1*000002*480*EA*1.47**BP*782-5521*VC*00940202ZPGLOBK~
PID*F****FUSE - ATO BLADE 32V ASST 5PK US AUTOMOTIVE PARTS GROUP~
ACK*IP*480*EA*068*20160304~
CTT*1*1~
SE*12*0001~
GE*1*000000001~
IEA*1*000000001~
ITEM BACKORDERED
GS*PR*SENDERGS*RECEIVERGS*20240509*163552*000000001*X*004010~
ST*855*01057779~
BAK*04*AE*01057779*20160229~
DTM*068*20160424~
N1*SF**92*123456789~
N1*ST*NAPA OF BOILING SPRINGS 648*92*0000035433~
N3*3433 BOILSING SPRINGS HWY~
N4*BOILING SPRINGS*SC*29316~
PO1*1*1*EA*10.39**BP*S.40320*VC*40320~
PID*F****BEARING SET, CONROD, .010, 85035A~
ACK*IB*1*EA*068*20160424~
CTT*1*1~
SE*12*01057779~
GE*1*000000001~
IEA*1*000000001~
ITEM PARTIAL BACKORDERED
GS*PR*SENDERGS*RECEIVERGS*20240509*163705*000000001*X*004010~
ST*855*01057779~
BAK*04*AE*01057779*20160229~
DTM*068*20160424~
N1*SF**92*123456789~
N1*ST*NAPA OF BOILING SPRINGS 648*92*0000035433~
N3*3433 BOILSING SPRINGS HWY~
N4*BOILING SPRINGS*SC*29316~
PO1*1*10*EA*10.39**BP*S.40320*VC*40320~
PID*F****BEARING SET, CONROD, .010, 85035A~
ACK*AC*8*EA*068*20160424~
ACK*IB*2*EA*068*20160524~
CTT*1*1~
SE*13*01057779~
GE*1*000000001~
IEA*1*000000001~
ITEM SPLIT BACKORDERED
GS*PR*SENDERGS*RECEIVERGS*20240509*163631*000000001*X*004010~
ST*855*01057779~
BAK*04*AE*01057779*20160229~
DTM*068*20160424~
N1*SF**92*123456789~
N1*ST*NAPA OF BOILING SPRINGS 648*92*0000035433~
N3*3433 BOILSING SPRINGS HWY~
N4*BOILING SPRINGS*SC*29316~
PO1*1*10*EA*10.39**BP*S.40320*VC*40320~
PID*F****BEARING SET, CONROD, .010, 85035A~
ACK*IB*8*EA*068*20160424~
ACK*IB*2*EA*068*20160524~
CTT*1*1~
SE*13*01057779~
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.