X12 860 Purchase Order Change Request - Buyer Initiated (Domestic)
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
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
Code identifying purpose of transaction set
- 01
- Cancellation
- 53
- Completion
Close the PO with the date sent in BCH11
- SU
- Status Update
Code specifying the type of Purchase Order
- CP
- Change to Purchase Order
for Regular Purchase Order
- ZZ
- Mutually Defined
for Back Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD
- BCH06 is the date assigned by the purchaser to purchase order.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Vendor Number assigned by CVS
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
Delivery Requested
To specify pertinent dates and times
Promised for Delivery – Old Delivery Date
To specify pertinent dates and times
Promised for Delivery – Old Delivery Date
Will be sent only if Old Delivery date is not = to zero
Name
To identify a party by type of organization, name, and code
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)
- 54
- Warehouse
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.
DC Code
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)
- CA
- Changes To Line Items
- CF
- Cancel Previously Transmitted Purchase Order
- DI
- Delete Item(s)
- NC
- Concurrent Item (No Change)
Quantity left to receive as qualified by the unit of measure
Required field – ignore, will always be zero
Price per unit of product, service, commodity, etc.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PI
- Purchaser's Item Code
Identifying number for a product or service
CVS Item Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UD
- U.P.C./EAN Consumer Package Code (2-5-5)
- UI
- U.P.C. Consumer Package Code (1-5-5)
Identifying number for a product or service
Item UPC Number or EAN
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ND
- National Drug Code (NDC)
If RX – ND (NDC)
Identifying number for a product or service
NDC if RX
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PQ
- Product ID Attribute Code
Identifying number for a product or service
01QTY and Regular Quantity (X07)
(01QTY0000099)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PQ
- Product ID Attribute Code
Identifying number for a product or service
DLQTY and Deal Quantity (X7)
(DLQTY0000099)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PQ
- Product ID Attribute Code
Identifying number for a product or service
Promo Event code (X5)QTY and Promo Quantity #(X7) (00099QTY0000099)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PQ
- Product ID Attribute Code
Identifying number for a product or service
Seasonal event code (X2)QTY and Seasonal quantity #(X7)
(XXQTY0000099)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Period Amount
To indicate a quantity, and/or amount for an identified period
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.
- X
- Semi-structured (Code and Text)
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
- ZZ
- Mutually Defined
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
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
Domestic PO Change Example
GS*PC*SENDERGS*RECEIVERGS*20231120*040001*000000001*X*004010~
ST*860*0001~
BCH*SU*ZZ*9999999***20100106*****20100129~
REF*VR*19999*29~
PER*BD*KIMBERLY O'CONNOR*******9~
DTM*002*20100119~
N1*ST**54*E101~
POC**CA*10*0*CA*.74**PI*123456*UI*00999999999*********PQ*LXQTY0000010~
PAM****1*7~
PID*X**ZZ*37*Item Description~
PO4*12~
POC**CA*14*0*CA*.52**PI*213456*UI*09999999999*********PQ*LXQTY0000014~
PAM****1*7~
PID*X**ZZ*36*Item Description~
PO4*8~
CTT*2~
SE*16*0001~
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.