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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Code specifying the type of acknowledgment
Note:
The following BAK02 code indicates the order was accepted without errors and will be shipped. Only use if all Line Items are Confirmed.
Code Name
AT Accepted
Note:
The following code indicates the order was accepted with changes and will be shipped. Only use when more than one, but less than all Line Items are Acknowledged.
Code Name
AC Acknowledged With Detail and change
Note:
The following code indicates at least one item on the order had an error and the order will not ship. Only use when all Line Items are Rejected.
Code Name
RD Rejected with Detail
- AC
- Acknowledge - With Detail and Change
Order was accepted with changes and will be shipped. Only use when more than one, but less than all Line Items are Acknowledged.
- AT
- Accepted
Order was accepted without errors and will be shipped. Only use if all Line Items are Confirmed.
- RD
- Reject with Detail
At least one item on the order had an error and the order will not ship. Only use when all Line Items are Rejected.
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 Identification
To specify identifying information
Code qualifying the Reference Identification
- VN
- Vendor Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
CDW’s original Purchase Order Number
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.
- BP
- Paid by Buyer
- CA
- Advance Collect
- CC
- Collect
- MX
- Mixed
- PA
- Advance Prepaid
- PC
- Prepaid but Charged to Customer
- PP
- Prepaid
- PS
- Paid by Supplier/Vendor
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
A free-form description to clarify the related data elements and their content
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
Code identifying the beginning of the terms period
- 2
- Delivery Date
- 3
- Invoice Date
- 5
- Invoice Receipt Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Number of days in the terms discount period by which payment is due if terms discount is earned
Number of days until total invoice amount is due (discount not applicable)
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
- O
- Origin Carrier (Air, Motor, or Ocean)
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.
- 91
- Assigned by Seller or Seller's Agent
- ZZ
- Mutually Defined
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- D
- Parcel Post
- E
- Expedited Truck
- H
- Customer Pickup
- M
- Motor (Common Carrier)
- R
- Rail
- S
- Ocean
- SR
- Supplier Truck
- T
- Best Way (Shippers Option)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
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)
- 91
- Assigned by Seller or Seller's Agent
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
- ZZ
- Mutually Defined
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
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
- VN
- Vendor
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
- ZZ
- Mutually Defined
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
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
- BT
- Bill-to-Party
- EN
- End User
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
- ZZ
- Mutually Defined
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
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.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
From 850 PO1
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type of unit price for an item
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.
- BP
- CDW’s part number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer's Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- OE
- OEM Part Number
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)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UR
- UCC/EAN-128 Coupon Extended Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- AC
- Aggregation Code (Used to Consolidate Part Families)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- AH
- License Authorization Number
- BB
- Manufacturer Authorization Number
- BD
- Bid Request Number
- CT
- Contract Number
- EU
- CDW customer’s purchase order number
- GC
- Bid Contract Number
- IA
- Internal Vendor Number
- PO
- CDW purchase order number
- VN
- Vendor Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
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
Note:
The following ACK01 codes indicate the line is fully accepted and will be shipped.
IA Item Accepted.
Note:
The following codes indicate the order was entered. Acceptance pending changes.
BP Partial Backordered
DR Item Accepted - Date Rescheduled
IB Item Backordered
IE Price Pending
IF Item on hold, incomplete description
IH Item on hold
IP Item Accepted - Price Changed
IQ Item Accepted - Quantity Changed
SP Item Accepted - Scheduled Date Pending
Note:
The following ACK01 codes indicate the line was rejected:
IR Item Rejected
R2 Item not carried
- BP
- Partial Backordered
- DR
- Item Accepted - Date Rescheduled
- IA
- Item Accepted
- IB
- Item Backordered
- IE
- 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
- R2
- Item not carried
- 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
Code specifying type of date or time, or both date and time
- 017
- Estimated Delivery
- 067
- Current Schedule 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)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
This element can be used to include a reason code. Work with the CDW implementer to determine valid codes.
Identifying number for a product or service
This element can be used to include a reason code. Work with the CDW implementer to determine valid codes.
Code specifying type of date or time, or both date and time
An estimated delivery date is required. This can be included in either the ACK or DTM segments.
- 017
- Estimated Delivery
- 067
- Current Schedule Delivery
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.
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.
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
CDW 855 PO Acknowledgement
BAK~00~AC~1047023~20001003
REF~VN~000907
FOB~CA
ITD~01~3~1~~10~~30
TD5~~~~T
N1~ST~CDW COMPUTER CENTERS, INC.~91~DS
N2~JOHN~DOE
N3~200 N Milwaukee Ave~One CDW Parkway
N4~Vernon Hills~IL~60061~US~DE~01
PO1~000000~1~EA~9817.92~~BP~217220~MG~1234567~VP~C7834A#ABA~OE~OEM1234~UP~88698919064~UR~1234567890123~AC~XYZ123
REF~VN~000907
ACK~IA~1~EA~017~20060623~0001059436
DTM~067~20060616
DTM~017~20060617
CTT~1
AMT~TT~1234.56
SE~18~5730001
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.