Follow-up Case Information Sets a Transmitted Report To 'New Data Available' State Instead of Scheduling a New Follow-up
(Doc ID 2731018.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.2.1 and laterInformation in this document applies to any platform.
Symptoms
Intermittently the Follow-up case information sets a previously transmitted report to 'New Data Available' state instead of Scheduling a new Follow-up Report.
As long as no manually scheduled report exists, Argus will correctly schedule a new follow-up report if the previous report is pending, but already transmitted.
However, if one of the previous reports (not necessarily the most recent) has been manually scheduled, Argus incorrectly regenerates the most recent report if this is already transmitted, but not yet submitted.
This regenerated report appear in bulk reporting under scheduled/generated as 'New Data Available'
Steps to Reproduce:
2. Significant Follow-up received
3. Follow-up manually generated and transmitted (pending submission date)
4. Further Significant Follow-up received for Follow-up #2
5. Significant Follow-up #3 received
5. FU#2 was regenerated despite already being transmitted (but not submitted)
So in terms of the data in the cmn_reg_reports we can see for this Follow-up (example dates only):
Scheduled on 30th September 2020 @21:19
Generated on 05 October 2020 @21:25:15 <== So, date generated is After Transmission
Transmitted on 01-October-2020 @12:50:56 Actual Transmission 01.Oct.2020 12:54:12
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |