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
- None included
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Use of the BAK is crucial to the success of your 855 messages. The use of 00 in BAK01 should always be for the initial 855 and SU for any updates. If you only send SU the message may fail to process in Walmart.com's systems and could cause a customer service issue.
Code identifying purpose of transaction set
- 00
- Original
- SU
- Status Update
Use when reporting status changes to order
quantities after the original acknowledgement
submission.
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
When BAK-01 = "00" then a PO1 loop must be
present in Table 2 for each PO1 that was present in the Purchase Order. The ACK loop(s) within each PO1 loop should express a fulfillment plan that addresses the full Quantity Ordered.When BAK-01 = "SU" then a PO1 loop is only
required for the Lineitems where a change to the current fulfillment plan and/or purchase
terms/conditions is being reported. The ACK
loop(s) within a PO1 loop should express a
fulfillment plan that addresses the 'remaining'
quantity for a Lineitem (i.e. original Quantity
Ordered less any shipment or cancellation that
already occurred).
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
This is the date of the Purchase Order in question.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BAK08 is the seller's order number.
A unique id assigned by supplier to identify this transaction.
Date expressed as CCYYMMDD
- BAK09 is the date assigned by the sender to the acknowledgment.
This is the date of this acknowledgement.
Date/Time Reference
To specify pertinent dates and times
This DTM is used to tell the customer the date of the shipment.
Code specifying type of date or time, or both date and time
- 068
- Current Schedule Ship
Date of next planned shipment related to the
Purchase Order being acknowledged. All items in this 855 with a Table 2 ACK-01 value of "IA"
should be included in the shipment that is
scheduled for this date.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
This is the PO Line number from the 850. It is located in the PO101.
PLEASE NOTE: Due to the unique nature of the Drop-Ship business these numbers may not be sequential and may not start with 1. Please make sure you are using the original data from the 850.
Quantity ordered
The ACK loop(s) contained in this PO1 loop must provide a fulfillment plan that addresses this quantity.
When BAK-01 = "00" this should be the Quantity Ordered from the Purchase Order Lineitem.
When BAK-01 = "SU" this should be the quantity 'remaining' to be fulfilled for the Lineitem, which may be less than the original Quantity Ordered if some portion has already been shipped or canceled.
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
These 3 codes are used to notify Walmart.com about the item status.
The first 855 you send should only contain IA or IR to communicate that the item has been accepted or rejected. The second 855 should contain AR or IR if the item has been released to shipping or it has been
determined that the item needs to be cancelled. The ACK06 contains the action code that is required if you are cancelling/rejecting a line item.
- AR
- Item Accepted and Released for Shipment
Quantity specified in ACK-02 has been "Released for Shipment" or the package with the goods has been sealed, and will be included in next shipment executed in fulfillment of the Purchase Order.
- IA
- Item Accepted
Quantity specified in ACK-02 will be included in next shipment executed in fulfillment of the Purchase Order.
- IR
- Item Rejected
Quantity specified in ACK-02 will NOT be fulfilled (cancellation). ACK-06 must specify a cancel reason.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
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)
When ACK-01 = "IR" this element is required to convey a code that represents the reason for rejection (i.e. cancellation) of the specified quantity. Below are the codes that need to be sent:
"bad_sku"
"merchant_request"
"out_of_stock" "discontinued
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.
Total number of line items in the transaction set
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.