Product: X12 EDI
Transaction: 999
Article Link: http://help.truecommerce.com/en/articles/10155069-x12-999-implementation-acknowledgement
999 - Implementation Acknowledgment
FUNCTIONAL GROUP=FA
This X12 Transaction Set contains the format and establishes the data contents of the Implementation Acknowledgment Transaction Set (999) 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 and relational analysis of the electronically encoded documents, based upon a full or implemented subset of X12 transaction sets. 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 | Required |
ST | Transaction Set Header | M |
AK1 | Functional Group Response Header | M |
AK2
Segment | Name | Required |
AK2 | Transaction Set Response Header | O |
IK3
Segment | Name | Required |
IK3 | Implementation Data Segment Note | O |
CTX | Context | O |
IK4
Segment | Name | Required |
IK4 | Implementation Data Element Note | M |
IK5
Segment | Name | Required |
IK5 | Implementation Transaction Set Response Trailer | M |
AK9
Segment | Name | Required |
AK9 | Functional Group Response Trailer | M |
SE | Transaction Set Trailer | M |
COMMENTS
Notes |
|
1/0100 | Neither the 997 nor the 999 Acknowledgment shall be acknowledged, thereby preventing an endless cycle of acknowledgments of acknowledgments. Nor shall a Implementation Acknowledgment be sent to report errors in a previous Implementation Acknowledgment. |
1/0100 | There is only one Implementation 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 Implementation 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 Implementation 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. |
1/0700 | The CTX Segment shall be used to disambiguate a reported error that is dependent on context. |
1/0800 | If any implementation guide errors have been reported in IK3 or IK4, then code I5 shall be reported in the IK5 Segment. |
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 as expressed in compliant implementation guides. 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