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
Example:
BAK00AP12345678919981001
BAK05AP12345678919981001
BAK01AP12345678919981001\
Code identifying purpose of transaction set
The "00" qualifier should be sent for new orders only. The "05" should
be sent when changing an order. The "01" should be sent when canceling an order.
- 00
- Original
- 01
- Cancellation
- 05
- Replace
Code specifying the type of acknowledgment
- AP
- Acknowledge - Product Replenishment
Identifying number for Purchase Order assigned by the orderer/purchaser
In the BAK03, a maximum field length of nine digits can be used for purchase order numbers. If the purchase order number is less than nine digits, it should be zero suppressed (no spaces included in the data element).
Unique purchase order numbers must be used when submitting Reverse Purchase Orders to Lowe's. An application on Loweslink™ will allow you to reserve purchase order numbers for this purpose. Documentation on how to register for this application as well as how to use the application can be found at LowesLink.com. Look under Partner Information / EDI Specifications and Business Examples / 855 - PO Reservation.
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
This should always be an eight-digit date (CCYYMMDD).
Reference Identification
To specify identifying information
Example:
REFWO22222
REFAN123456789\
Code qualifying the Reference Identification
- AN
- Cross-Dock Truck Load Number
- WO
- Replenishment Program (RP) Reference Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
For the Replenishment Program (RP) Reference number (REF01=WO), Lowe's Merchandising must provide the five digit internal RP reference number to be sent in this field. The RP Reference Number can vary based on the store/item combination and it can periodically change. Merchandising will advise you of any changes.
For the Cross-Dock Truck Load Number (REF01=AN), if you ship vendor prepared cross-dock (VPXD) orders to Lowe's, all VPXD orders that are to be shipped together on the same truck should be identified by the Truck Load Number field. The Truck Load Number assigned to VPXD orders should be the purchase order number from any VPXD order on the truck. The new VPXD Truck Load Number can be up to nine digits in length, with leading zeros suppressed. The Truck Load Number should be sent in the REF segment where the REF01 field should include ‘AN’ as the qualifier and the REF02 should contain the VPXD Truck Load Number.
This is an example of VPXD orders to be shipped on the same truck.
PO Number 123456789 VPXD Truck Load Number REFAN123456789
PO Number 123456790 VPXD Truck Load Number REFAN123456789
PO Number 123456791 VPXD Truck Load Number REFAN123456789
See the N1 segment for additional information on VPXD orders.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This segment should be used to communicate the name of the individual at our retail locations who placed the order. In case of a change, it should contain the name at the vendor location who is requesting the change.
Example:
PEROCJOHN DOE\
Date/Time Reference
To specify pertinent dates and times
Example:
DTM06719980826
DTM06819980825\
Code specifying type of date or time, or both date and time
Both the Delivery Date and the Ship Date are required on all 855 documents.
- 067
- Current Schedule Delivery
- 068
- Current Schedule Ship
Date expressed as CCYYMMDD
This date should always be an eight-digit date (CCYYMMDD).
Name
To identify a party by type of organization, name, and code
Example:
N1ST**94960
N1MA**94465\
Code identifying an organizational entity, a physical location, property or an individual
The MA code is sent for cross-dock purchase orders ONLY. The MA code will reference the ultimate store that will receive the cross-dock purchase order from Lowe's distribution center. The invoice sent back to Lowe's should be for the ultimate store for which the cross-dock order was intended.
- MA
- Party for whom Item is Ultimately Intended
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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.
This element should contain the location number for either the store or distribution center to which you are shipping. Only send one leading zero for stores 1 through 9. For all other stores, just send us the actual store number. Examples: store 02, store 23, store 302, store 1066.
Name
To identify a party by type of organization, name, and code
Example:
N1ST**94960
N1MA**94465\
Code identifying an organizational entity, a physical location, property or an individual
The ST code should always be sent, referencing either a distribution center or store. For a cross-dock order, the ST will represent the distribution center. The invoice sent back to Lowe's should be for the ultimate store for which the cross-dock order was intended
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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.
This element should contain the location number for either the store or distribution center to which you are shipping. Only send one leading zero for stores 1 through 9. For all other stores, just send us the actual store number. Examples: store 02, store 23, store 302, store 1066.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Example:
PO125EA2.5CB*12345\
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.
The price should be sent with a decimal point only when needed, e.g. $15.95 should be sent as "15.95", and $29.00 should be sent as "29".
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
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
This element should contain Lowe's item number or the UPC number for the product being shipped.
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.
Example:
CTT*1\
Total number of line items in the transaction set
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
BAK*00*AP*123456789*19981001~
REF*WO*22222~
REF*AN*123456789~
PER*OC*JOHN DOE~
DTM*067*19980826~
DTM*068*19980825~
N1*ST**94*960~
N1*MA**94*465~
PO1**25*EA*2.5**CB*12345~
CTT*1~
SE*12*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.