FFIEC009: F_TRANSFERABILITY_RESTRICTION Usage And Sourcing
(Doc ID 2767958.1)
Last updated on APRIL 15, 2021
Applies to:Oracle Financial Services - Regulatory Reporting for US Federal Reserve - Lombard Risk Integration Pack - Version 8.0.9 and later
Information in this document applies to any platform.
Version: RRS 80963, FSDF 8093
1) SVF has only STG_CORRESPONDENT_ACCOUNT & STG_INVESTMENTS tables with F_TRANSFERABILITY_RESTRICTION flags.
FCT_REG_FUND_LEND_DETAILS.F_TRANSFERABILITY_RESTRICTION is populated from FCT_COMMON_ACCOUNT_SUMMARY.F_TRANSFERABILITY_RESTRICTION.
Hence F_TRANSFERABILITY_RESTRICTION may not be populated for all the claims
2) All FSI_RRS_ACCT_MITI_PLCD_COLL insert statements filters on
AND COALESCE(FCT_REG_FUND_LEND_DETAILS.F_TRANSFERABILITY_RESTRICTION, 'Y') = 'Y'
Why filter Y is applied for ACCTMITIGANT, ACCTGUARANTOR, ACCTCOLATERAL, ACCOUNT Grains?
(FN_RRS_FAMM_DATA_POP, FN_RRS_FAPCM_DATA_POP, FN_RRS_ACCT_MITIGANT_DATA_POP, FN_RRS_ACCT_PLCD_COLL_DATA_POP)
3) Following configuration uses HREG2357 - HIR - RR Transferability Restriction Flag = N, Y
C-Part-II - Collateral held against claims with No risk transfer - M870, M871, M872
a) Why C-Part-II MDRMs uses Transferability Restriction Flag = N,Y filter, since these MDRMs report collaterals with no risk transfers (should be transferability restriction = Y)
b) Hierarchy uses logic (COALESCE(A_DIM_BOOLEAN_TRANSF_RESTR_FLG.V_FLAG_CODE, 'N')) which defaults to 'N'
Any NULL records will get treated as no transfer restriction on claim
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