0% found this document useful (0 votes)
11 views10 pages

865 Purchase Order Change Acknowledgment/Request - Seller Initiated CA

The document outlines the Draft Standard for Trial Use of the Purchase Order Change Acknowledgment/Request - Seller Initiated Transaction Set (865) for EDI environments. It specifies the format and data contents necessary for sellers to acknowledge or request changes to previously submitted purchase orders. Key segments include transaction set headers, line item changes, acknowledgments, and transaction totals.

Uploaded by

ashik.sociusus
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views10 pages

865 Purchase Order Change Acknowledgment/Request - Seller Initiated CA

The document outlines the Draft Standard for Trial Use of the Purchase Order Change Acknowledgment/Request - Seller Initiated Transaction Set (865) for EDI environments. It specifies the format and data contents necessary for sellers to acknowledge or request changes to previously submitted purchase orders. Key segments include transaction set headers, line item changes, acknowledgments, and transaction totals.

Uploaded by

ashik.sociusus
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

865 Purchase Order Change

Acknowledgment/Request - Seller Initiated

Functional Group ID= CA


Introduction:

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.

Heading:
Pos. Seg. Req. Loop
No. ID Name Des. Max.Use Repeat
M 010 ST Transaction Set Header M 1
M 020 BCA Beginning Segment for Purchase Order M 1
Change Acknowledgment
LOOP ID - N1 200
300 N1 Name O 1

Detail:
Pos. Seg. Req. Loop
No. ID Name Des. Max.Use Repeat
LOOP ID - POC >1
Must Use 010 POC Line Item Change O 1
LOOP ID - ACK 104
Must Use 270 ACK Line Item Acknowledgment O 1
Must Use 280 DTM Date/Time Reference O 1

Summary:
Pos. Seg. Req. Loop
No. ID Name Des. Max.Use Repeat
LOOP ID - CTT 1
Must Use 010 CTT Transaction Totals O 1

M 030 SE Transaction Set Trailer M 1

8654010V2 (004010) 1 November 19, 2021


Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Business Rules: Variable Name: STST

Data Element Summary


Ref. Data
Des. Element Name Attributes
M ST01 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
865 Purchase Order Change Acknowledgment/Request -
Seller Initiated
M ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

8654010V2 (004010) 2 November 19, 2021


Segment: BCA Beginning Segment for Purchase Order Change Acknowledgment
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the Purchase Order Change Acknowledgment
Transaction Set and transmit identifying numbers and dates

Data Element Summary


Ref. Data
Des. Element Name Attributes
M BCA01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set
00 Original
>> BCA02 587 Acknowledgment Type O ID 2/2
Code specifying the type of acknowledgment
AC Acknowledge - With Detail and Change
AD Acknowledge - With Detail, No Change
RD Reject with Detail
M BCA03 324 Purchase Order Number M AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
M BCA06 373 Date M DT 8/8
Date expressed as CCYYMMDD
BCA07 326 Request Reference Number O AN 1/45
Reference number or RFQ number to use to identify a particular
transaction set and query (additional reference number or description
which can be used with contract number)

8654010V2 (004010) 3 November 19, 2021


Segment: N1 Name
Position: 300
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code

Data Element Summary


Ref. Data
Des. Element Name Attributes
M N101 98 Entity Identifier Code M ID 2/3
Code identifying an organizational entity, a physical location, property or
an individual
BT Bill-to-Party
BY Buying Party (Purchaser)
SE Selling Party
ST Ship To
N102 93 Name X AN 1/60
Free-form name
N103 66 Identification Code Qualifier X ID 1/2
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
N104 67 Identification Code X AN 2/80
Code identifying a party or other code

8654010V2 (004010) 4 November 19, 2021


Segment: POC Line Item Change
Position: 010
Loop: POC Optional (Must Use)
Level: Detail
Usage: Optional (Must Use)
Max Use: 1
Purpose: To specify changes to a line item

