Discrepancies Created through Validation Checks are not Processed to External System
(Doc ID 2389702.1)
Last updated on APRIL 23, 2018
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) 126.96.36.199 version,
A Generic Connector has been defined by following the steps from <Note.2172786.1>.
When trying to create discrepancies through Validation Checks for a Rave external system,
at DMW level the discrepancies are getting created, but they are not getting processed.
The tag 'Processing for Rave' is applied after VC installation.
The problem seems to be before starting of processing the discrepancy to external system
because the 'SendtoRave' tag is not applied. There are no messages generated in the defined
adapter for Medidata Rave.
It would be expected that the discrepancies created through Validation Checks should be
processed to External System (Rave).
The issue can be reproduced with the following steps:
1. Create and install the adapter to external system by following the steps from Doc ID 2172786.1
2. Create a validation batch and check on the existing successful installed and already loaded data model.
3. Run the validation check.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!