Product: X12 EDI
Transaction: 997
997 - Functional Acknowledgment
FUNCTIONAL GROUP=FA
This X12 Transaction Set 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.
SCHEMA
ST
Segment | Name | Position |
ST | 0100 | |
AK1 | Functional Group Response Header | 0200 |
AK2
Segment | Name | Position |
AK2 | Transaction Set Response Header | 0300 |
AK3
Segment | Name | Position |
AK3 | Data Segment Note | 0400 |
AK4 | Data Element Note | 0500 |
AK5
Segment | Name | Position |
AK5 | Transaction Set Response Trailer | 0600 |
AK9
Segment | Name | Required |
AK9 | Functional Group Response Trailer | 0700 |
SE | Transaction Set Trailer | 0800 |
Comments
Notes |
|
1/0100 | 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. |
1/0100 | There is only one Functional Acknowledgment Transaction Set per acknowledged functional group. |
1/0100 | Only one acknowledgement, either a single Transaction Set 997 or a single Transaction Set 999, should be generated for a functional group unless mutually agreed upon. |
1/0200 | AK1 is used to respond to the functional group header and to start the acknowledgment for a functional group. There shall be one AK1 segment for the functional group that is being acknowledged. |
1/0200 | The Functional Acknowledgement is generated at the point of translation, intended for the originator (not any intermediate parties). |
1/0200 | 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. |
1/0300 | AK2 is used to start the acknowledgment 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. |
Comments |
|
1/0400 | The data segments of this standard are used to report the results of the syntactical analysis of the functional groups of transaction sets; they report the extent to which the syntax complies with the standards or proper subsets of transaction sets and functional groups. They do not report on the semantic meaning of the transaction sets (for example, on the ability of the receiver to comply with the request of the sender). |
rev 11/19/2024