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
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating 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 Acknowledgment (855)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
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) is 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
When using qualifier AE, only send the information that is changing.
When using qualifier AK, only the mandatory segments at the header level are required
When using qualifier RJ (Rejected) then the mandatory segments at the header level are required as well as the MTX segment.
Code specifying the type of acknowledgment
- AE
- Acknowledge - With Exception Detail Only
- AK
- Acknowledge - No Detail or Change
- RJ
- Rejected - No Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
Purchase Order Number.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BAK04 is the date assigned by the purchaser to purchase order.
Purchase Order Date
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BAK09 is the date assigned by the sender to the acknowledgment.
PO Acknowledgement Date / Original Requested Ship Date.
Reference Identification
To specify identifying information
Both of these numbers are required. The Vendor number sent back on the Invoice must be the same vendor number sent in REF(IA) on the 850 you received
Code qualifying the Reference Identification
- 19
- Division Identifier
- IA
- Internal Vendor Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Vendor Number
Reference Identification
To specify identifying information
If sent on the PO, this field is required on the PO Ack
Code qualifying the Reference Identification
- CO
- Customer Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Customer Order Number
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This is to be used to communicate who or what number Cabela's can use if questions arrives about this transaction
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Telephone #
Code identifying the type of communication number
- FX
- Facsimile
Complete communications number including country or area code when applicable
Fax #
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Email address
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Only send this information if a change is needed.
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- 11
- Rule 11 Shipment
- CC
- Collect
- CF
- Collect, Freight Credited Back to Customer
- FO
- FOB Port of Call
- HP
- Half Prepaid
- PB
- Customer Pick-up/Backhaul
- PP
- Prepaid (by Seller)
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- AC
- City and State
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
- PE
- Port of Entry
A free-form description to clarify the related data elements and their content
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- AC
- City and State
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
- PE
- Port of Entry
A free-form description to clarify the related data elements and their content
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Only send this information if a change is needed.
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- A
- Allowance
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- A260
- Advertising Allowance
- A990
- Cataloging Services
Page Allowance
- C260
- Discount - Incentive
Anticipation Discount
- C300
- Discount - Special
- C310
- Discount
- C320
- Display Allowance
Ad Compensation
- C540
- Early Buy Allowance
- D170
- Free Goods
- D240
- Freight
- D500
- Handling
- E270
- Late Order Charge
- E750
- New Store Discount
- F110
- Overrun Charge
Over Charge Allowance
- F800
- Promotional Allowance
Program Allowance
- F970
- Rebate
- G520
- Returned Load
Returns Allowance
- I530
- Volume Discount
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Code indicating on what basis allowance or charge percent is calculated
- 7
- Base Price Amount Less Previous Discount
Code indicating method of handling for an allowance or charge
- 02
- Off Invoice
A free-form description to clarify the related data elements and their content
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Only send this information if a change is needed.
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.
- 05
- Discount Not Applicable
- 08
- Basic Discount Offered
- 09
- Proximo
- 41
- Letter of Credit
Code identifying the beginning of the terms period
- 3
- Invoice 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)
A free-form description to clarify the related data elements and their content
Terms Description
The numeric value of the day of the month between 1 and the maximum day of the month being referenced
Date/Time Reference
To specify pertinent dates and times
Only send this information if a change is needed
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Only send this information if a change is needed
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.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
SCAC (Standard Carrier Alpha Code)
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- BU
- Bus
- CE
- Customer Pickup / Customer's Expense
- D
- Parcel Post
- E
- Expedited Truck
- H
- Customer Pickup
- L
- Contract Carrier
- M
- Motor (Common Carrier)
- R
- Rail
- S
- Ocean
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Code indicating the level of transportation service or the billing service offered by the transportation carrier
- CG
- Ground
- DS
- Door Service
- ND
- Next Day Air
- PB
- Priority Mail
- PI
- Priority Mail Insured
- SC
- Second Day Air
Code indicating the level of transportation service or the billing service offered by the transportation carrier
- CG
- Ground
- DS
- Door Service
- ND
- Next Day Air
- PB
- Priority Mail
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
This Loop is required for International orders as confirmation of Factory location but is optional for Vendor.
This information will assist in determining port of export. For Manufacturing Plant, when Loop is sent, the N1, N3 and N4 segments are required
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.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- BG
- Bag
- BK
- Book
- BN
- Bulk
- BO
- Bottle
- CA
- Case
- CQ
- Cartridge
- CT
- Carton
- DR
- Drum
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- GS
- Gross
- HU
- Hundred
- IN
- Inch
- LB
- Pound
- OZ
- Ounce - Av
- PH
- Pack (PAK)
- PK
- Package
- PL
- Pallet/Unit Load
- PR
- Pair
- Q4
- Fifty
- RL
- Roll
- SO
- Spool
- TB
- Tube
- TH
- Thousand
- UN
- Unit
- VC
- Five Hundred
- YD
- Yard
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.
- IN
- Buyer's Item Number
- UP
- UCC - 12
Identifying number for a product or service
Buyer's Part Number
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
Vendor Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- EAN/UCC - 13
- UP
- UCC - 12
Identifying number for a product or service
UPC/EAN Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UK
- EAN/UCC - 14
Identifying number for a product or service
GTIN
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
Code identifying the general class of a product or process characteristic
- 08
- Product
A free-form description to clarify the related data elements and their content
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
Code identifying the general class of a product or process characteristic
- 73
- Vendor color description
- 74
- Vendor size description
A free-form description to clarify the related data elements and their content
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
f ACK01= IB or DR, ACK04 and 05 are required
If ACK01 = IB or IQ, ACK02 and 03 are required
If ACK01 = IP, new price for this item must be sent in PO104
If ACK01 = IS, substitute vendor Item number must be sent in the PO1 segment, qualifier VN
Code specifying the action taken by the seller on a line item requested by the buyer
- DR
- Item Accepted - Date Rescheduled
- IA
- Item Accepted
- IB
- Item Backordered
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- IR
- Item Rejected
- IS
- Item Accepted - Substitution Made
- R2
- Item Rejected, Invalid Item Product Number
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- BG
- Bag
- BK
- Book
- BN
- Bulk
- BO
- Bottle
- CA
- Case
- CQ
- Cartridge
- CT
- Carton
- DA
- Days
- DR
- Drum
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- GS
- Gross
- HU
- Hundred
- IN
- Inch
- LB
- Pound
- OZ
- Ounce - Av
- PH
- Pack (PAK)
- PK
- Package
- PL
- Pallet/Unit Load
- PR
- Pair
- Q4
- Fifty
- RL
- Roll
- SO
- Spool
- TB
- Tube
- TH
- Thousand
- VC
- Five Hundred
- YD
- Yard
Code specifying type of date or time, or both date and time
- 068
- Current Schedule Ship
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Current Schedule Ship Date
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
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
Sample from Cabela's 1
BAK*00*AE*2581988*20081219*****20090126
REF*IA*Cabela Assigned Vendor number
REF*19*001
PER*IC*Customer Services*TE*216-431-3560
FOB*CC*AC*City
ITD*05*3*3.0**30**45*****3% 30days net 45
DTM*010*20081219
PO1**600*EA*6.5**IN*60035997*VN*S3D002C*UP*793539127873
PID*F*08***LOTION PUMP SECLUSION 3D
ACK*IB*600*EA*068*20090509
CTT*1
SE*13*0001
Sample from Cabela's 2
BAK*00*AE*2581988*20081219*****20090126
REF*CO*Customer Order number sent on 850
REF*IA*Cabela Assigned Vendor number
REF*19*001
PER*IC*Customer Services*TE*216-431-3560
DTM*010*20081219
PO1**600*EA*6.5**IN*60035997*VN*S3D002C*UP*793539127873
PID*F*08***LOTION PUMP SECLUSION 3D
ACK*IB*600*EA*068*20090509
CTT*1
SE*12*0001
Sample from Cabela's 3
BAK*00*AK*2581988*20081219*****20090126
REF*19*001
PER*IC*Customer Services*TE*216-431-3560
DTM*010*20081219
N1*MP*FACTORY NAME
N3*FACTORY STREET ADDRESS
N4*FACTORY CITY*MA*1234*US
PO1**600*EA*6.5**IN*60035997*VN*S3D002C*UP*793539127873
PID*F*08***LOTION PUMP SECLUSION 3D
ACK*IB*600*EA*068*20090509
CTT*1
SE*11*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.