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

X12 860 Purchase Order Change Request - Buyer Initiated

X12 Release 4010

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 sample
    View the latest version of this implementation guide as an interactive webpage
    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
    FOB
    080
    F.O.B. Related Instructions
    Max use 1
    Optional
    N1 Loop
    detail
    POC 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

    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
    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

    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
    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
    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
    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
    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
    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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    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

    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
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    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
    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
    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

    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
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    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

    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

    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

    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
    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

    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

    Code identifying purpose of transaction set

    01
    Cancellation
    04
    Change
    BCH-02
    92
    Purchase Order Type Code
    Required

    Code specifying the type of Purchase Order

    CP
    Change to Purchase Order
    BCH-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BCH-05
    327
    Change Order Sequence Number
    Optional
    Min 1Max 8

    Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set

    BCH-06
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BCH06 is the date assigned by the purchaser to purchase order.
    Usage notes

    Purchase Order Date

    BCH-09
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    • BCH09 is the seller's order number.
    Usage notes

    Supplier Sales Order Number

    BCH-11
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BCH11 is the date of the purchase order change request.
    Usage notes

    P.O. Change Request Date

    FOB
    080

    F.O.B. Related Instructions

    OptionalMax use >1

    To specify transportation instructions relating to shipment

    Usage notes

    This segment may be used or omitted

    Example
    If Transportation Terms Qualifier Code (FOB-04) is present, then Transportation Terms Code (FOB-05) is required
    If Description (FOB-07) is present, then Location Qualifier (FOB-06) is required
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    PC
    Prepaid but Charged to Customer
    FOB-04
    334
    Transportation Terms Qualifier Code
    Optional
    Min 2Max 2

    Code identifying the source of the transportation terms

    FOB-05
    335
    Transportation Terms Code
    Optional

    Code identifying the trade terms which apply to the shipment transportation responsibility

    FOB
    Free on Board
    FOB-06
    309
    Location Qualifier
    Optional

    Code identifying type of location

    • FOB06 is the code specifying the title passage location.
    DE
    Destination (Shipping)
    FA
    Factory
    OR
    Origin (Shipping Point)
    FOB-07
    352
    Description
    Optional
    Min 1Max 80

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

    N1 Loop
    OptionalMax >1
    N1
    300

    Name

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Usage notes

    This segment may be used or omitted

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

    For Drop Ships only

    N1-03
    66
    Identification Code Qualifier
    Optional

    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
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 80

    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.
    Usage notes

    If previous qualifier = ‘91’,
    Supplier’s code.
    If previous qualifier = ‘92’,
    Distributor’s code

    N2
    310

    Additional Name Information

    OptionalMax use 2

    To specify additional names or those longer than 35 characters in length

    Usage notes

    This segment may be used or omitted

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N2-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N3
    320

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Usage notes

    This segment may be used or omitted

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    330

    Geographic Location

    OptionalMax use >1

    To specify the geographic place of the named party

    Usage notes

    This segment may be used or omitted

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    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.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    REF
    340

    Reference Identification

    OptionalMax use 12

    To specify identifying information

    Usage notes

    This segment may be used or omitted

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    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
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    TD5
    380

    Carrier Details (Routing Sequence/Transit Time)

    OptionalMax use 12

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

    Usage notes

    This segment may be used or omitted

    Example
    If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
    TD5-01
    133
    Routing Sequence Code
    Optional

    Code describing the relationship of a carrier to a specific shipment movement

    O
    Origin Carrier (Air, Motor, or Ocean)
    Z
    Mutually Defined
    TD5-02
    66
    Identification Code Qualifier
    Optional

    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
    TD5-03
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Carrier Code

    TD5-04
    91
    Transportation Method/Type Code
    Optional

    Code specifying the method or type of transportation for the shipment

    A
    Air

    Detail

    POC Loop
    RequiredMax >1
    POC
    010

    Line Item Change

    RequiredMax use 1

    To specify changes to a line item

    Example
    If Basis of Unit Price Code (POC-07) is present, then Unit Price (POC-06) is 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
    POC-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • POC01 is the purchase order line item identification.
    Usage notes

    Line Number from Purchase Order

    POC-02
    670
    Change or Response Type Code
    Required

    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
    POC-03
    330
    Quantity Ordered
    Optional
    Min 1Max 15

    Quantity ordered

    POC-04
    671
    Quantity Left to Receive
    Optional
    Min 1Max 9

    Quantity left to receive as qualified by the unit of measure

    POC-05
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    355
    Unit or Basis for Measurement Code
    Required

    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
    POC-06
    212
    Unit Price
    Optional
    Min 1Max 15

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

    Usage notes

    Unit Price with maximum of five decimal places.

    POC-07
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item

    HP
    Price per Hundred
    PE
    Price per Each
    TP
    Price per Thousand
    POC-08
    235
    Product/Service ID Qualifier
    Optional

    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
    POC-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Part Number

    POC-10
    235
    Product/Service ID Qualifier
    Optional

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

    VP
    Vendor's (Seller's) Part Number
    POC-11
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Part Number

    REF
    100

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Usage notes

    This segment may be used or omitted

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    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
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    SCH Loop
    OptionalMax >1
    SCH
    295

    Line Item Schedule

    RequiredMax use 1

    To specify the data for scheduling a specific line-item

    Usage notes

    This segment may be used or omitted

    Example
    SCH-01
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    Usage notes

    Remaining quantity

    SCH-02
    355
    Unit or Basis for Measurement Code
    Required

    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
    SCH-05
    374
    Date/Time Qualifier
    Required

    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
    SCH-06
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Usage notes

    Delivery Date

    Summary

    CTT Loop
    OptionalMax >1
    CTT
    010

    Transaction Totals

    RequiredMax use 1

    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.
    Usage notes

    This segment may be used or omitted

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    CTT-02
    347
    Hash Total
    Optional
    Min 1Max 10

    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.

    ## Example:
    -.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.

    Usage notes

    Sum of quantities in element POC03

    SE
    030

    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
    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
    Min 4Max 9

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

    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
    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
    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
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ST*860*5850001~
    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.