E2B Report Generates With the Wrong Data
(Doc ID 2729972.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.1.2 and laterOracle Life Sciences Argus Safety Cloud Service - Version 8.1.2 and later
Information in this document applies to any platform.
Symptoms
Case has all required data to pass E2B validation
Run Draft E2B and get Validation errors
Steps to reproduce the issue:
1. Create a new case that would cause the Validation error. (Initial Receipt Date: 11-OCT-2020)
2. Lock the case.
3. Add Significant Follow-up
4. Lock the Case.
5. Scheduled Report (This sets the Aware Date: 14-OCT-2020)
6. The Aware Date in the CMN_REG_REPORTS table shows 14-OCT-2020
7. Click on Draft link and get the Validation error, since the Validation issues still exist
2. Lock the case.
3. Add Significant Follow-up
4. Lock the Case.
5. Scheduled Report (This sets the Aware Date: 14-OCT-2020)
6. The Aware Date in the CMN_REG_REPORTS table shows 14-OCT-2020
7. Click on Draft link and get the Validation error, since the Validation issues still exist
8. Add another Significant Follow up: 15-OCT-2020
9. Correct the Validation errors
10. Saved and lock the case
11. The Aware Date in the CMN_REG_REPORTS table still shows 14-OCT-2020
12. Click on Draft link and get the Validation error (Not expected, since the expected data has been entered)
9. Correct the Validation errors
10. Saved and lock the case
11. The Aware Date in the CMN_REG_REPORTS table still shows 14-OCT-2020
12. Click on Draft link and get the Validation error (Not expected, since the expected data has been entered)
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 |