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.
- ~ Segment
- * Element
- > Component
- ^ Repetition
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
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
EXAMPLE: BCH\04\CP\7606936\4\19990113~
Code identifying purpose of transaction set
- 02
- Add
- 03
- Delete
- 04
- Change
- 05
- Replace
Code specifying the type of Purchase Order
- CP
- Change to Purchase Order
Identifying number for Purchase Order assigned by the orderer/purchaser
BLI - assigned Purchase Order number (numeric only, no additional characters)
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
BLI - assigned
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.
Reference Information
To specify identifying information
EXAMPLE:
REF\LU\550\S~
REF\IA\1234567890~
REF\NB\C123456~
REF\PK\Y~
REF\ZZ\Y~
REF\FJ\125~
Code qualifying the Reference Identification
- FJ
- Total Units
- IA
- Internal Vendor Number
Number assigned by BLI
- LU
- Location Number
- NB
- Letter of Credit Number
- PK
- Packing List Number
- ZZ
- Pre-Ticket
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
When ‘LU’ - Location Number:
‘S’ – Store
‘W’ - Warehouse
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
EXAMPLE: PER\BD\JILL JONES~
On Vessel
To specify transportation instructions relating to shipment
EXAMPLE: FOB\PP\OV\FOB Cntry\\CA\Origin\Prepaid By Seller~
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- DE
- Delivery Duty Unpaid
- DF
- Split Half and Half
- PC
- Prepaid but Charged to Customer
- PP
- Prepaid (by Seller)
- PS
- Paid by Seller
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
Free On Board (FOB) point - IMPORTS
- OV
- On Vessel (Free On Board [FOB] point)
Free On Board (FOB) point - IMPORTS
A free-form description to clarify the related data elements and their content
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- CA
- Country of Origin
A free-form description to clarify the related data elements and their content
‘US’ – Will indicate a Domestic PO
A free-form description to clarify the related data elements and their content
Destination Shipping
To specify transportation instructions relating to shipment
EXAMPLE: FOB\PP\DE\Port \\OR\Ship Point\O~
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- DE
- Delivery Duty Unpaid
- DF
- Split Half and Half
- PC
- Prepaid but Charged to Customer
- PP
- Prepaid (by Seller)
- PS
- Paid by Seller
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
A free-form description to clarify the related data elements and their content
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- OR
- Origin (Shipping Point)
A free-form description to clarify the related data elements and their content
A free-form description to clarify the related data elements and their content
FOB Point - Indicates place where legal ownership of merchandise is transferred:
‘O’ – Origin - at the vendor's warehouse
‘D’ – Destination - at our warehouse or store
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
EXAMPLE: ITD\01\3\2\10\30\\\2%-10/NET 30~
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
- 01
- Basic
Code identifying the beginning of the terms period
- 3
- Invoice Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Note for Net Terms this element will default.
Number of days in the terms discount period by which payment is due if terms discount is earned
Note for Net Terms this element will default.
Number of days until total invoice amount is due (discount not applicable)
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
EXAMPLE:
DTM\073\19990101~
DTM\037\19990113~
DTM\002\19990123~
DTM\001\19990213~
Extended Reference Information
To transmit identifying information as specified by the Reference Identification Qualifier
EXAMPLE: N9\L1\Header Comments~
Text
To specify textual data
EXAMPLE: MTX\Header Comments~
Note this segment may occur multiple times for a single N9 loop.
To transmit large volumes of message text
Currently 80 characters but it is subject to change.
Party Identification
To identify a party by type of organization, name, and code
Required :
‘ST’ - Ship To
‘VN’ – Vendor
‘BT’ - Bill To
Optional:
‘SF’ - Ship From
‘RI’ - Remit To
EXAMPLE:
N1\ST \STORE 500\92\0500~
N1\BT\BIG LOTS STORES INC~
N1\SF\ABC CO~
N1\VN\ABC CO~
N1\RI\ABC CO~
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
N1-03 and N1-04 are optional
- RI
- Remit To
N1-03 and N1-04 are optional
- SF
- Ship From
N1-03 and N1-04 are optional
- ST
- Ship To
- VN
- Vendor
N1-03 and N1-04 are optional
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.
BLI maximum of 5 digit location
Party Location
To specify the location of the named party
EXAMPLE: N3\1417 N BELT HWY~
Geographic Location
To specify the geographic place of the named party
EXAMPLE: N4\SAINT JOSEPH\MO\645062415~
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)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
EXAMPLE: PER\IC\JILL JONES\TE\6142786800\FX\6142786676~
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Fax
Complete communications number including country or area code when applicable
Detail
Line Item Change
To specify changes to a line item
EXAMPLE:
POC\1\PQ\1\EA\8.955\SK\610000014\MG\D44-40T\UP\012300319861\ SZ\48OZ\BL\PREGO\\KM\20101110\SC\O\JP\N\ZZ\Y~
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
- PQ
- Unit Price/Quantity Change
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)
- SK
- Stock Keeping Unit (SKU)
Big Lots SKUs are numeric only 10 Digits Max
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer's Part Number
30 Characters
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- UCC - 12
Format 1-5-5-1
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SZ
- Vendor Alphanumeric Size Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BL
- Brand/Label
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CL
- Color
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- KM
- Shelf-Life Code
Identifying number for a product or service
Expiration Date Required for Consumables
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SC
- Seller's Date Code
Identifying number for a product or service
Seller’s Open/Close Date Code Required for Consumables
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- JP
- Package Type Code
Identifying number for a product or service
- F
- Flat
- G
- Garments on hangers
- H
- Hang
- N
- None
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Electronic Article Surveillance Tag
Identifying number for a product or service
- Y
- Required when requested
Additional Item Detail
To specify additional item-related data involving variations in normal price/quantity structure
EXAMPLE: P03\QO\\\1\CT~
Code specifying the reason for price or quantity change
- QO
- Carton Quantity Ordered
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO307 defines the unit of measure for PO306.
- CT
- Carton
Product/Item Description
To describe a product or process in coded or free-form format
EXAMPLE: PID\F\\Extension Table ~
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
A free-form description to clarify the related data elements and their content
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
EXAMPLE: PO4\1\\\\1\CF\\\1~
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Master Pack
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
Destination Quantity
To specify destination and quantity detail
EXAMPLE: SDQ\EA\92\0001\10\0002\20~
Segment will be used for palletized store quantity
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- EA
- Each
Code designating the system/method of code structure used for Identification Code (67)
- SDQ02 is used only if different than previously defined in the transaction set.
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- SDQ03 is the store 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.
EXAMPLE: CTT\2~
Monetary Amount Information
To indicate the total monetary amount
EXAMPLE: AMT\TT\287.200~
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*05*CP*7606936*4**19990113~
REF*LU*550*S~
REF*IA*1234567890~
REF*NB*C123456~
REF*PK*Y~
REF*ZZ*Y~
REF*FJ*125~
PER*BD*JILL JONES~
FOB*PP*OV*FOB Cntry***CA*Origin**Prepaid By Seller~
FOB*PP*DE*Port***OR*Ship Point**O~
ITD*01*3*2**10**30*****2%-10/NET 30~
DTM*073*19990101~
DTM*037*19990113~
DTM*002*19990123~
DTM*001*19990213~
N9*L1**Header Comments~
MTX**Header Comments~
N1*BT*BIGLOTS INC CORP~
N3*300 PHILLIPI RD~
N4*COLUMBUS*OH*432281310~
PER*IC*JOHN JONES*TE*6142786800*FX*6142786676~
N1*ST*STORE 500*92*0500~
N3*1417 N BELT HWY~
N4*SAINT JOSEPH*MO*645062415~
PER*IC*JILL JONES*TE*6142786800*FX*6142786676~
N1*VN*ABC CO~
N3*12 EAST HWY~
N4*JACKSON *MO*12345~
PER*IC*RODGER*TE*6142781234*FX*6142781235~
POC*1*PQ*1**EA*8.955**SK*610000014*MG*D44-40T*UP*012300319861*SZ*48OZ*BL*PREGO***KM*20101110*SC*O*JP*N*ZZ*Y~
PO3*QO*****1*CT~
PID*F**** Extension Table ~
PO4*1*******1*CF*****1~
SDQ*EA*92*0001*10*0002*20~
MTX**Detail Comments~
CTT*1~
AMT*TT*287.200~
SE*25*000101504~
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.