REI
/
Purchase Order Change Request - Buyer Initiated
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from REI. Contact REI for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
REI logo

X12 860 Purchase Order Change Request - Buyer Initiated

X12 Release 4010
REI

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/rei/purchase-order-change-request-buyer-initiated/01HXW5Q75MJQ5GW5Y2DTH7XTA6
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BCH
020
Beginning Segment for Purchase Order Change
Max use 1
Required
REF
050
Reference Identification
Max use 1
Optional
FOB
080
F.O.B. Related Instructions
Max use 1
Optional
ITD
130
Terms of Sale/Deferred Terms of Sale
Max use 5
Optional
DTM
150
Date/Time Reference
Max use 10
Optional
TD5
240
Carrier Details (Routing Sequence/Transit Time)
Max use 12
Optional
N9 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PC
Purchase Order Change Request - Buyer Initiated (860)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BCH
020
Heading > BCH

Beginning Segment for Purchase Order Change

RequiredMax use 1

To indicate the beginning of the Purchase Order Change Transaction Set and transmit identifying numbers and dates

Example
BCH-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

04
Change
BCH-02
92
Purchase Order Type Code
Required
Identifier (ID)

Code specifying the type of Purchase Order

SA
Stand-alone Order
BCH-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCH06 is the date assigned by the purchaser to purchase order.
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCH11 is the date of the purchase order change request.
REF
050
Heading > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IA
Internal Vendor Number
PD
Promotion/Deal Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

FOB
080
Heading > FOB

F.O.B. Related Instructions

OptionalMax use >1

To specify transportation instructions relating to shipment

Example
If Description (FOB-07) is present, then Location Qualifier (FOB-06) is required
FOB-01
146
Shipment Method of Payment
Required
Identifier (ID)

Code identifying payment terms for transportation charges

  • FOB01 indicates which party will pay the carrier.
CC
Collect
PP
Prepaid (by Seller)
FOB-02
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

  • FOB02 is the code specifying transportation responsibility location.
DE
Destination (Shipping)
OR
Origin (Shipping Point)
FOB-06
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

  • FOB06 is the code specifying the title passage location.
ZZ
Mutually Defined
FOB-07
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

FOB-09
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

ITD
130
Heading > ITD

Terms of Sale/Deferred Terms of Sale

OptionalMax use 5

To specify terms of sale

Example
If Terms Discount Percent (ITD-03) is present, then Terms Discount Days Due (ITD-05) is required
ITD-03
338
Terms Discount Percent
Optional
Decimal number (R)
Min 1Max 6

Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date

ITD-05
351
Terms Discount Days Due
Optional
Numeric (N0)
Min 1Max 3

Number of days in the terms discount period by which payment is due if terms discount is earned

ITD-07
386
Terms Net Days
Optional
Numeric (N0)
Min 1Max 3

Number of days until total invoice amount is due (discount not applicable)

ITD-12
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
150
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

037
Ship Not Before
038
Ship No Later
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

TD5
240
Heading > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use 12

To specify the carrier and sequence of routing and provide transit time information

Example
TD5-05
387
Routing
Required
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

Usage notes

REI Vendor Guide

N9 Loop
OptionalMax >1
N9
285
Heading > N9 Loop > N9

Reference Identification

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

PO
Purchase Order Number
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

MSG
290
Heading > N9 Loop > MSG

Message Text

OptionalMax use 1000

To provide a free-form format that allows the transmission of text information

Example
MSG-01
933
Free-Form Message Text
Required
String (AN)
Min 1Max 264

Free-form message text

N9 Loop end
Heading end

Detail

POC Loop
OptionalMax >1
POC
010
Detail > POC Loop > POC

Line Item Change

RequiredMax use 1

To specify changes to a line item

Example
If Quantity Ordered (POC-03) is present, then Quantity Left to Receive (POC-04) and Composite Unit of Measure (POC-05) are required
If either Product/Service ID Qualifier (POC-08) or Product/Service ID (POC-09) is present, then the other is required
If either Product/Service ID Qualifier (POC-10) or Product/Service ID (POC-11) is present, then the other is required
If either Product/Service ID Qualifier (POC-12) or Product/Service ID (POC-13) is present, then the other is required
POC-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • POC01 is the purchase order line item identification.
POC-02
670
Change or Response Type Code
Required
Identifier (ID)

Code specifying the type of change to the line item

AI
Add Additional Item(s)
CA
Changes To Line Items
DI
Delete Item(s)
POC-03
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

POC-04
671
Quantity Left to Receive
Optional
Decimal number (R)
Min 1Max 9

Quantity left to receive as qualified by the unit of measure

POC-05
C001
Composite Unit of Measure
OptionalMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

POC-06
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

POC-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

VA
Vendor's Style Number
POC-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Vendor's Part Number

POC-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

UP
U.P.C. Consumer Package Code (1-5-5-1)
POC-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

POC-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

IN
Buyer's Item Number
POC-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PID Loop
OptionalMax >1
PID
050
Detail > POC Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

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
PID-02
750
Product/Process Characteristic Code
Optional
Identifier (ID)

Code identifying the general class of a product or process characteristic

08
Product
PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID Loop end
POC Loop end
Detail end

Summary

SE
030
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.