Manually Rejected Case has Errors Log Detail Appended to Rejection Comments - Is this Correct ?
(Doc ID 2788514.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 8.1.2 and laterInformation in this document applies to any platform.
Goal
User received two cases from a third party and rejected them manually by entering rejection comments.
The Actual ACK that was sent back to the third party had the manual rejection comment entered by user and error logs separated by semi colon.
Sample extract from the Ack File 1 without comment:
Imported Case #: XXXX, E2B rejected as will attach follow up manually Case # XXXX ;
Value for SOURCE_ID not found in table LM_CAUSALITY_SOURCE for DTD element DRUGASSESSMENTSOURCE value - Reporter ; Value for SOURCE_ID not found in table
Value for SOURCE_ID not found in table LM_CAUSALITY_SOURCE for DTD element DRUGASSESSMENTSOURCE value - Reporter ; Value for SOURCE_ID not found in table
Sample Extract from the Ack File 2 with rejection comment :
errormessagecomment>Imported Case #: XXXX, E2B rejected as will attach follow up manually Case #XXXX
(contains nullification) ;
ORA-01403: no data found DRUGASSESSMENTMETHOD: EVCTMR3 not found in lm_causality_method ; Value for CAUSALITY_ID not found in table
(contains nullification) ;
ORA-01403: no data found DRUGASSESSMENTMETHOD: EVCTMR3 not found in lm_causality_method ; Value for CAUSALITY_ID not found in table
Is this expected behaviour of Argus Safety ?
Solution
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
| Goal |
| Solution |