X12 860 Purchase Order Change Request - Buyer Initiated
This X12 Transaction Set 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.
SDQ SEGMENT LOOPS BY EIGHT STORES (SDQ05 THRU SDQ22) FOR NEIMAN MARCUS STORES, CUSP, LAST CALL, NEIMAN MARCUS DIRECT AND BERGDORF GOODMAN. THESE DIVISIONS ALL UTILIZE 4 DIGIT STORE NUMBERS.
*NOTE - UPC CHANGES SHOULD INCLUDE BOTH AN AI AND DI POC SEGMENT
NEW VALUES ON POC02
**RQ = REDISTRO
- ~ 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
- 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
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).
- 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
Code identifying purpose of transaction set
- 01
- Cancellation
ENTIRE PO CANCEL ONLY BCH SEGMENT TRANSMITS
- 04
- Change
ANY CHANGE OTHER THAN PO CANCEL
Code specifying the type of Purchase Order
- BH
- Bill and Hold
USED FOR PACK AND HOLD
- NO
- Not for Sale
USED FOR COLLATERAL
- OS
- Special Order
SPORT-M2M
- PR
- Promotion
USED FOR TRUNKSHOW
- RE
- Reorder
- SA
- Stand-alone Order
USED FOR FASHION
- SP
- Sample
- SS
- Supply or Service Order
USED FOR EXPRESS ALLOCATION
- ST
- Standing Order
USED FOR REPLENISHMENT
- ZZ
- Mutually Defined
USED FOR IMPORT
Identifying number for Purchase Order assigned by the orderer/purchaser
NMG ASSIGNED PURCHASE ORDER NUMBER
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BCH06 is the date assigned by the purchaser to purchase order.
Ship Not Before Date
To specify pertinent dates and times
Detail
Line Item Change
To specify changes to a line item
Code specifying the type of change to the line item
- AI
- Add Additional Item(s)
- DI
- Delete Item(s)
- PC
- Price Change
(UNIT AND RETAIL) NO SDQ WILL BE SENT
- QD
- Quantity Decrease
- QI
- Quantity Increase
- RQ
- Reschedule/Quantity Change
- RZ
- Replace All Values
Numeric value of quantity
- POC03 is quantity ordered.
Quantity left to receive as qualified by the unit of measure
DIFFERENCE BETWEEN ORIGINAL QUANTITY AND NEW QUANTITY
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- LE
- Catalog Price per Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- EAN/UCC - 13
- UK
- GTIN 14-digit Data Structure
- UP
- UPC
Identifying number for a product or service
UPC 12 DIGIT NUMBER
EAN 13 DIGIT NUMBER
GTIN 14 DIGIT NUMBER
*REQUIRED ON ALL TRANSACTIONS WHEN PRESENT
*ALLOWED ONLY ONCE PER CARTON
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VA
- Vendor's Style Number
Identifying number for a product or service
MFG STYLE NUMBER
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Code identifying pricing specification
- MSR
- Manufacturer's Suggested Retail
Retail
To specify pricing information
Code identifying pricing specification
- RES
- Resale
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
PRODUCT DESCRIPTION
- 08
- Product
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
- 73
- Vendor color description
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
- 74
- Vendor size description
Destination Quantity
To specify destination and quantity detail
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying a party or other code
- SDQ03 is the store number.
NMG ASSIGNED LOCATION 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.
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.