My Oracle Support Banner

KYC[807] - F_CLOSURE_UPADTES Is Not Updating The Jurisdiction In The FCT_CUST_RVWDTLS (Doc ID 2769900.1)

Last updated on APRIL 26, 2021

Applies to:

Oracle Financial Services Know Your Customer - Version 8.0.0 and later
Information in this document applies to any platform.

Symptoms

F_CLOSURE_UPADTES is not updating the jurisdiction in the FCT_CUST_RVWDTLS
In other words, the customers present in FCT_CUST_RVWDTLS are inserted with jurisdiction they were first loaded & are not being updated based on the last data loaded into the CUST table.

Steps to replicate:
1. Pick any customer who is having an assessment in fct_cust_ra_histry.
2. change cust.JRSDCN_CD for the identified customer.
3. Now run a new batch to pick this customer under accelerate_re-review/periodic_rereview. 
4. We see fct_cust_ra_histry & fct_ra tables updated with new jurisdiction code whereas FCT_CUST_RVWDTLS.V_JRSDCN_CD still shows old jurisdiction code.

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


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