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
Sample EDI:
BAK00AT1317126200706110850**0001369955~
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AT
- Accepted
- RD
- Reject with Detail
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.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
This is the PO Release number for Blanket Release Orders. The Release Number should be returned if it is in the 850 Release Purchase Order.
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)
Pass the Transaction Set Number that is being acknowledged to AT&T Mobility. This element will contain either 850 or 860.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BAK08 is the seller's order number.
The Supplier Order Number must be sent in the 855 PO Acknowledgement transaction.
PO Type
To specify identifying information
The REF02 "ZZ" element must contain the same value that was sent in the Original Purchase Order header REF02 "ZZ" element.
If the REF*ZZ is present in the 850, the REF02 from the 850 must be sent back to AT&T Mobility.
Sample EDI:
REFZZHandset Device Accessory~
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Revision Number
To specify identifying information
The PO Revision Number is generated for each PO Change that is created in the AT&T Mobility ERP system. The PO Revision Number must be returned in the 855 PO Acknowledgement.
The PO Revision Number will be sent in the EDI 860 Purchase Order Change transaction.
Sample EDI:
REFYBRevision Number~
Code qualifying the Reference Identification
- YB
- Revision Number
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This segment mandatory for contact information if N1 segment is not included in data.
Sample EDI:
PERBDFirstName LastNameTE123-456-7890~
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
Code identifying the type of communication number
PO Received
To specify pertinent dates and times
The Purchase Order Date is required for all EDI 855 transactions. This is the date of the original Purchase Order.
Sample EDI:
DTM00820070620~
Revision
To specify pertinent dates and times
The Purchase Order Revision Date as defined in the EDI 860 Purchase Order Change transaction.
The Purchase Order Revision Date is only required if the EDI 855 is acknowledging an EDI 860.
Sample EDI:
DTM17120070630~
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1STShip To Name92Ship To Code~
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Free-form name
Provide the Ship To Name from the Original Purchase Order if the N101 element contains qualifier "ST"
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.
Provide the Ship To Code as it appears in the Original Purchase Order.
Address Information
To specify the location of the named party
Sample EDI:
N3*STREET ADDRESS~
Geographic Location
To specify the geographic place of the named party
Sample EDI:
N4CITYSTZIPCOUS~
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)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This segment mandatory for contact information if N1 segment is included in data.
Sample EDI:
PERSTFirstName LastNameTE123-456-7890~
Code identifying the major duty or responsibility of the person or group named
- ST
- Ship To 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
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1SUSupplier Name92Supplier Code~
Code identifying an organizational entity, a physical location, property or an individual
- SU
- Supplier/Manufacturer
Free-form name
Provide the Supplier Site Name if the N101 element contains qualifier "SU".
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.
Provide the Supplier Code as it appears in the Original Purchase Order.
Address Information
To specify the location of the named party
Sample EDI:
N3*STREET ADDRESS~
Geographic Location
To specify the geographic place of the named party
Sample EDI:
N4CITYSTZIPCOUS~
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)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This segment mandatory for contact information if N1 segment is included in data.
Sample EDI:
PERSUFirstName LastNameTE123-456-7890~
Code identifying the major duty or responsibility of the person or group named
- SU
- Supplier 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
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Sample EDI:
PO11100EA424*SKRTL.12345VNVendor Item Number~
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
The Original Purchase Order or Purchase Order Change line number
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Price per unit of product, service, commodity, etc.
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.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Subline Item Detail
To specify product subline detail item data
Sample EDI:
SLN00011O120EA290**SKRTL.29805~
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
The SLN01 must match the PO101 Line Number.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
Unique Counter for each SLN iteration.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- O
- Information Only
Charges which relate to but may not be included in or added to the unit price of the SLN.
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- SK
- Stock Keeping Unit (SKU)
Product/Item Description
To describe a product or process in coded or free-form format
Sample EDI:
PIDF***ITEM DESCRIPTION~
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
Additional Item Detail
To specify additional item-related data involving variations in normal price/quantity structure
The PO3 segment is only used to pass the Extended Price to the partner.
Sample EDI:
PO3UP**EST120*0EA*290.00~
Code specifying the reason for price or quantity change
The PO301 is not used as a Change to the Purchase Order but is used as per the X12 Standard requirements dictate.
- UP
- Unit Price
Code identifying pricing specification
- EST
- Estimated Price
Price per unit of product, service, commodity, etc.
Extended Unit Price:
Calculated as Line Item Quantity x Item Unit Price = Extended Unit Price
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.
- EA
- Each
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
If BAK02 contains the qualifier "AT", the Estimated Delivery date must apply to all items on the Original Purchase Order. Do not use the "AT" qualifier in the BAK02 if there are changes to any line item.
The N9 Loop is required per ACK loop if any of the following codes are used in the ACK01:
ID, IF, IH, IR, IW, R1, R2, R3, R4, R5, R6, R7, R8
Sample EDI:
ACKIA120EA01720070608**SKRTL.29805~
Code specifying the action taken by the seller on a line item requested by the buyer
- AA
- Item Accepted - Order Forwarded to Alternate Supplier Location
- AC
- Item Accepted and Shipped
- AR
- Item Accepted and Released for Shipment
- 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
- IE
- Item Accepted, Price Pending
- IF
- Item on Hold, Incomplete Description
- IH
- Item on Hold
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- IR
- Item Rejected
- IS
- Item Accepted - Substitution Made
- IW
- Item on Hold-Waiver Required
- R1
- Item Rejected, Not a Contract Item
- R2
- Item Rejected, Invalid Item Product Number
- R3
- Item Rejected, Invalid Unit of Issue
- R4
- Item Rejected, Contract Item not Available
- R5
- Item Rejected, Reorder Item as a Just in Time (JIT) Order
- R6
- Item Rejected, Reorder Item as an Extended Delivery Order (EDO)
- R7
- Item Rejected, Reorder Item as a Drop Shipment
- R8
- Item Rejected, Reorder Item as a Surge Order
- SP
- Item Accepted - Schedule Date Pending
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
- 017
- Estimated Delivery
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)
Future usage
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
The N9 Loop is required per ACK loop if any of the following codes are used in the ACK01:
ID, IF, IH, IR, IW, R1, R2, R3, R4, R5, R6, R7, R8
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Sample EDI:
N9ZZDETAIL MESSAGE NOTES~
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Message Text
To provide a free-form format that allows the transmission of text information
Send additional message notes on why the item/component was rejected or changed.
If the item was accepted with no changes, the N9/MSG loop is not required.
Sample EDI:
MSGFREE-FORM MESSAGE TEXTSS~
Name
To identify a party by type of organization, name, and code
The N1ST on the detail-level N1 should match the N1ST from the header-level.
Sample EDI:
N1STShip To Name92Ship To 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.
Distribution List
To specify identifying information
Distribution Number is being sent with the Line Item. Default Distribution Number cannot be null.
Sample EDI:
REFKA1~
Code qualifying the Reference Identification
- KA
- Distribution List
Shipment ID
To specify identifying information
Shipment Number is being sent with the Line Item. Default Shipment Number cannot be null.
Sample EDI:
REFSI1~
Code qualifying the Reference Identification
- SI
- Shipper's Identifying Number for Shipment (SID)
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.
Sample EDI:
CTT*1~
Monetary Amount
To indicate the total monetary amount
- If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction amount as calculated by the sender.
Sample EDI:
AMTTT34800~
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
BAK*00*AT*1317126*20070611*0*850**0001369955~
REF*YB*Revision Number~
REF*ZZ*Handset Device Accessory~
PER*BD*FirstName LastName*TE*123-456-7890~
DTM*008*20070620~
DTM*171*20070630~
N1*ST*Ship To Name*92*Ship To Code~
N3*STREET ADDRESS~
N4*CITY*ST*ZIPCO*US~
PER*ST*FirstName LastName*TE*123-456-7890~
N1*SU*Supplier Name*92*Supplier Code~
N3*STREET ADDRESS~
N4*CITY*ST*ZIPCO*US~
PER*SU*FirstName LastName*TE*123-456-7890~
PO1*1*100*EA*424**SK*RTL.12345*VN*Vendor Item Number~
SLN*0001*1*O*120*EA*290***SK*RTL.29805~
PID*F****ITEM DESCRIPTION~
PO3*UP**EST*120**0*EA*290.00~
ACK*IA*120*EA*017*20070608**SK*RTL.29805~
N9*ZZ*DETAIL MESSAGE NOTES~
MSG*FREE-FORM MESSAGE TEXT*SS~
N1*ST*Ship To Name*92*Ship To Code~
REF*KA*1~
REF*SI*1~
CTT*1~
AMT*TT*34800~
SE*28*0001~
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.