Tracking and Acknowledgement keeps track of the transmission and updates the Transmission Server queue status. At the end of an import or export task, the tracking module updates the information within the E2B table as "E2B Message Queue".
If the export request is exported and transmitted successfully, then in the table "E2B Message Queue", the field "Status" is updated stating that the AER is exported and transmitted successfully. The column "Status last updated" is also updated to the system date (That is, the date on which the case is successfully transmitted).
Once the Authority imports the case, the message acknowledgement is sent to the sender indicating whether the case is successfully imported or not.
One of the following can occur:
If the case is imported successfully, then the message and report acknowledgement is generated.
If any errors are encountered at the time of importing, then the message acknowledgement and report acknowledgement are generated providing details of the errors encountered when importing the specific AER.
If the error occurs while importing multiple AERs, multiple report acknowledgements are generated.
Note: There can be multiple report Acknowledgements generated for a message acknowledgement.
If the acknowledgement indicates that the recipient did not properly import the exported AERs, the Web-UI client sends an e-mail to the ARISg user who actually distributed the case.
Once the Export or Import process is completed successfully, then the entry from the queue and the intermediate table is removed. In case of export, the transmission is successful when you receive an the acknowledgement from the receiver. In case of import, the transmission is successful when the acknowledgement for the successful import is sent to the sender. The message 'Successfully placed request for import is displayed'.
When the ESM Server receives an acknowledgment, the data available in the <parsingerrormessage> and <errormessagecomment> tags are imported into the corresponding columns in the acknowledgment tables.
The data size of E2B_MESSAGE_ACK.PARSING_ERROR_MESSAGE and E2B_REPORT_ACK.ERROR_MESSAGE_COMMENT is up to 2000 characters. If the value exceeds 2000 characters, the data is truncated and populated into the respective columns.
When the ESMServer is generating the acknowledgment for the Imported E2B ICSR Files, the <parsingerrormessage> and <errormessagecomment> are truncated to 250 characters to adhere to the ICH standards.
Message acknowledgement indicates if the SGML/XML file contained any errors and if it is able to extract the transmitted data.
The acknowledgment notifies the sender about any one of the following:
Parsing is successful and all ICSRs could be loaded into the target database.
Parsing is successful but not all ICSRs could be loaded into the target database.
The SGML / XML file failed validation by an SGML / XML parser.
To help in tracking and identifying the transmission, this section includes the following:
Sender defined ICH ICSR message number
Local message number
Identifier of sender and receiver
Message sent date
Acknowledgment received date
Description of the transaction
Report Acknowledgment provides information on the actual errors encountered while loading the data into the relevant tables. This is a repeatable section in the ICSR acknowledgement file, as there can be multiple records for each message number.
This section includes the following:
The safety record ID (AER_NO)
Report version number
Local report number
Authority number
Company case report number
Other sender's case report number
Data of receipt of most recent information for this report
Description of the transaction/error
Note: ESM Server accepts acknowledgement files with .sgml/.xml extension.
A sample of the Acknowledgement Details page is shown below:
Acknowledgment Details Page