Discrepancy Is In Cancelled State When It Was Expected To Be In Closed State
(Doc ID 2814841.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Data Management Workbench - Version 2.4.8.4 and laterInformation in this document applies to any platform.
Symptoms
A Discrepancy raised by a validation check went into Cancelled state when it was expected to be closed.
Changes
When looking at the history of the discrepancy, it started out as candidate and was then opened. The data was then changed in InForm which auto answered the query. After a data load ran, it went into candidate state again. This time it wasn't answered and when there was a data change in InForm, the discrepancy was cancelled.
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! |