My Oracle Support Banner

'PendingforEDC' Tag Removal Only Occurs When Data Is Refreshed (Doc ID 2742596.1)

Last updated on JANUARY 19, 2021

Applies to:

Oracle Health Sciences Data Management Workbench - Version 2.5.3 and later
Information in this document applies to any platform.

Symptoms

A scenario was reported where discrepancies were created on the source datamodel that went to 'PendingtoEDC' tag.  The tag only got removed when the data was corrected or config was corrected and data was pushed and records got refreshed.

Expected DMW Flow:
1.Load data into DMW from Rave
2.Update data in Rave
3.Raise discrepancy in datapoint corrected in Rave
4.Status goes to 'PendingtoEDC' status and manage discrepancy in disabled
5.Load the corrected data from Rave to DMW , the tag goes to Null and can be reused.

Actual Flow:
1.Load data into DMW from Rave
2.Update data in Rave
3.Raise discrepancy in datapoint corrected in Rave
4.Status goes to 'PendingtoEDC' status and manage discrepancy in disabled
5.Load the corrected data from Rave to DMW , the tag is still 'PendingtoEDC'
status and manage discrepancy is disabled.

Changes

 

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.