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
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Example: BAK16AP3738641059620200106
Code identifying purpose of transaction set
- 16
- Proposed
Code specifying the type of acknowledgment
- AP
- Acknowledge - Product Replenishment
Identifying number for Purchase Order assigned by the orderer/purchaser
The PO number is pre-issued by HBC. The PO number is are 11-digits (i.e. 7-digit Purchase Order Number plus 4-digit ship-to location).
Reference Identification
To specify identifying information
Example: REFDP556
Code qualifying the Reference Identification
- DP
- Department Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Category Number
The REF02 should include HBC assigned department. Please confirm department number with your buying office.
Date/Time Reference
To specify pertinent dates and times
Example: DTM01020200113
Name
To identify a party by type of organization, name, and code
Example: N1ST**920596
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)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Ship-to Location Code
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Example: PO119EA*EN3661601679711
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
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
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT
- Buyer's Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BO
- Buyers Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Resale
To specify pricing information
Example: CTP*RES272
Code identifying pricing specification
- RES
- Resale
Code identifying pricing specification
- UCP
- Unit cost 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.
Numeric value of quantity
Buying Pack Qty
Destination Quantity
To specify destination and quantity detail
As many as 10 locations may be included within the SDQ segment. Multiple SDQ segments may be sent. For store addresses, please refer to the store and DC list available at hbcediextranet.hbc.com/.
Example:
SDQEA92VT11013VT11043VT11063VT11073VV11083VT11093VV11113TW11123TW11133CX11143
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code designating the system/method of code structure used for Identification Code (67)
- SDQ02 is used only if different than previously defined in the transaction set.
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- SDQ03 is the store number.
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
Code identifying a party or other code
Alphanumeric Store Code
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*12
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
Sample
GS*PR*SENDERGS*RECEIVERGS*20231101*015626*000000001*X*004010
ST*855*373864199
BAK*16*AP*37386410596*20200106
REF*DP*556
DTM*010*20200113
N1*ST**92*0596
PO1*1*9*EA***EN*9991601679711
CTP**UCP*112*1*EA
CTP**RES*272
SDQ*EA*92*TR1613*1*TR1560*1*TQ1601*3*TR1637*1*TR1604*1*TR1606*1*LS1617*1
PO1*2*2*EA***EN*9999601684296
CTP**UCP*25.05*1*EA
CTP**RES*80.5
SDQ*EA*92*TR1613*2
PO1*3*7*EA***EN*9991601676284
CTP**UCP*56*1*EA
CTP**RES*175
SDQ*EA*92*TR1613*1*TR1560*1*TQ1601*1*TR1637*1*TR1604*1*TR1606*1*LS1617*1
PO1*4*10*EA***EN*9991601670442
CTP**UCP*35.25*1*EA
CTP**RES*72
SDQ*EA*92*TR1613*2*TR1560*1*TQ1601*3*TR1637*1*TR1604*1*TR1606*1*LS1617*1
PO1*5*1*EA***EN*9991601666896
CTP**UCP*12.4*1*EA
CTP**RES*32
SDQ*EA*92*TR1963*1
SE*26*373864199
GE*1*000000001
IEA*1*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.