Case Number Not Populated After Accepting E2B From ICSR Pending Screen
(Doc ID 2636659.1)
Last updated on FEBRUARY 09, 2020
Applies to:
Oracle Argus Safety - Version 8.1.2 and laterInformation in this document applies to any platform.
Symptoms
Accepted Initial cases from ISCR Pending screen.
ICSR Report Pop-Up screen shows N/A in "Accepted Case Number" field.
Upon closing the ICSR Report Pop-Up screen the message:
Case is not Accepted
Checked in SAFETYREPORT Table, the status is 102 (Accepted), but CASE_XREF is null.
Checked in CMN_ERROR_LOG table with the USER_ID and found the below error logged in.
Argus Safety.COM :- Oracle error 1 occurred.
ORA-00001: unique constraint (ARGUS_APP.PK_USER_E2B_INCOMING_CASES) violated
SQL: insert into USER_E2B_INCOMING_CASES (user_id, case_id, report_id, seq_num, transmit_warning,case_num) values(:P_USER_ID, :P_CASE_ID, :P_E2B_REPORT_ID, :P_ESM_SEQ_NUM, :P_ESM_TRANSMIT,:P_CASE_NUM)
PL/SQL Call Stack:
SQL
673 PKG_CONSOLE_COMMON.P_ERROR_LOG
1 __anonymous_block
ORA-00001: unique constraint (ARGUS_APP.PK_USER_E2B_INCOMING_CASES) violated
SQL: insert into USER_E2B_INCOMING_CASES (user_id, case_id, report_id, seq_num, transmit_warning,case_num) values(:P_USER_ID, :P_CASE_ID, :P_E2B_REPORT_ID, :P_ESM_SEQ_NUM, :P_ESM_TRANSMIT,:P_CASE_NUM)
PL/SQL Call Stack:
SQL
673 PKG_CONSOLE_COMMON.P_ERROR_LOG
1 __anonymous_block
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 |