X12 860 Purchase Order Change Request - Buyer Initiated
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request - Buyer Initiated Transaction Set (860) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the information required for the customary and established business and industry practice relative to a purchase order change. This transaction can be used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties.
- ~ 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
- PC
- Purchase Order Change Request - Buyer Initiated (860)
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).
- 860
- Purchase Order Change Request - Buyer Initiated
Beginning Segment for Purchase Order Change
To indicate the beginning of the Purchase Order Change Transaction Set and transmit identifying numbers and dates
BCH01 will contain code 04 for all change requests except order
level cancellations. BCH01 will contain code 01 only when all open
items on the order are cancelled.
Code identifying purpose of transaction set
- 01
- Cancellation
- 04
- Change
Code specifying the type of Purchase Order
- RL
- Release or Delivery Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
9 – 11 Original P.O. number
Date expressed as CCYYMMDD
- BCH06 is the date assigned by the purchaser to purchase order.
Department Number
To specify identifying information
When REF01 contains code DP, REF02 contains 3 characters.
The department number for direct to store orders will be specified at the item level. REF02 when REF01 contains code DP will always contain 999 in the header REF segment.
Direct to store orders will only have one iteration of the REF segment to specify the 999 department number.
The department number for JIT or DC orders will be specified in the header in REF02 when REF01 contains code DP.
Code qualifying the Reference Identification
- DP
- Department Number
Internal Vendor Number
To specify identifying information
When REF01 contains code IA, REF02 contains 11 characters.
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Purchase Order Number Suffix
To specify identifying information
When REF01 contains code PS, REF02 contains 1 - 2 characters.
A = Accelerated flow
R = Regular
J1 = Just in Time Inventory (JIT)
Code qualifying the Reference Identification
- PS
- Purchase Order Number Suffix
Date/Time Reference
To specify pertinent dates and times
The DTM segment will be transmitted to specify a revised ship / delivery date only. If the date has not changed, this segment will not be sent.
Code specifying type of date or time, or both date and time
- 002
- Delivery Requested
- 010
- Requested Ship
- 074
- Requested for Delivery (Prior to and Including)
- 076
- Scheduled for Delivery (Week of)
Name
To identify a party by type of organization, name, and code
N101 will contain BY when the purchase order is for Just In Time
Inventory only (REF02 contains J1 when REF01 contains PS).
If N101 contains ST, N104 will contain the following:
Direct to store Duns # '008965873' + 4 character store number
OR
DC Duns # '000394726' + 4 character DC number
If N101 contains BY, N104 will contain the four position store unit number
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 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.
Detail
Line Item Change
To specify changes to a line item
POC segments will NOT be sent on order level cancellations
(BCH01 contains code 01) or order level ship date changes.
Each change to a line item will be specified in a separate POC loop.
Therefore, more than one POC loop for the same item may be present in the same transaction when more than one change is made to the item.
When an item is added to a purchase order (POC02 contains code AI), then all detail information for that item, including cost, pack quantities, and item description will be sent.
POC03 is the current (net) amount on order before the quantity is applied. POC04 is the quantity to be subtracted or added based upon the code in POC02. This is based on VICS retail industry standards.
If the shipping GTIN or retail GTIN (UPC or EAN number) is changed, there will be two POC segments generated. The first POC will contain code value DI in POC02 and the second will contain AI in POC02. Both POC segments will contain the same item line number in POC01.
The qualifiers used in data element 235 Product/Service ID Qualifier fields (e.g. POC06, POC08) may be sent in any order as long as they are paired with their appropriate Product ID. For example, the POC06 may contain UP if POC07 contains the U.P.C. number. Or POC06 may contain IN if POC08 contains the KSN (after EIM conversion.). In other words, the receiver of the 860 must be able to accept any 235 Product/Service ID Qualifier and the paired Product ID in any of the applicable fields.
POC02 containing code ‘CA’ is used to indicate that the pack quantities in the PO4 segment have changed.
If an item has been partially shipped and the remainder is cancelled by Sears Holdings, an item deletion (POC02 containing code DI) will be sent to cancel the balance
Alphanumeric characters assigned for differentiation within a transaction set
- POC01 is the purchase order line item identification.
Code specifying the type of change to the line item
- AI
- Add Additional Item(s)
- CA
- Changes To Line Items
- DI
- Delete Item(s)
- QD
- Quantity Decrease
- QI
- Quantity Increase
Quantity left to receive as qualified by the unit of measure
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 EAN number (POC Qualifier=EN)
9 - 9 Kmart KSN item number (POC Qualifier=IN)
14 - 14 Shipping GTIN (POC Qualifier=UK)
12 - 12 U.P.C. number (POC Qualifier=UP)
1 - 17 Vendor's item number (POC Qualifier=VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See POC09
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See POC09
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Product/Item Description
To describe a product or process in coded or free-form format
The PID segment is used to provide the item description. This segment will be present for added item only (POC01 contains code AI).
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
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The PO4 segment will be present if the pack quantities change. POC02 will contain code CA.
The PO4 segment may be present if an item is added (POC02 contains code AI).
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
- AS
- Assortment
- CA
- Case
- EA
- Each
Reference Identification
To specify identifying information
When REF01 contains code DP, REF02 contains 3 characters.
The department number for direct to store orders will be specified at the item level. REF02 when REF01 contains code DP will always contain 999 in the header REF segment.
The department number for JIT or DC orders will be specified in the header in REF02 when REF01 contains code DP.
Code qualifying the Reference Identification
- DP
- Department Number
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of POC segments.
If used, hash total (CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment.
CTT01 will contain a count of POC segments. If no POC segments are present, CTT01 will contain zero.
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.