My Oracle Support Banner

Insert Into FCC_ACCOUNTTRADEDLY_LOOKUP Failing In ECM Batch Task 40 (Doc ID 3063266.1)

Last updated on DECEMBER 17, 2024

Applies to:

Oracle Financial Services Enterprise Case Management - Version 8.0.7 and later
Information in this document applies to any platform.

Symptoms

Insert into FCC_ACCOUNTTRADEDLY_LOOKUP failing in ECM Batch Task 40

We are running ECM batches in prod and our batch is failing on Task 40. Upon investigating, we were able to identify that it's failing due to the UK_FCC_ACCOUNTTRADEDLY_LOOKUP violation.

This is due to the same account with same Trade date (process date) coming again for insertion on a new data_dump_date.
We noticed that there is a NOT EXISTS condition to prevent this kind of insertion, but that NOTEXISTS is conditioned on Account internal id and last data dump dt. We believe that because the constraint and primary key is on Account_id and trade date, the NOT EXISTS condition should also look for ACCOUNT_INTRL_ID and TRADE_DT not data_dump_dt.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.