My Oracle Support Banner

Recon Allocations Failing In 8.1 (Doc ID 2796067.1)

Last updated on MAY 24, 2023

Applies to:

Oracle Financial Services Analytical Applications Reconciliation Framework - Version 8.0.0 and later
Information in this document applies to any platform.


Clarification required on below points :

1. Allocation is failing with java exception for datatype of N_EXPOSURE_AMOUNT. Oracle code is restricted to integer with max length of 10 as per this exception. Please analyze this exception on your end and let us know resolution.
2. After fixing error in step 1 to replace N_EXPOSURE_MOUNT values to less than 10 we see allocation proceeding but failing for invalid column N_LOAD_RUN_ID. Is N_LOAD_RUN_ID expected in all custom allocation targets? We do not have this column in custom product processor used as allocation target but insert generated is referring to this.
3. After adding N_LOAD_RUN_ID in custom product processor allocation task proceeds but fails for another error on mismatch in column names for optional dimension. We have V_ALT_GL_ACCOUNT_CODE column in dimension table used as optional dimension. Allocation is expecting column with same NAME to be present in allocation target PP and/or FCT_GL_ADJUSTMENT_ENTRIES. We have this column names as V_ALT_GLCODE (missing ACCOUNT) in allocation target PP.
4. Cartesian is forming and duplicate adjustments for same exposure are getting populated into target allocation table. Loop in the code should have a filter either on FSI_GL_MAPPING_PP_ALLOC_DTLS.V_ADJ_OBJECT_DEF_CODE or FSI_GL_MAPPING_PP_ALLOC_DTLS.V_TABLE_NAME to avoid cartesian


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

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