CS - ECM batch Issue
(Doc ID 2890457.1)
Last updated on AUGUST 22, 2022
Applies to:
Oracle Financial Services Customer Screening - Version 8.0.8.1.0 and laterInformation in this document applies to any platform.
Symptoms
The Job 13 (FCCMINFO_Oracle_CS_Event_Processing_13) failed and it is throwing error as invalid number.
ORA-01722: invalid number
Changes
Verified below table data:
SELECT * FROM FCC_DM_ERROR_DETAILS WHERE DM_ID='5002';
SELECT * FROM FCC_DM_AUDIT WHERE DM_ID='5002';
Below is the query which is throwing the error from above audit table.
SELECT CS_ALERTS.JRSDCN_CD,CS_ALERTS.N_ALERT_ID,9734 N_RUN_SKEY,'NEW' V_STATUS_CD,CS_ALERTS.BUS_DMN_LIST_TX,to_date('20220729','yyyyMMdd') D_MIS_DATE,CS_ALERTS.N_ALERT_SCORE,CS_ALERTS.FIC_MIS_DATE,FCC_EVENT_LOOKUP.N_EVENT_SKEY,'CS' V_DATA_ORIGIN,nvl(fcc_case_PRIORITY.V_CASE_PRIORITY_CODE,'HIGH') V_EVENT_PRIORITY,'CS_'||CS_ALERTS.WATCHLIST_RECORD_TYPE V_EVENT_TYPE FROM CS_ALERTS INNER JOIN FCC_EVENT_LOOKUP ON CS_ALERTS.n_alert_id = FCC_EVENT_LOOKUP.v_event_cd LEFT JOIN fcc_case_PRIORITY ON FCC_CASE_PRIORITY.V_CASE_TYPE='CS_'||CS_ALERTS.WATCHLIST_RECORD_TYPE AND FCC_CASE_PRIORITY.V_JURISDICTION_CD = CS_ALERTS.JRSDCN_CD AND fcc_case_PRIORITY.V_BUSINESS_DOMAIN_CD=CS_ALERTS.BUS_DMN_LIST_TX AND ( CASE WHEN CS_ALERTS.N_ALERT_SCORE>=FCC_CASE_PRIORITY.N_CASE_PRIORITY_MIN_SCORE AND CS_ALERTS.N_ALERT_SCORE < FCC_CASE_PRIORITY.N_CASE_PRIORITY_MAX_SCORE THEN 1 ELSE 0 END=1 ) WHERE CS_ALERTS.FIC_MIS_DATE = to_date('20220729','yyyyMMdd') AND CS_ALERTS.Prcsng_Batch_Nm IN (SELECT FCC_BATCH_DATAORIGIN.V_DATA_ORIGIN FROM FCC_BATCH_DATAORIGIN WHERE FCC_BATCH_DATAORIGIN.N_RUN_SKEY = 9734) AND CS_ALERTS.CUST_TYPE = 'CUSTOMER' AND FCC_EVENT_LOOKUP.v_data_origin = CS_ALERTS.Prcsng_Batch_Nm;
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 |