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
Qualifier 05 indicates that the supplier is making a correction to a previously sent 855. However it is acceptable for the supplier to provide qualifier 00 for the initial acknowledgment as well as any followup communications. Both qualifiers will be treated as an independent communication.
- 00
- Original
- 05
- Replace
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
Vendors are required to provide all of the items on the order with the individual item status.
- AT
- Accepted
All Items on the order are accepted as is with no changes and the supplier will ship and invoices as requested/indicated on the order (850).
- RJ
- Rejected - No Detail
Entire order is being rejected. Vendors are required to send an explanation of why the rejection in the N9/MSG segments.
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.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BAK08 is the seller's order number.
This can be the vendor defined reference number.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
- CN
- General Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 068
- Current Schedule Ship
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
Required if BAK02 = RJ or ACK01 = IR.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Message Text
To provide a free-form format that allows the transmission of text information
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)
- 54
- Warehouse
Used for ISN facility locations.
- ZZ
- Mutually Defined
Used for ISN Customer Drop Ship orders.
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.
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Detail
All items that were on the order must be included in the POA when BAK02 = AC and must indicate that Items status in the ACK segment. Vendors can send items when BAK02 = AT but is not required. When BAK02 = RJ,
items are not expected to be included in the 855.
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.
Must match ISN PO line number from the 850.
Quantity ordered
Used to confirm order quantity. If backordering an item, indicate the applicable quantity and date in the ACK segment.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Used to confirm UOM from PO.
- EA
- Each
Price per unit of product, service, commodity, etc.
Used to confirm PO cost. If the cost is incorrect on the order, vendors are to provide the requested/correct cost in the CTP segment.
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.
- CB
- Buyer's Catalog 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
Pricing Information
To specify pricing information
Code identifying pricing specification
- CHG
- Changed Price
Product/Item Description
To describe a product or process in coded or free-form format
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
When Item details are sent the ACK loop/segment is required.
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
- IA
- Item Accepted
- IB
- Item Backordered
When sending this code, ACK04 and ACK05 are required.
- IC
- Item Accepted - Changes Made
- IP
- Item Accepted - Price Changed
When indicating this code, corrected price needs to be included in the CTP segment.
- IR
- Item Rejected
Vendors are required to provide an explanation for why item is rejected in the POA header N9/MSG segments.
Numeric value of quantity
Required when ACK01 = IB.
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
Required when ACK01 = IB.
- 067
- Current Schedule Delivery
- 068
- Current Schedule Ship
Date/Time Reference
To specify pertinent dates and times
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.