X12 855 Purchase Order Acknowledgment
This X12 Transaction Set 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
- None included
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
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
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
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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
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
Code specifying the type of acknowledgment
Drop ship Orders must include all items.
- AC
- Acknowledge - With Detail and Change
PO1 and ACK segments are required.
- AD
- Acknowledge - With Detail, No Change
PO1 and ACK segments are required.
- AK
- Acknowledge - No Detail or Change
Only mandatory header level information is required.
- RD
- Reject with Detail
PO1 and ACK segments are required.
- RJ
- Rejected - No Detail
Only mandatory header level information is required.
Identifying number for Purchase Order assigned by the orderer/purchaser
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
Customer Order Number
To specify identifying information
Code qualifying the Reference Identification
- CO
- Customer Order Number
Required if present on the Purchase Order.
Internal Vendor Number
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Forever 21 assigned vendor number.
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
- IC
- Information Contact
Code identifying the type of communication number
- EM
- Electronic Mail
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
- TE
- Telephone
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Only include segment if changing from the original order.
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- CF
- Collect, Freight Credited Back to Customer
- DF
- Defined by Buyer and Seller
- MX
- Mixed
- PC
- Prepaid but Charged to Customer
- PO
- Prepaid Only
- PP
- Prepaid (by Seller)
- PS
- Paid by Seller
- 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 the source of the transportation terms
- 01
- Incoterms
Current Schedule Delivery
To specify pertinent dates and times
Only send this segment if changing for the entire order. Else, if only the scheduled date for certain items is changing, use the ACK segment to indicate this.
Current Schedule Ship
To specify pertinent dates and times
Only send this segment if changing for the entire order. Else, if only the scheduled date for certain items is changing, use the ACK segment to indicate this.
If the Purchase Order (EDI 850) is being rejected in full (BAK02=RD or RJ) you must include a note as to why.
Extended Reference Information
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- L1
- Letters or Notes
Party Identification
To identify a party by type of organization, name, and code
Party Location
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
The Forever 21 assigned Item SKU must be returned if available.
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
PO1 loop is required when BAK02 = AD, AC or RD.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Numeric value of quantity
- PO102 is quantity ordered.
Original Ordered Qty
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.
This is the NET purchase price of the item.
If ACK01=IP, the new Price should be sent here.
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.
- EN
- EAN/UCC - 13
- UP
- UCC - 12
- 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)
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
Forever 21 assigned item SKU.
- UP
- UCC - 12
- 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)
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
Forever 21 assigned item SKU.
- UP
- UCC - 12
- 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)
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
Forever 21 assigned item SKU.
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
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
Mandatory
- 73
- Vendor color description
Mandatory
- 74
- Vendor size description
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
- DR
- Item Accepted - Date Rescheduled
- IA
- Item Accepted
- IB
- Item Backordered
- IP
- Item Accepted - Price Changed
- IQ
- Item Accepted - Quantity Changed
- IR
- Item Rejected
Numeric value of quantity
Required when ACK01 = DR, IB or IQ.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Required when ACK01 = DR, IB or IQ.
- EA
- Each
Code specifying type of date or time, or both date and time
Required when ACK01 = DR or IB.
- 067
- Current Schedule Delivery
- 068
- Current Schedule Ship
If the line item is being rejected (ACK01 = IR), you must include a note as to why.
Extended Reference Information
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- L1
- Letters or Notes
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
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.