X12 865 Purchase Order Change Acknowledgment/Request - Seller Initiated
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Acknowledgment/Request - Seller Initiated Transaction Set (865) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to convey acceptance or rejection of changes to a previously submitted purchase order by the seller or to notify the buyer of changes initiated by the seller to a previously submitted purchase order by the seller.
- ~ 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
- CA
- Purchase Order Change Acknowledgment/Request - Seller Initiated (865)
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).
- 865
- Purchase Order Change Acknowledgment/Request - Seller Initiated
Beginning Segment for Purchase Order Change Acknowledgment
To indicate the beginning of the Purchase Order Change Acknowledgment Transaction Set and transmit identifying numbers and dates
Code identifying purpose of transaction set
- 01
- Cancellation
- 04
- Change
- 06
- Confirmation
Code specifying the type of acknowledgment
- AC
- Acknowledge - With Detail and Change
- AT
- Accepted
- RD
- Reject with Detail
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD
- BCA06 is the date assigned by the purchaser to purchase order.
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)
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
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.
Should be the O’Reilly Store Number.
Name
To identify a party by type of organization, name, and code
Detail
Line Item Change
To specify changes to a line item
Code specifying the type of change to the line item
- CA
- Changes To Line Items
- NC
- Concurrent Item (No Change)
- QD
- Quantity Decrease
- QI
- Quantity Increase
Quantity left to receive as qualified by the unit of measure
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
Identifying number for a product or service
Should be the buyer’s part number as provided on the original purchase order.
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
Should be the vendor’s part number as provided on the original purchase order (if it was provided).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO
- Purchase Order Number
Item Identification
To specify basic item identification data
This segment is required if the original item number has been replaced or a substitution was made.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- RR
- Replacement Product Number
Pricing Information
To specify pricing information
This segment is required if the original item number has been replaced or a substitution was made.
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Should be the price of the replacement item.
Date/Time Reference
To specify pertinent dates and times
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a specific line item
Code specifying the action taken by the seller on a line item requested by the buyer
If the item was rejected and the reason for rejection is not listed above, ACK 01 should be “IR”. If “IR” is provided, the MSG segment is required with a description of why the item was rejected.
- AR
- Item Accepted and Released for Shipment
- BP
- Item Accepted - Partial Shipment, Balance Backordered
If this code is provided, the following DTM segment is mandatory.
- IA
- Item Accepted
- IB
- Item Backordered
If this code is provided, the following DTM segment is mandatory.
- IR
- Item Rejected
- IS
- Item Accepted - Substitution Made
- R1
- Item Rejected, Not a Contract Item
- R2
- Item Rejected, Invalid Item Product Number
- R3
- Item Rejected, Invalid Unit of Issue
- R4
- Item Rejected, Contract Item not Available
- SP
- Item Accepted - Schedule Date Pending
Date/Time Reference
To specify pertinent dates and times
This segment is required if the item has been partially or fully back ordered.
Message Text
To provide a free-form format that allows the transmission of text information
This segment is required if the item was rejected but a corresponding reason code was not found in ACK 01.
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
Accepted Order
GS*CA*SENDERGS*RECEIVERGS*20231120*040407*000000001*X*004010~
ST*865*8650002~
BCA*06*AT*888888S04444***20150601*******OS~
SE*3*8650002~
GE*1*000000001~
IEA*1*000000001~
Back Ordered Item
GS*CA*SENDERGS*RECEIVERGS*20231120*040414*000000001*X*004010~
ST*865*8650001~
BCA*04*AC*992097S02068***20150601*******OS~
N1*SU*Supplier Name~
N1*BY* OReilly 2068~
POC**CA*1*0*EA***BP*A12345*VP*A-12345*PO*992097S02068~
DTM*004*20150601~
ACK*IB~
DTM*169*20150701~
CTT*1~
SE*10*8650001~
GE*1*000000001~
IEA*1*000000001~
Cancelled Item
GS*CA*SENDERGS*RECEIVERGS*20231120*040429*000000001*X*004010~
ST*865*8650003~
BCA*01*AC*991825S02201***20150601*******OS~
N1*SU*Supplier Name~
N1*BY* OReilly 2201~
POC**CA*1*0*EA***BP*662593A*VP*662593-A*PO*991825S02201~
DTM*004*20150601~
ACK*IR~
MSG*MUST BE ORDERED AS A PAIR~
CTT*1~
SE*10*8650003~
GE*1*000000001~
IEA*1*000000001~
Multiple Items
GS*CA*SENDERGS*RECEIVERGS*20231120*040436*000000001*X*004010~
ST*865*8650003~
BCA*04*AC*777777S03334***20150101*******OS~
N1*SU*Supplier·Name~
N1*BY*·OReilly···3334~
POC**CA*1*1*EA***BP*123456***PO*777777S03334~
LIN**RR*654321~
CTP***999.99~
DTM*004*20150101~
ACK*IS~
POC**NC*1*1*EA***BP*6565***PO*777777S03334~
DTM*004*20150101~
ACK*IA~
CTT*2~
SE*14*8650003~
GE*1*000000001~
IEA*1*000000001~
Replacement/Substituted Item
GS*CA*SENDERGS*RECEIVERGS*20231120*040442*000000001*X*004010~
ST*865*8650002~
BCA*04*AC*991545S00930***20150601*******OS~
N1*SU*Supplier Name~
N1*BY* OReilly 930*94*930~
POC**CA*1*1*EA***BP*DW551*VP*DW-551*PO*99145S00930~
LIN**RR*DW-551-1~
CTP***99.99~
DTM*004*20150601~
ACK*IS~
CTT*1~
SE*11*8650002~
GE*1*000000001~
IEA*1*000000001~
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.