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
Code identifying purpose of transaction set
- 00
- Original
- 04
- Change
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
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.
Grainger Sales Order Number (This segment is populated in BEG04 of the 850 for Third Party Orders only).
Internal Customer Number
To specify identifying information
Code qualifying the Reference Identification
Third Party PO Only
- IT
- Internal Customer Number
Grainger Customer Purchase Order Number
Internal Vendor Number
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Grainger Internal Supplier Number
Special Instructions Number
To specify identifying information
Code qualifying the Reference Identification
Third Party PO Only
- KD
- Special Instructions Number
Grainger Brand Organization Code Value
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
Grainger Buyer Name (Mandatory)
- CN
- General Contact
Grainger Customer Contact (Optional)
- DI
- Delivery Instructions Contact
Grainger Customer Delivery Contact (Optional)
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
Additional Name Information
To specify additional names or those longer than 35 characters in length
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)
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)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 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.
Grainger plant code.
Refer to Grainger plant location spreadsheet for a listing of all Grainger plant locations.
Additional Name Information
To specify additional names or those longer than 35 characters in length
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)
Name
To identify a party by type of organization, name, and code
Additional Name Information
To specify additional names or those longer than 35 characters in length
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
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
It is Grainger’s expectation any PO1 data generated to the supplier via the EDI 850 PO will be returned in this segment.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
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.
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
Grainger Stock Number
Grainger Sourcing (FindMRO) Stock Number
- VP
- Vendor's (Seller'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)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CP
- Carry-over Part Number
Grainger Customer Material Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Grainger Customer PO Line Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MN
- Model Number
Manufacturer Model Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer'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)
This segment is a place holder for future use by Grainger and its suppliers.
- UD
- U.P.C./EAN Consumer Package Code (2-5-5)
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
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
Collect with exception.
Collect and allowed.
Consignee collect.
- PA
- Advance Prepaid
Prepaid and add.
- PO
- Prepaid Only
Prepaid with exception.
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
- OA
- Origin (After Loading on Equipment)
A free-form description to clarify the related data elements and their content
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- ZZ
- Mutually Defined
Carrier code qualifier.
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Code specifying special transportation handling instructions
- ZZZ
- Mutually Defined
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
- 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
(ACK02 = Quantity Available)
- DR
- Item Accepted - Date Rescheduled
- IA
- Item Accepted
- IB
- Item Backordered
- IE
- Item Accepted, Price Pending
- IF
- Item on Hold, Incomplete Description
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- 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
- R7
- Item Rejected, Reorder Item as a Drop Shipment
- SP
- Item Accepted - Schedule Date Pending
Line Item Schedule
To specify the data for scheduling a specific line-item
- The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of measurement code in the associated PO1 segment (PO103) and the sum of values of quantity (SCH01) should always equal the quantity ordered (PO102) in the PO1 segment.
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
- SCH05 specifies the interpretation to be used for SCH06 and SCH07.
- 068
- Current Schedule Ship
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
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
Sample
GS*PR*SENDERGS*RECEIVERGS*20231030*023018*000000001*X*004010~
ST*855*0004~
BAK*00*AC*4610000000*20110725****1134256352~
REF*IA*20001616~
REF*KD*20~
REF*IT*PO12345~
PER*BD*GRAINGER BUYER NAME*TE*847-566-7711*FX*847-566-5053*EM*GRAINGERBUYER@GRAINGER.COM~
PER*CN*GRAINGER CUSTOMER NAME*TE*CUSTOMER PHO*FX*CUSTOMER FAX NUMBER*EM*GRAINGERCUSTOMER@CUSTOMER.COM~
PER*DI*GRAINGER DELIVERY*TE*CUST DELIVRY*FX*CUSTOMER DELIVERY FAX NUMBER*EM*GRAINGERCUSTOMERDELIVERYCONTACT@CUSTOMER.COM~
N1*VN*W.W. GRAINGER~
N1*SF*SUPPLIER COMPANY~
N2*ATTN: DELIVERY~
N3*100 MAIN STREET~
N4*CHICAGO*IL*60601*US~
N1*ST*ABC COMPANY*92*TPSO~
N2*TOOL CRIB~
N3*157 WEST 57TH STREET~
N4*COLUMBUS*OH*43017*US~
PO1*1*1*EA*5.5**VP*GRAINGER PART NO*VN*SUPPLIER ITEM NO*CP*CUSTOMER MATERIAL NO*PL*GRAINGER CUSTOMER LINE ITEM NO*MN*MFR MODEL NO*MG*NFR PART NO~
PID*F****FREEFORM DESCRIPTION1~
PID*F****FREEFORM DESCRIPTION2~
FOB*TP*DE*THIRD PARTY PAY ACCOUNT NUMBER**FOB~
TD5**ZZ*GRAINGER CARRIER CODE**CODE DESCRIPTION~
TD4*ZZZ***DELIVERY INSTRUCTIONS~
ACK*IP*1*EA~
SCH*1*EA***068*20110809~
N9*L1**NOTES~
MSG*INFORMATION AS TO WHY AN ITEM WAS CHANGED, MODIFIED, ETC. OTHER NOTES BY SUPPLIER~
MSG*THIS IS MESSAGE LINE NUMBER 2~
CTT*1~
SE*30*0004~
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.