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
- 01
- Duns (Dun & Bradstreet)
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
When notifying a retailer of a vendor-generated replenishment order, either code 00 or 16 is used in BAK01 and code AP is used in BAK02. When acknowledging a retailer's purchase order, code 00 is used in BAK01 and either code AD or AK is used in BAK02.
When changing a vendor-generated replenishment order, code 05 is used in BAK01 and code AP is used in BAK02. When acknowledging a retailer's purchase order with change, code 19 is used in BAK01 and either code AC or AE is used in BAK02.
When canceling a vendor-generated replenishment order, code 01 is used in BAK01 and code AP is used in BAK02. When acknowledging a retailer's purchase order with a cancellation, code 01 is used in BAK01 and code RJ is used in BAK02.
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 05
- Replace
- 16
- Proposed
- 19
- Seller initiated change
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AD
- Acknowledge - With Detail, No Change
- AE
- Acknowledge - With Exception Detail Only
- AK
- Acknowledge - No Detail or Change
- AP
- Acknowledge - Product Replenishment
- RJ
- Rejected - No Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
NOTIFICATION: Purchase order numbers are negotiable as part of trading partner relationships and can be pre-assigned in XPO01 or XPO02 in Transaction Set 852.
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
NOTIFICATION: When the BAK02 value is AK the date is the purchase order date. When the purchase order is vendor generated, the date should be the purchase order creation date.
Reference Identification Department Number
To specify identifying information
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
When REF01 equals 'DP' the Nordstrom department number will be sent in the REF02.
Department numbers are 4-numeric with leading 0's. For example, department 28 would be sent as
0028.
Reference Identification Vendor Number
To specify identifying information
When REF01 equals 'IA' the Nordstrom Assigned Vendor number will be sent in the REF02. Vendor numbers are 10-numeric with leading 0's.
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
When REF01 equals 'IA' the Nordstrom Assigned Vendor number will be sent in the REF02. Vendor numbers are 10-numeric with leading 0's.
Date/Time Reference Cancel After
To specify pertinent dates and times
Date/Time Reference Ship Not Before
To specify pertinent dates and times
Detail
The codes listed for PO106 apply to every occurrence of Data Element 235 in the PO1 segment.
See Section III for complete U.P.C. and EAN code definitions.
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
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
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
Note: This data element is used to clarify or alter the basis of unit price. The unit price expressed in PO104 is always in the same terms as the unit of measure in PO103, unless otherwise specified in PO105.
- PE
- Price per Each
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)
- VA
- Vendor'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)
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
Identifying number for a product or service
Destination Quantity
To specify destination and quantity detail
This segment is used to distribute the line item quantity to various locations. SDQ02 serves the same purpose as N103, and all occurrences of Data Element 67 in this segment function as N104. The SDQ segment functions as an N1 segment containing code BY in N101, that is, the SDQ segment specifies various buying locations. The N1 segment, in the basic order, specifies only one location.
An SDQ segment can hold up to 10 locations. When the PO has more than 10 locations, additional SDQ segments should be sent.
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.
Note: Nordstrom Store Numbers are 4 digits. For example Store 1 would be sent as 0001.
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
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
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.