Is it Possible to Disable ACK Timeout Warnings for Specific Agency/Reports ?
(Doc ID 2560331.1)
Last updated on JUNE 15, 2021
Applies to:
Oracle Argus Interchange - Version 8.1.2 and laterInformation in this document applies to any platform.
Goal
Oracle Argus Safety Version 8.1.2
An E2B report is sent to a Health Authority. A few hours after sending this initial report, further information is received for the case which requires a followup E2B.
After waiting 2 days, there is still no ACK returned from the initial report.
Because the clock is running and there are only 5 days to submit, the decision was taken to update the initial report status as submitted because it is not possible to submit the Followup without having the previous report acknowledged.
The followup E2B was submitted successfully.
However, one day later, warning/notification messages are received from the Argus Interchange service concerning the initial report (Note: The ACK timeout is set to 72 hours).
Below is an example:
email@emailaddress
Today, 2:01 AM
This mail has been sent by the system to notify that the following reports are waiting for acknowledgement
Transmit Date(GMT): [5/10/2019 3:46:49 PM]
Message Number : [######]
Receiver : [UNITED KINGDOM (RECEIVER)]
AE Case Number : [######]
E2B Company Number: [SAMPLE-COMPANY-#####]
Thanks,
ESM Service
In previous versions of Argus, if the report is marked as submitted (cmn_reg_reports.date_submitted is not null) there was no error message.
In Argus Safety 8.1.2, the system does not mark the report as being "manually" acknowledged. Updating cmn_reg_reports.date_submitted does not update MESSAGES and SAFETYREPORT which are still at status 17 (pending ACK).
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| 5.1.10 What do the bug status numbers mean? |
| References |