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
Veyer’s PO Number must match EXACTLY what was sent on the EDI PO.
Example:
BAK00AD~ 15971515-110520070501~~~~11077720520070501}
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
- AD
- Accept with Detail
- RD
- Reject with Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
Veyer’s Original PO Number
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
Veyer’s Original PO 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’s Order Number
Reference Identification Customer Account Number
To specify identifying information
Example: REFCO12345678} ODP Business Solutions AOPS Customer Account Number
Code qualifying the Reference Identification
- CO
- Customer Account Number
Reference Identification Document Number
To specify identifying information
Example: REFQC083431107001} ODP Business Solutions AOPS Order Number
Code qualifying the Reference Identification
- QC
- Document Number
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Example: PO1148EA3.1~~VA1111IN0173179UP051131069060MG~MFR’s Part Number}
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Veyer’s Purchase Order Line Number
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.
Acknowledged Unit 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.
- VA
- Vendor's Style Number
Identifying number for a product or service
Vendor’s Style Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Identifying number for a product or service
Veyer Item Number (SKU #)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
UPC Consumer Package Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer's Part Number
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Example: ACKIA48EA08320100501~~ZZI1 Invalid Item Cost}
Code specifying the action taken by the seller on a line item requested by the buyer
- IA
- Item Accepted (Fill)
- IR
- Item Rejected (Kill)
Numeric value of quantity
Quantity accepted or rejected
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
- 083
- Scheduled for Shipment
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Mutually Defined
Identifying number for a product or service
Reason Codes and Descriptions must be sent when ACK01 = “IA” or “IR”.
- I1 Invalid Item Cost
- I1 Invalid Item Cost
Send in ACK01 Response: IA
- I3 Out of Stock
- I3 Out of Stock
Send in ACK01 Response: IR
- I4 Bad SKU
- I4 Bad SKU
Send in ACK01 Response: IR
- I5 Product Has Been Discontinued
- I5 Product Has Been Discontinued
Send in ACK01 Response: IR
- IB Backorder
- IB Backorder
Send in ACK01 Response: IR
- O1 Duplicate Order
- O1 Duplicate Order
Send in ACK01 Response: IR
- O2 Order Info Missing
- O2 Order Info Missing
Send in ACK01 Response: IR
- R3 Unit of Issue (UOM)
- R3 Unit of Issue (UOM)
Send in ACK01 Response: IA
- S1 Cannot Ship USPS
- S1 Cannot Ship USPS
Send in ACK01 Response: IR
- S2 Cannot Ship to PO Box
- S2 Cannot Ship to PO Box
Send in ACK01 Response: IR
- S3 Cannot Ship to Country
- S3 Cannot Ship to Country
Send in ACK01 Response: IR
- S4 Invalid Method of Shipment
- S4 Invalid Method of Shipment
Send in ACK01 Response: IR
- S5 Bad Address
- S5 Bad Address
Send in ACK01 Response: IR
- S6 Cannot Ship as Ordered
- S6 Cannot Ship as Ordered
Send in ACK01 Response: IR
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: CTT148}
Total number of line items in the transaction set
Total Number of Lines Acknowledged
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.
Total Quantity Acknowledged
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 1
GS~PR~SENDERGS~RECEIVERGS~20231208~162047~000000001~X~004010}
ST~855~100001}
BAK~00~AD~15971515-1105~20100501~~~~110777205~20100501}
REF~CO~12345678}
REF~QC~083431107001}
PO1~1~48~EA~3.7~~VA~1111~IN~0173179~UP~051131069060~MG~MFR’s Part Number}
ACK~IA~48~EA~083~20100501~~ZZ~I1 Invalid Item Cost}
CTT~1~48}
SE~8~100001}
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.