Expected Report Did Not Schedule For a Case After Case Lock During Routing of Follow-up Data
(Doc ID 2243145.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 7.0.7 and laterInformation in this document applies to any platform.
Symptoms
On Applications Oracle Life Sciences Argus Safety Version : 7.0.7
It was found that case 'CASE_A' did not schedule reports for the Follow Up #7 dates once.
It was noted that routing for the case lock was missing.
The case was reopened and resent again to distribution and the reports generated.
After further examination of the CMN_ERROR_LOG it was noted that during the routing and subsequent lock for the case, the below error was encountered:
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 |