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
BAK00AC900023456920060424***12345620040425
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AD
- Acknowledge - With Detail, No Change
- RD
- Reject with Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
Insight Purchase Order Number
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
Insight Purchase Order Date
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BAK08 is the seller's order number.
Vendor Sales Order Number
Date expressed as CCYYMMDD
- BAK09 is the date assigned by the sender to the acknowledgment.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
CURBYUSD
CURBYCAD
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
PO10000107EA29.99CPBP55555523VP*777777723
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
This is the line item number from the original Purchase Order. This number must match the line item number on the original purchase order. If the order was not sent via EDI and you are returning the 855 EDI you must number the line item 00010, 00020 00030 etc.
Quantity ordered
This must equal the quantity from the original purchase order line.
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.
This is the price the vendor is charging Insight.
Code identifying the type of unit price for an item
- CP
- Current Price (Subject to Change)
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
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
Reference Identification
To specify identifying information
The REF segment will only be expected when the ACK01= 'IR'
REFZZIR5~Invalid/Missing End User information
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The following item-rejection codes should be used when the ACK01=IR
IR1 Duplicate Order
IR2 Insight Requested Cancellation
IR3 Invalid/Expired Agreement Number
IR4 Invalid Ship To
IR5 Invalid/Missing End User information
IR6 Shipping/Carrier Issue
IR7 Other
IR8 Cannot be ordered as a standalone part
IR9 EOL/Discontinued Part
IR10 Fill/Kill and no inventory available
IR11 Invalid/Missing material number
IR12 Missing/Incorrect/Expired quote
IR13 Minimum Order Quantity Required
IR14 Need HW/Serial Number
IR15 Not authorized to sell product
IR16 Price Discrepancy
IR17 SKU/Quantity does not match quote
A free-form description to clarify the related data elements and their content
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Line item changes (IC) are not accepted via EDI. Please contact the buyer before making any changes to the Insight PO.
The below ACK segments are describing a PO with an original quantity of seven:
Line Item Accepted; No changes:
ACKIA7EA055*20060425
Line Item Rejected; The quantity in ACK02 must equal the quantity from the original purchase order line: ACKIR7*EA
Line Item Fully Backordered; The quantity in ACK02 must equal the quantity from the original purchase order line: ACKIB7EA06820060505
Line Item Partially Backordered; If an item has been partially accepted and the remainder has been backordered, we would expect an ACK segment for the quantity accepted (ACKIA) and another ACK segment for the quantity Backordered (ACKIB)For Example: The original PO contained a line item which asked for a quantity of 7. Of that 7, only 3 could be shipped
nd 4 went on backorder. The following should be sent:
ACKIA3EA05520060428
ACKIB4EA068*20060519
Code specifying the action taken by the seller on a line item requested by the buyer
See examples below to determine how to use the various code combinations in this segment.
- IA
- Item Accepted
- IB
- Item Backordered
- IR
- Item Rejected
Numeric value of quantity
The sum of ACK02 elements must equal the corresponding quantity in the PO102.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code specifying type of date or time, or both date and time
- 055
- Confirmed
Used with ACK01 value IA. This is the confirmed ship date.
- 068
- Current Schedule Ship
Used with ACK01 value IB. This is the date the shipment is expected to ship.
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
CTT*1
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.