X12 860 DTC 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
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
- 00400
- Standard Issued as ANSI X12.5-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
- 004000
- ASC X12 Standards Approved by ANSI in 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
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 Change
To indicate the beginning of the Purchase Order Change Transaction Set and transmit identifying numbers and dates
If the BCH01 = “01”, the PO has been cancelled. No additional detail segments will be transmitted.
Example: BCH01SA900800564820190405***20190407~
Code identifying purpose of transaction set
- 01
- Cancellation
- 04
- Change
Code specifying the type of Purchase Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
TSC 10-digit PO Number
Date expressed as CCYYMMDD
- BCH06 is the date assigned by the purchaser to purchase order.
This is the date the original PO was created.
Date expressed as CCYYMMDD
- BCH11 is the date of the purchase order change request.
This is the date the PO Change was created.
Reference Identification
To specify identifying information
Example: REFIA880000
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
TSC’s 6-digit Vendor #
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example:
PERCNDrop Ship CoordinatorEMdropshipmc@tractorsupply.com~
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Detail
Line Item Change
To specify changes to a line item
Will only be included if the BCH01 value is "04".
Example: POC10AIEA33UP123456789012VNWO88333IN*1234567~
Alphanumeric characters assigned for differentiation within a transaction set
- POC01 is the purchase order line item identification.
Line number from the 850 purchase order.
Code specifying the type of change to the line item
- AI
- Add Additional Item(s)
- DI
- Delete Item(s)
- RZ
- Replace All Values
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
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)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Vendor's item/part number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IN
- Buyer's Item Number
Identifying number for a product or service
TSC's 7-digit item number.
Quantity
To specify quantity information
Will only be included if the BCH01 value is "04".
Example: QTYA59*EA~
Summary
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
Full Order Cancellation Sample
PER*CN*Drop Ship Coordinator*EM*dropshipmc@tractorsupply.com~
DTM*010*20190717~
Line Cancellation Sample
PER*CN*Drop Ship Coordinator*EM*dropshipmc@tractorsupply.com~ DTM*010*20140717~
POC*20*DI****33**UP*123456789012*VN*99JHGH5*IN*1234567~
QTY*A5*2*EA~
Replace All Values (Change) Sample
PER*CN*Drop Ship Coordinator*EM*dropshipmc@tractorsupply.com~
DTM*010*20190715~
POC*00010*RZ****33**UP*123456789012*VN*99JHGH5*IN*1234567~
QTY*A5*2*EA~
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.