Electronic Data Interchange
Construction of Implementation Acknowledgment (ASC/X12)

The following table shows what reporting level is created in the acknowledgment at the same time a level has been referenced in the subject document.

The implementation acknowledgment reports errors from a functional group, so verification begins with the functional group header (GS) and ends with the functional group trailer (GE).  For each functional group encountered in a subject document, FREDI builds an implementation acknowledgment document as defined by the Implementation Acknowledgment (999) transaction set.  The diagram below shows the resulting implementation acknowledgment structure created from a subject document containing 2 functional groups.  It also shows the corresponding data segment created in the implementation acknowledgment as data segments are encountered in the subject document.

The implementation acknowledgment is constructed as follows:

1. ISA.  The Interchange Control Header (ISA) is automatically generated when the first interchange header in the subject document is encountered during verification.  See Auto-Create of Interchange Control Header (ISA).

2. GS.  The Functional Group Header (GS) is automatically generated when the first functional group in the subject document is encountered.  See Auto-Create of Functional Group Header (GS).

3. ST.  A transaction set is created for every functional group encountered in the subject interchange.  The transaction set is always started with a Transaction Set Header (ST) control segment and is created as follows for the implementation acknowledgment:

   POSITION	ELEMENT ID	DESCRIPTION	CONSTRUCT INFO
   01	143	Transaction Set Identifier Code	The implementation acknowledgment transaction set identifier "999" is assigned to this data element.
   02	329	Transaction Set Control Number	The control number is the current count of the transaction sets created within the functional group, padded to the left with zeros to satisfy the minimum length requirement.  The first transaction set has a control number of 1. The value here is saved to be later stored in the Transaction Set Trailer (SE) data element 329 when the transaction set is closed.
   03	1705	Implementation Convention Reference	Not created.




4. AK1.  Auto-Create Functional Group Response Header (AK1).
   

5. AK2.  Auto-Create Transaction Set Response Header (AK2).

 

6. IK3.  Auto-Create Implementation Data Segment Note (IK3).
   

7. IK4.  Auto-Create Implementation Data Element Note (IK4).
   

8. IK5.  An Implementation Transaction Set Response Trailer (IK5) is created when the Transaction Set Trailer (SE) is encountered in the subject document.
   

   POSITION	ELEMENT ID	DESCRIPTION	CONSTRUCT INFO
   01	717	Transaction Set Acknowledgment Code	See Accepting or Rejecting a Transaction Set for implementation acknowledgment.
   02	618	Implementation Transaction Set Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   03	618	Implementation Transaction Set Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   04	618	Implementation Transaction Set Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   05	618	Implementation Transaction Set Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   06	618	Implementation Transaction Set Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.




9. AK9.  A Functional Group Response Trailer (AK9) is created the Functional Group Trailer (GE) is encountered in the subject document.
   

   POSITION	ELEMENT ID	DESCRIPTION	CONSTRUCT INFO
   01	715	Functional Group Acknowledge Code	See Accepting or Rejecting a Functional Group for implementation acknowledgment.
   02	97	Number of Transaction Sets Included	The total number of transaction sets specified by the functional group that this AK9 is reporting for.
   03	123	Number of Received Transaction Sets	The total number of transaction sets that was actually verified in the functional group that this AK9 is reporting for.
   04	2	Number of Accepted Transaction Sets	The total number of transaction sets that were accepted by the recipient.
   05	716	Functional Group Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   06	716	Functional Group Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   07	716	Functional Group Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   08	716	Functional Group Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.
   09	716	Functional Group Syntax Error Code	A syntax error code determined from a syntax error discovered by FREDI is stored in this data element.




10. SE.  A Transaction Set Trailer (SE) is created 
    

    POSITION	ELEMENT ID	DESCRIPTION	CONSTRUCT INFO
    01	96	Number of Included Segments	The total number of data segments in the transaction set.  This total includes the Transaction Set Header and Trailer (ST/SE).
    02	329	Transaction Set Control Number	The same control number that was assigned to the Transaction Set Header (ST) is also assigned here.




11. GE.  The Functional Group Trailer (GE) is created when the Interchange Control Trailer (IEA) has been encountered which indicates that the end of the subject interchange has been reached.  See Auto-Create of Functional Group Trailer (GE).




12. IEA.  The Interchange Trailer (IEA) is created immediately after the Functional Group Trailer (GE) has been created.  See Auto-Create of Interchange Control Trailer (IEA).

See Also:

• Implementation Acknowledgment (ASC/X12)