997
	Functional Acknowledgment
	Functional Group=FA
This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define 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. This standard does not cover the semantic meaning of the information encoded in the transaction sets.       Heading:   Pos Id Segment Name Req Max Use Repeat Notes Usage                                           010 ST Transaction Set Header M 1 N1/010 Must use   020 AK1 Functional Group Response Header M 1 N1/020 Must use Loop ID - AK2 999999           030 AK2 Transaction Set Response Header O 1 N1/030 Used       Loop ID - AK3 999999               040 AK3 Data Segment Note O 1   Used             050 AK4 Data Element Note O 99   Used             060 AK5 Transaction Set Response Trailer M 1   Must use         070 AK9 Functional Group Response Trailer M 1   Must use   080 SE Transaction Set Trailer M 1   Must use

Notes:

1/010	These acknowledgments shall not be acknowledged, thereby preventing an endless cycle of acknowledgments of acknowledgments. Nor shall a Functional Acknowledgment be sent to report errors in a previous Functional Acknowledgment. The Functional Group Header Segment (GS) is used to start the envelope for the Functional Acknowledgment Transaction Sets. In preparing the functional group of acknowledgments, the application sender's code and the application receiver's code, taken from the functional group being acknowledged, are exchanged; therefore, one acknowledgment functional group responds to only those functional groups from one application receiver's code to one application sender's code. There is only one Functional Acknowledgment Transaction Set per acknowledged functional group.
1/020	AK1 is used to respond to the functional group header and to start the acknowledgement for a functional group. There shall be one AK1 segment for the functional group that is being acknowledged.
1/030	AK2 is used to start the acknowledgement of a transaction set within the received functional group. The AK2 segments shall appear in the same order as the transaction sets in the functional group that has been received and is being acknowledged.