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
- 00
- Original
- 07
- Duplicate
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AH
- Acknowledge - Hold Status
- AT
- Accepted
- RJ
- Rejected - No Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
Purchase Order Number.
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
Purchase Order Date.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
This segment may be included if the Acknowledgment Type (BAK02) is AC.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
PO item number.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Order Quantity Unit of Measure.
- 03
- Seconds
- BD
- Bundle
- BF
- Board Feet
- BG
- Bag
- BM
- Bolt
- BO
- Bottle
- BR
- Barrel
- CA
- Case
- CF
- Cubic Feet
- CG
- Card
- CI
- Cubic Inches
- CL
- Cylinder
- CM
- Centimeter
- CN
- Can
- CT
- Carton
- CX
- Coil
- CY
- Cubic Yard
- DA
- Days
- DF
- Dram
- DH
- Miles
- DR
- Drum
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- GA
- Gallon
- GR
- Gram
- GS
- Gross
- HA
- Hank
- HR
- Hours
- HU
- Hundred
- HV
- Hundred Weight (Short)
- IN
- Inch
- JA
- Job
- JR
- Jar
- KG
- Kilogram
- KT
- Kit
- LB
- Pound
- LF
- Linear Foot
- LN
- Length
- LO
- Lot
- LT
- Liter
- LY
- Linear Yard
- MJ
- Minutes
- ML
- Milliliter
- MM
- Millimeter
- OZ
- Ounce - Av
- PA
- Pail
- PC
- Piece
- PD
- Pad
- PK
- Package
- PR
- Pair
- PT
- Pint
- QT
- Quart
- RL
- Roll
- RM
- Ream
- SC
- Square Centimeter
- SF
- Square Foot
- SH
- Sheet
- SI
- Square Inch
- SJ
- Sack
- SM
- Square Meter
- SO
- Spool
- SQ
- Square
- ST
- Set
- SY
- Square Yard
- TB
- Tube
- TG
- Gross Ton
- TH
- Thousand
- TO
- Troy Ounce
- TQ
- Thousand Feet
- UN
- Unit
- VI
- Vial
- ZP
- Page
- ZZ
- Mutually Defined
Price per unit of product, service, commodity, etc.
Item Unit Price.
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
- Buyer's Part Number
Pricing Information
To specify pricing information
• CTP should only be used when the Acknowledgment Type (BAK02) is "AC" and must be used to convey any price changes.
• The CTP segment is used in conjunction with an ACK01 segment "Line Item Status Code" (IP) for Price Change.
Code identifying pricing specification
- CON
- Contract Price
- INV
- Invoice Billing Price
- MAX
- Maximum Order Quantity Price
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Item Unit Price.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Ordered Quantity Unit of Measure.
- 03
- Seconds
- BD
- Bundle
- BF
- Board Feet
- BG
- Bag
- BM
- Bolt
- BO
- Bottle
- BR
- Barrel
- CA
- Case
- CF
- Cubic Feet
- CG
- Card
- CI
- Cubic Inches
- CL
- Cylinder
- CM
- Centimeter
- CN
- Can
- CT
- Carton
- CX
- Coil
- CY
- Cubic Yard
- DA
- Days
- DF
- Dram
- DH
- Miles
- DR
- Drum
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- GA
- Gallon
- GR
- Gram
- GS
- Gross
- HA
- Hank
- HR
- Hours
- HU
- Hundred
- HV
- Hundred Weight (Short)
- IN
- Inch
- JA
- Job
- JR
- Jar
- KG
- Kilogram
- KT
- Kit
- LB
- Pound
- LF
- Linear Foot
- LN
- Length
- LO
- Lot
- LT
- Liter
- LY
- Linear Yard
- MJ
- Minutes
- ML
- Milliliter
- MM
- Millimeter
- OZ
- Ounce - Av
- PA
- Pail
- PC
- Piece
- PD
- Pad
- PK
- Package
- PR
- Pair
- PT
- Pint
- QT
- Quart
- RL
- Roll
- RM
- Ream
- SC
- Square Centimeter
- SF
- Square Foot
- SH
- Sheet
- SI
- Square Inch
- SJ
- Sack
- SM
- Square Meter
- SO
- Spool
- SQ
- Square
- ST
- Set
- SY
- Square Yard
- TB
- Tube
- TG
- Gross Ton
- TH
- Thousand
- TO
- Troy Ounce
- TQ
- Thousand Feet
- UN
- Unit
- VI
- Vial
- ZP
- Page
- ZZ
- Mutually Defined
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
ACK segment should only be used when the Acknowledgment Type (BAK02) is assigned a value of 'AC' and it should only be used for the following reasons.
- Date Reschedule
- Price Changed
- Quantity Changed
- Item Rejection
Code specifying the action taken by the seller on a line item requested by the buyer
- DR
- Item Accepted - Date Rescheduled
- IA
- Item Accepted
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- IR
- Item Rejected
Numeric value of quantity
Ordered Quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Ordered Quantity Unit of Measure.
- 03
- Seconds
- BD
- Bundle
- BF
- Board Feet
- BG
- Bag
- BM
- Bolt
- BO
- Bottle
- BR
- Barrel
- CA
- Case
- CF
- Cubic Feet
- CG
- Card
- CI
- Cubic Inches
- CL
- Cylinder
- CM
- Centimeter
- CN
- Can
- CT
- Carton
- CX
- Coil
- CY
- Cubic Yard
- DA
- Days
- DF
- Dram
- DH
- Miles
- DR
- Drum
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- GA
- Gallon
- GR
- Gram
- GS
- Gross
- HA
- Hank
- HR
- Hours
- HU
- Hundred
- HV
- Hundred Weight (Short)
- IN
- Inch
- JA
- Job
- JR
- Jar
- KG
- Kilogram
- KT
- Kit
- LB
- Pound
- LF
- Linear Foot
- LN
- Length
- LO
- Lot
- LT
- Liter
- LY
- Linear Yard
- MJ
- Minutes
- ML
- Milliliter
- MM
- Millimeter
- OZ
- Ounce - Av
- PA
- Pail
- PC
- Piece
- PD
- Pad
- PK
- Package
- PR
- Pair
- PT
- Pint
- QT
- Quart
- RL
- Roll
- RM
- Ream
- SC
- Square Centimeter
- SF
- Square Foot
- SH
- Sheet
- SI
- Square Inch
- SJ
- Sack
- SM
- Square Meter
- SO
- Spool
- SQ
- Square
- ST
- Set
- SY
- Square Yard
- TB
- Tube
- TG
- Gross Ton
- TH
- Thousand
- TO
- Troy Ounce
- TQ
- Thousand Feet
- UN
- Unit
- VI
- Vial
- ZP
- Page
- ZZ
- Mutually Defined
Code specifying type of date or time, or both date and time
- 038
- Ship No Later
- 083
- Scheduled for Shipment (Prior to and Including)
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.
SCH is used to display original Schedule Dates which are located on the original Purchase Order (850).
Numeric value of quantity
Schedule Quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Line Item Unit of Measure.
- 03
- Seconds
- BD
- Bundle
- BF
- Board Feet
- BG
- Bag
- BM
- Bolt
- BO
- Bottle
- BR
- Barrel
- CA
- Case
- CF
- Cubic Feet
- CG
- Card
- CI
- Cubic Inches
- CL
- Cylinder
- CM
- Centimeter
- CN
- Can
- CT
- Carton
- CX
- Coil
- CY
- Cubic Yard
- DA
- Days
- DF
- Dram
- DH
- Miles
- DR
- Drum
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- GA
- Gallon
- GR
- Gram
- GS
- Gross
- HA
- Hank
- HR
- Hours
- HU
- Hundred
- HV
- Hundred Weight (Short)
- IN
- Inch
- JA
- Job
- JR
- Jar
- KG
- Kilogram
- KT
- Kit
- LB
- Pound
- LF
- Linear Foot
- LN
- Length
- LO
- Lot
- LT
- Liter
- LY
- Linear Yard
- MJ
- Minutes
- ML
- Milliliter
- MM
- Millimeter
- OZ
- Ounce - Av
- PA
- Pail
- PC
- Piece
- PD
- Pad
- PK
- Package
- PR
- Pair
- PT
- Pint
- QT
- Quart
- RL
- Roll
- RM
- Ream
- SC
- Square Centimeter
- SF
- Square Foot
- SH
- Sheet
- SI
- Square Inch
- SJ
- Sack
- SM
- Square Meter
- SO
- Spool
- SQ
- Square
- ST
- Set
- SY
- Square Yard
- TB
- Tube
- TG
- Gross Ton
- TH
- Thousand
- TO
- Troy Ounce
- TQ
- Thousand Feet
- UN
- Unit
- VI
- Vial
- ZP
- Page
- ZZ
- Mutually Defined
Code specifying type of date or time, or both date and time
- SCH05 specifies the interpretation to be used for SCH06 and SCH07.
- 038
- Ship No Later
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.
Total number of line items in the transaction set
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
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.