FRY14Q Schedule M: Issue With Rule RLUS_FRAS_REG_PROD_TYPE_04 Post 807 Patch
(Doc ID 2494303.1)
Last updated on OCTOBER 31, 2019
Applies to:Oracle Financial Services - Regulatory Reporting for US Federal Reserve - Lombard Risk Integration Pack - Version 8.0.7 and later
Information in this document applies to any platform.
We noticed a change in join condition as part of 807 in rule RLUS_FRAS_REG_PROD_TYPE_04 (Reg US Reg Acc Summ Reg Product Type 04 - Commerical And Industrial)
Dataset : DSFD5023 (DS - US RL Reg Product Type 03 - Std Product Type and Party Type)
• Due to the removal of coalesce in the join condition, the v_reg_property_type is reported as null instead of MSG (n_reg_property_type_skey = 0). Because of this change the filter condition (mentioned below) will fail returning no records and hence the rule will not classify anything
• New rule RLUS_FRAS_REG_PROPERTY_TYP_MAP has been provided to classify n_reg_property_type_skey in FCT_REG_ACCOUNT_SUMMARY. The rule has an inner join with FCT_LOAN_ACCOUNT_SUMMARY table which is not being used in FRY14’s in AMEX and the rule doesn’t classify n_reg_property_type_skey in FCT_REG_ACCOUNT_SUMMARY table
Old Join Condition:
LEFT OUTER JOIN dim_property_type ON coalesce(fct_loan_account_summary.n_property_type_skey,0) = dim_property_type.n_property_type_skey
New Join Condition:
LEFT OUTER JOIN dim_reg_property_type ON fct_reg_account_summary.n_reg_property_type_skey = dim_reg_property_type.n_reg_property_type_skey
( ( dim_reg_property_type.v_reg_property_type = 'MSG' )
OR ( dim_reg_property_type.v_reg_property_type = 'OTH' ))
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