ECIA
/
Purchase Order Change Acknowledgment/Request - Seller Initiated
  • Specification
  • EDI Inspector
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 865 Purchase Order Change Acknowledgment/Request - Seller Initiated

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ecia/purchase-order-change-acknowledgmentrequest-seller-initiated/01H25WNQH12KDDGGYXHMPAZE0V
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
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
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

CA
Purchase Order Change Acknowledgment/Request - Seller Initiated (865)
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).
865
Purchase Order Change Acknowledgment/Request - Seller 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

BCA
020
Heading > BCA

Beginning Segment for Purchase Order Change Acknowledgment

RequiredMax use 1

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

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

Code identifying purpose of transaction set

00
Original
01
Cancellation
04
Change
19
Seller initiated change
BCA-02
587
Acknowledgment Type
Required
Identifier (ID)

Code specifying the type of acknowledgment

AC
Acknowledge - With Detail and Change
AD
Acknowledge - With Detail, No Change
AE
Acknowledge - With Exception Detail Only
AH
Acknowledge - Hold Status
AK
Acknowledge - No Detail or Change
AT
Accepted
RD
Reject with Detail
RF
Reject with Exception Detail Only
RJ
Rejected - No Detail
ZZ
Mutually Defined
BCA-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

BCA-05
327
Change Order Sequence Number
Optional
String (AN)
Min 1Max 8

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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

Purchase Order Date

BCA-09
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

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

Supplier’s Sales Order Number

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCA10 is the date assigned by the sender to the acknowledgment.
Usage notes

Acknowledgment Date

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 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
String (AN)
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
Identifier (ID)

Code specifying the type of change to the line item

AI
Add Additional Item(s)
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
RC
Reject Item Change
RS
Reschedule
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
RequiredMax 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
Required
Identifier (ID)

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
Decimal number (R)
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
Identifier (ID)

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
Identifier (ID)

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

BP
Buyer's Part Number
POC-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Customer’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)

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

Identifying number for a product or service

Usage notes

Vendor’s Part Number

ACK Loop
OptionalMax >1
ACK
270
Detail > POC Loop > ACK Loop > ACK

Line Item Acknowledgment

RequiredMax use 1

To acknowledge the ordered quantities and specify the ready date for a specific line item

Example
If either Quantity (ACK-02) or Unit or Basis for Measurement Code (ACK-03) is present, then the other is required
If Date/Time Qualifier (ACK-04) is present, then Date (ACK-05) is required
ACK-01
668
Line Item Status Code
Required
Identifier (ID)

Code specifying the action taken by the seller on a line item requested by the buyer

AC
Item Accepted and Shipped
AR
Item Accepted and Released for Shipment
BP
Item Accepted - Partial Shipment, Balance Backordered
DR
Item Accepted - Date Rescheduled
IA
Item Accepted
IB
Item Backordered
IC
Item Accepted - Changes Made
ID
Item Deleted
IH
Item on Hold
IP
Item Accepted - Price Changed
IQ
Item Accepted - Quantity Changed
IR
Item Rejected
IS
Item Accepted - Substitution Made
R2
Item Rejected, Invalid Item Product Number
R7
Item Rejected, Reorder Item as a Drop Shipment
SP
Item Accepted - Schedule Date Pending
ACK-02
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

ACK-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

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
ACK-04
374
Date/Time Qualifier
Optional
Identifier (ID)

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

017
Estimated Delivery
067
Current Schedule Delivery
068
Current Schedule Ship
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Delivery Date

DTM
280
Detail > POC Loop > ACK Loop > DTM

Date/Time Reference

OptionalMax use 1

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

002
Delivery Requested
071
Requested for Delivery (After and Including)
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Requested delivery date

ACK Loop end
POC Loop end
Detail end

Summary

CTT Loop
OptionalMax >1
CTT
010
Summary > CTT Loop > CTT

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.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

CTT-02
347
Hash Total
Optional
Decimal number (R)
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

CTT Loop end
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

EDI Samples

Sample

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231102*0329*U*00401*000000001*0*T*>
GS*CA*SENDERGS*RECEIVERGS*20231102*032949*000000001*X*004010
ST*865*0001
BCA*00*AD*H0501234567**00000001*20061027***12345*20061030
POC*4*RS*5000*5000*EA*.123*PE*BP*126ABC-D1109Z*VP*126ABC-D1109Z
ACK*IA*5000*EA*067*20061030
DTM*002*20061030
CTT*1*5000
SE*7*0001
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.