Expected Report Did Not Schedule For a Case After Case Lock During Routing of Follow-up Data
Last updated on MARCH 30, 2017
Applies to:Oracle Argus Safety - Version 7.0.7 and later
Information in this document applies to any platform.
On Applications Oracle Argus Safety Version : 7.0.7
It was found that once case CASE_A did not schedule reports for the FU#7 dates.
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:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms