Discrepancy is not Auto Closed though the 'Allow Autoclose' field was set to 'Yes' in Validation Check
(Doc ID 2494164.1)
Last updated on OCTOBER 03, 2019
Applies to:Oracle Health Sciences Data Management Workbench - Version 2.4.7 and later
Information in this document applies to any platform.
On Oracle Health Sciences Data Management Workbench (DMW) 188.8.131.52.3 version,
Validation Check was defined with 'Allow Auto Close' set to 'Yes'.
Validation Check was executed in the batch mode on the corresponding table in Production lifecycle.
This Validation Check has generated two discrepancies for two records because a column was having 'N' as a value.
That column records were updated to 'Y' in InForm.
One of the discrepancy created by the Validation Check was autoclosed in DMW.
The other discrepancy created by the Validation Check is not auto closed though the enabled flag was set in the Validation Check.
It would be expected that the discrepancy created by VC should be auto closed when the enabled flag is set to 'Yes'.
The issue can be reproduced with the following steps:
1. Create a Validation Batch Check named 'CM_01'.
2. Create a Validation Check which checks the a column to be 'Y' on a specific table in a data model.
3. Submit the VC for execution.
Since one of the record was set to 'N', a discrepancy was created.
4. Changed the data to 'Y'.
5. Check the discrepancy created at step 3.
The discrepancy is in 'Answered' state.
It would be expected that the discrepancy should be in 'Auto Close' state as the flag was set to autoclose.
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