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
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
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
- AE
- Acknowledge - With Exception Detail Only
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.
The date assigned by the purchaser to the purchase order.
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 Reference Number
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- L1
- Letters or Notes
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
"PUR" Purchasing Information
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
City in which the ship from location is located.
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.
State in which the ship from location is located.
Name
To identify a party by type of organization, name, and code
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.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
City in which the ship to location is located.
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.
State in which the ship to location is located.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
VERIZON requires the Buyer's Part Number (BP) be transmitted in each PO1 segment. Without this product ID, VERIZON cannot match the Purchase Order Acknowledgment with the original Purchase Order.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
The line item identification from the original purchase order. VERIZON Logistics must have the original line item number from the PO to match the POA with the PO.
Quantity ordered
The quantity ordered on the original purchase order.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
The unit of measure code from the original purchase order.
Price per unit of product, service, commodity, etc.
The unit price of material from the original purchase order.
The price is sent with a decimal point only when needed, e.g. $15.95 would be Maximum of seven whole digits and five decimal places.
Code identifying the type of unit price for an item
The Basis of Unit Price code from the original purchase order.
Note: This value should be equivalent to the unit of measure basis
- HP
- Price per Hundred
- PE
- Price per Each
- PN
- Price per Ten
- TP
- Price per Thousand
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.
VERIZON recommends sending the Buyer's Part Number (BP) in PO106
- BP
- Buyer's Part Number
Identifying number for a product or service
VERIZON’s Part Number (associated to code 'BP' in PO106) ordered on the original purchase order
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
VERIZON recommends sending the Vendor's (Seller's) Item Number (VN) in PO108.
- VN
- Vendor's (Seller's) Item Number
Additional Item Detail
To specify additional item-related data involving variations in normal price/quantity structure
Code specifying the reason for price or quantity change
- QO
- Quantity Ordered
- QT
- Quantity Price Break
- UM
- Unit of Measure Difference
- UP
- Unit Price
Price per unit of product, service, commodity, etc.
New unit price of material.
Used when PO301 = 'QT' or 'UP'.
The price is sent with a decimal point only when needed, e.g. $15.95 would be sent as "15.95", and $29.00 would be sent as "29".
Maximum of eight whole digits and five decimal places.
Code identifying the type of unit price for an item
New Unit Price Basis associated to the New Unit Price identified in PO304.
Used when PO301 = 'QT' or 'UP'.
Note: The new unit price basis should be equivalent to the new unit of measure basis.
- HP
- Price per Hundred
- PE
- Price per Each
- PN
- Price per Ten
- TP
- Price per Thousand
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO307 defines the unit of measure for PO306.
The new measurement code associated to the new quantity in PO306.
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
- BP
- Item Accepted - Partial Shipment, Balance Backordered
- DR
- Item Accepted - Date Rescheduled
- IA
- Item Accepted
- IB
- Item Backordered
- IC
- Item Accepted - Changes Made
- ID
- Item Deleted
- IH
- Item on Hold
- IS
- Item Accepted - Substitution Made
Numeric value of quantity
Backordered Quantity
Used when ACK01 = 'BP' or 'IB'.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Unit of measure associated to the backorder quantity in ACK02.
Used when ACK01 = 'BP' or 'IB'
Code specifying type of date or time, or both date and time
To indicate the type of date.
Used when ACK01 = 'BP', 'DR', 'IA', 'IB', 'IC', 'IH', or 'IS'
- 079
- Promised for Shipment
Date expressed as CCYYMMDD
The promised ship date of the item being acknowledged.
Used when ACK01 = 'BP', 'DR', 'IA', 'IB', 'IC', 'IH', or 'IS'
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Used when ACK01 = 'IC' or 'IS'
- VN
- Vendor's (Seller's) Item 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.
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
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.