Data Element Summary


Ref. Data
Des. Element Name Attributes
>> POC01 350 Assigned Identification O AN 1/20
Alphanumeric characters assigned for differentiation within a transaction
set
M POC02 670 Change or Response Type Code M ID 2/2
Code specifying the type of change to the line item
CA Changes To Line Items
PQ Unit Price/Quantity Change
PR Unit Price/Reschedule Change
RC Reject Item Change
>> POC03 330 Quantity Ordered O R 1/15
Quantity ordered
>> POC04 671 Quantity Left to Receive X R 1/9
Quantity left to receive as qualified by the unit of measure
>> POC05 C001 Composite Unit of Measure X
To identify a composite unit of measure (See Figures Appendix for
examples of use)
M C00101 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner
in which a measurement has been taken
EA Each
POC06 212 Unit Price X R 1/17
Price per unit of product, service, commodity, etc.
POC07 639 Basis of Unit Price Code O ID 2/2
Code identifying the type of unit price for an item
>> POC08 235 Product/Service ID Qualifier X ID 2/2
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
>> POC09 234 Product/Service ID X AN 1/48

8654010V2 (004010) 5 November 19, 2021


Identifying number for a product or service
>> POC10 235 Product/Service ID Qualifier X ID 2/2
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
>> POC11 234 Product/Service ID X AN 1/48
Identifying number for a product or service

8654010V2 (004010) 6 November 19, 2021


Segment: ACK Line Item Acknowledgment
Position: 270
Loop: ACK Optional (Must Use)
Level: Detail
Usage: Optional (Must Use)
Max Use: 1
Purpose: To acknowledge the ordered quantities and specify the ready date for a specific line
item

Data Element Summary


Ref. Data
Des. Element Name Attributes
M ACK01 668 Line Item Status Code M ID 2/2
Code specifying the action taken by the seller on a line item requested by
the buyer
DR Item Accepted - Date Rescheduled
IA Item Accepted
IB Item Backordered
IP Item Accepted - Price Changed
IQ Item Accepted - Quantity Changed
IR Item Rejected
SP Item Accepted - Schedule Date Pending
>> ACK02 380 Quantity X R 1/15
Numeric value of quantity
>> ACK03 355 Unit or Basis for Measurement Code X ID 2/2
Code specifying the units in which a value is being expressed, or manner
in which a measurement has been taken
EA Each
>> ACK04 374 Date/Time Qualifier O ID 3/3
Code specifying type of date or time, or both date and time
068 Current Schedule Ship
>> ACK05 373 Date X DT 8/8
Date expressed as CCYYMMDD

8654010V2 (004010) 7 November 19, 2021


Segment: DTM Date/Time Reference
Position: 280
Loop: ACK Optional (Must Use)
Level: Detail
Usage: Optional (Must Use)
Max Use: 1
Purpose: To specify pertinent dates and times

Data Element Summary


Ref. Data
Des. Element Name Attributes
M DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time
010 Requested Ship
>> DTM02 373 Date X DT 8/8
Date expressed as CCYYMMDD

8654010V2 (004010) 8 November 19, 2021


Segment: CTT Transaction Totals
Position: 010
Loop: CTT Optional (Must Use)
Level: Summary
Usage: Optional (Must Use)
Max Use: 1
Purpose: To transmit a hash total for a specific element in the transaction set

Data Element Summary


Ref. Data
Des. Element Name Attributes
M CTT01 354 Number of Line Items M N0 1/6
Total number of line items in the transaction set

8654010V2 (004010) 9 November 19, 2021


Segment: SE Transaction Set Trailer
Position: 030
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments)

Data Element Summary


Ref. Data
Des. Element Name Attributes
M SE01 96 Number of Included Segments M N0 1/10
Total number of segments included in a transaction set including ST and
SE segments
M SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

8654010V2 (004010) 10 November 19, 2021

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy