X12 860 Purchase Order Change Request
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.
For SAS, BCH01 will always contain code 04. Since no order level cancel will be transmitted, the vendor must be sure to cancel the order from their books when all items on an order have been canceled.
Code identifying purpose of transaction set
- 01
- Cancellation
- 04
- Change
Code specifying the type of Purchase Order
- IN
- Information Copy
- RE
- Reorder
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
1 - 7 Release number from the PO (BCH02 contains code RL)
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
- BT
- Batch Number
- CO
- Customer Order Number
- DP
- Department Number
- IA
- Internal Vendor Number
- MI
- Mill Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
3 - 3 Batch number (REF01=BT)
12 - 12 Customer order number (REF01=CO)
3 - 3 Department number (REF01=DP
9 - 9 Internal vendor number (REF01=IA)
8 - 8 Mill order number (REF01=MI)
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 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.
4 - 7 Buying party (N101=BY)
9 - 9 Ship from (N101=SF)
4 - 7 Ship to (N101=ST)
Address Information
To specify the location of the named party
This segment is used only by ISOS and RSOS to change address information for the ship to customer or installer.
Geographic Location
To specify the geographic place of the named party
This segment is used only by ISOS and RSOS to change address information for the ship to customer or installer.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This segment is used only by ISOS and RSOS to specify new contact information for the party specified in the associated N1 segment.
Code identifying the major duty or responsibility of the person or group named
- DC
- Delivery Contact
Code identifying the type of communication number
- TE
- Telephone
Detail
Line Item Change
To specify changes to a line item
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
- CT
- Change of Dates
- DI
- Delete Item(s)
- PC
- Price Change
- 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
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 EAN number (POC Qualifier=EN)
4 - 5 Sears’ item number (POC Qualifier=IN)
1 - 5 Sears’ style number (POC Qualifier=IT)
3 - 3 Sears’ SKU Number (POC Qualifier=IZ)
12 - 12 U.P.C. number (POC Qualifier=UP)
1 - 30 Vendor's style number (POC Qualifier=VA)
1 - 15 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
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- 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
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- 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
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- 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
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Date/Time Reference
To specify pertinent dates and times
This segment is used to specify a revised ship date for the associated 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
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.