scope:

This document contains X12 implementation guides (Type 3 Technical Reports - TR3) for Electronic Data Interchange (EDI) standards that streamline and facilitate consistent electronic interchange of business transactions within the aerospace industry. It is published by X12 in conjunction with the Aerospace Industries Association. X12 standards are developed to identify the broadest data requirements for a transaction set. Type 3 Technical Reports (TR3) define explicit data requirements for a specific business purpose. Trading partners who implement according to the instructions in this TR3 can exchange data with multiple trading partners in a consistent manner.

Edition 7 contains the following volumes:

Volume I: Aerospace Industry Invoice (810) (unique identifier code: 004010X348)

This implementation guide is designed to assist aerospace industry implementers, such as contractors and suppliers, with consistent invoice data exchange using the ASC X12 810 transaction.

Volume II: Aerospace Request For Quotation (840) (unique identifier code: 004010X354)

This TR3 defines consistent requirements for use of the X12 840 transaction set for the exchange of requests for quotations within the aerospace industry.

Volume III: Aerospace Industry Purchase Order (850) (unique identifier code: 004010X357)

This TR3 defines consistent requirements for use of the X12 850 transaction set within the aerospace industry for the exchange of purchase orders (PO). Related acknowledgments and revisions are exchanged via other X12 transaction sets and based on separate implementation instructions. This transaction set is not used to convey purchase order changes or purchase order acknowledgment information, instead, use those transactions specifically designed for that purpose.

Volume IV: Aerospace Industry Purchase Order Acknowledgment (855) (unique identifier code: 004010X358)

This TR3 defines consistent requirements for use of the X12 855 transaction set within the aerospace industry for the exchange of purchase orders (PO) acknowledgments. Related acknowledgments and revisions are exchanged via other X12 transaction sets and based on separate implementation instructions. This transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order or Planning Schedule/Release. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

Volume V: Aerospace Industry Functional Acknowledgment (997) (unique identifier code: 004010X363)

This TR3 defines the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents.The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. Related acknowledgments and revisions are exchanged via other X12 transaction sets and based on separate implementation instructions. The various levels of status (error) codes in the Functional Acknowledgment (997) show the results of the syntax check of a document by the receiver of that document. The 997 shows results at the Functional Group level via the AK9 segment; at the Transaction Set level via the AK5 segment; at the Segment level via the AK3 segment and at the Data Element level via the AK4 segment. If a Functional Group shows an Acknowledgment Code of "M", "P", "R", or "X," that Functional Group must be corrected and re-transmitted.

Volume VI: Aerospace Industry Planning Schedule with Release Capability (830) (unique identifier code: 004010X351)

This TR3 defines consistent requirements for use of the X12 830 Planning Schedule with Release Capability transaction set within the aerospace industry for the exchange of forecasting and material release information between companies. The transaction may be used as a simple forecast, a forecast that includes the buyer's authorization for the seller to commit to resources, or act as an order release mechanism.

Volume VII: Aerospace Industry Response To Request For Quote (843) (unique identifier code: 004010X355)

This TR3 defines consistent requirements for use of the X12 843 transaction set within the aerospace industry for the exchange of responses to a request for quote. Related acknowledgments and revisions are exchanged via other X12 transaction sets and based on separate implementation instructions.

Volume VIII: Aerospace Industry Purchase Order Change Buyer-Initiated (860) (unique identifier code: 004010X361)

This TR3 defines consistent requirements for use of the X12 860 transaction set within the aerospace industry for the exchange of buyer initiated purchase order change requests and buyer acknowledgment of seller initiated purchase order change requests. These instructions govern the following business activities: 1. The buyer's request to change a purchase order previously submitted using X12's 850 transaction. 2. The buyer's acceptance, rejection, or modification of purchase order changes the seller submitted separately using X12's 865 transaction. More than one 860 PO Change may be exchanged between the buyer and seller while a specific purchase order is in effect between the trade parties. The 860 transaction may update the 850 original order or changes that have been applied to the original order by successive 860 transactions. Related acknowledgments and revisions are exchanged via other X12 transaction sets and based on separate implementation instructions. This transaction set is not used to convey an initial purchase order or purchase order acknowledgment information. Refer to the transaction sets specifically designed for those purposes.

Volume IX: Aerospace Industry Purchase Order Change Acknowledgment/ Request Seller - Initiated (865)  (unique identifier code: 004010X362) - NEW!

This TR3 defines consistent requirements for use of the X12 865 transaction set within the aerospace industry for the exchange of purchase order change acknowledgment requests, seller-initiated. Related acknowledgments and revisions are exchanged via other X12 transaction sets and based on separate implementation instructions. 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.