E2B R3 Follow-up Scheduled Instead of Amendment
(Doc ID 2863907.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.2.1 and laterInformation in this document applies to any platform.
Symptoms
When processing a follow-up for a case which is marked an amendment at the same time an additional follow-up (ie. Non-Significant F/U), a Follow Up report is scheduled instead of an Amendment Report.
STEPS
- Book in a case and schedule an Initial E2B Report.
- Set the report to submitted
- Route the case and add a significant follow-up. NOTE: Flag this as Amendment
- Verify that an Amendment report is scheduled
- Route the case add a significant follow-up
- Verify that a follow-up report is scheduled as F/U#1- EXPECTED BEHAVIOR
- Route the case and add a significant follow-up. NOTE: Flag this as Amendment
- WITHOUT routing, add an additional NON-SIGNIFICANT follow-up
- Route the case and observe that instead of an Amendment report to F/U#1, a normal follow-up is scheduled (FU#2).
This results in an incorrect XML file as the new report to the R3 recipient does not indicate that this report is an amendment.
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 |
Cause |
Solution |
References |