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
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
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
Code identifying purpose of transaction set
- 01
- Cancellation
- 04
- Change
Code specifying the type of Purchase Order
- CP
- Change to Purchase Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
Date expressed as CCYYMMDD
- BCH06 is the date assigned by the purchaser to purchase order.
Purchase Order Date
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BCH09 is the seller's order number.
Supplier Sales Order Number
Date expressed as CCYYMMDD
- BCH11 is the date of the purchase order change request.
P.O. Change Request Date
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
This segment may be used or omitted
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- PC
- Prepaid but Charged to Customer
Code identifying the source of the transportation terms
Code identifying the trade terms which apply to the shipment transportation responsibility
- FOB
- Free on Board
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- DE
- Destination (Shipping)
- FA
- Factory
- OR
- Origin (Shipping Point)
A free-form description to clarify the related data elements and their content
Name
To identify a party by type of organization, name, and code
This segment may be used or omitted
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)
- 91
- Assigned by Seller or Seller's Agent
- 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.
If previous qualifier = ‘91’,
Supplier’s code.
If previous qualifier = ‘92’,
Distributor’s code
Additional Name Information
To specify additional names or those longer than 35 characters in length
This segment may be used or omitted
Address Information
To specify the location of the named party
This segment may be used or omitted
Geographic Location
To specify the geographic place of the named party
This segment may be used or omitted
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
This segment may be used or omitted
Code qualifying the Reference Identification
Other codes may be used in REF01 (element 128) besides that listed above. But, the codes must be mutually agreed upon before they are used.
- PR
- Price Quote Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
This segment may be used or omitted
Code describing the relationship of a carrier to a specific shipment movement
- O
- Origin Carrier (Air, Motor, or Ocean)
- Z
- Mutually Defined
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- 93
- Code assigned by the organization originating the transaction set
Code identifying a party or other code
Carrier Code
Code specifying the method or type of transportation for the shipment
- A
- Air
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.
Line Number from Purchase Order
Code specifying the type of change to the line item
- DI
- Delete Item(s)
- MU
- (Multiple) For Unit Price Quantity Reschedule Change
- NC
- Concurrent Item (No Change)
- PC
- Price Change
- PQ
- Unit Price/Quantity Change
- PR
- Unit Price/Reschedule Change
- QD
- Quantity Decrease
- QI
- Quantity Increase
- RQ
- Reschedule/Quantity Change
- RS
- Reschedule
Quantity left to receive as qualified by the unit of measure
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CM
- Centimeter
- EA
- Each
- FT
- Foot
- IN
- Inch
- MR
- Meter
Price per unit of product, service, commodity, etc.
Unit Price with maximum of five decimal places.
Code identifying the type of unit price for an item
- HP
- Price per Hundred
- PE
- Price per Each
- TP
- Price per Thousand
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Part Number
Reference Identification
To specify identifying information
This segment may be used or omitted
Code qualifying the Reference Identification
Other codes may be used in REF01 (element 128) besides those listed above. But, the codes must be mutually agreed upon before they are used.
- CO
- Customer Order Number
- DQ
- Delivery Quote Number
- GC
- Government Contract Number
- GP
- Government Priority Number
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Line Item Schedule
To specify the data for scheduling a specific line-item
This segment may be used or omitted
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CM
- Centimeter
- EA
- Each
- FT
- Foot
- IN
- Inch
- MR
- Meter
Code specifying type of date or time, or both date and time
- SCH05 specifies the interpretation to be used for SCH06 and SCH07.
- 002
- Delivery Requested
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.
This segment may be used or omitted
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
Sum of quantities in element POC03
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
Sample
BCH*04*CP*H0504857118**00000003*20060530~
FOB*PC***02*FOB*FA*FACTORY~
N1*ST*AVNET*92*H050~
TD5*O*92*STD~
POC*9*RS*160*160*EA*26.1*PE*VP*040090~
SCH*160*EA***002*20060719~
CTT*1*160~
SE*13*5850001~
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.