Instrument Table Validation Fails With Multiple Errors Due to Data Model Inconsistency
(Doc ID 2469722.1)
Last updated on MARCH 11, 2024
Applies to:
Oracle Financial Services Funds Transfer Pricing - Version 8.0.0 and laterInformation in this document applies to any platform.
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Symptoms
Instrument Table Validation fails with below errors generated in FSI_MESSAGE_LOG output:
ERRORS
1).
HINT1: Column XXX.PRIORITY_SECTOR_FLAG has Y for "nullable" in user_tab_columns
HINT2: Column XXX.PRIORITY_SECTOR_FLAG has N for "nullable" in rev_column_requirements
Table XXX.PRIORITY_SECTOR_FLAG column Nullable not met
2).
Hint1: Table - XXX. Columns in table that has column_property_cd of 15 is 6
Hint2: Table - XXX. Columns in table that are part of unique index XXX is 3
Table Property 1020 - Validate Transaction Key. Object: YYY. Invalid Processing Key Column Properties.
3).
FAILED: Table FSI_D_ASSET_BACK_SEC. Leaf Column "STRATEGY_ID" missing or incorrectly registered. Data Type must be NUMBER and FDM Data Type must be LEAF
HINT: check_table_class_req procedure returned status N while validating table FSI_D_ASSET_BACK_SEC for classification code 360
4).
HINT2: NO_DATA_FOUND exception encountered while validating table FSI_D_FUTURES
HINT3: FSI_D_FUTURES.PRIORITY_SECTOR_FLAG: No record found in rev_tab_columns
5).
HINT: Last query executed was - SELECT index_name FROM all_indexes WHERE table_owner = '<atomic schema>' AND table_name = 'XXX_LRM_CREDIT_LINES_V' AND uniqueness = 'UNIQUE'
Failed: Table Property 1010 - Validate Instrument.
Table:XXX_LRM_CREDIT_LINES_V. No valid unique index found
Failed: Table Property 1010 - Validate Instrument.
Table:XXX_LRM_LOAN_CONTRACTS_V. No valid unique index found"
6).
HINT3: FSI_D_TERM_DEPOSITS.CUR_PAR_BAL: rev_column_requirements.rev_data_type_cd is 1 rev_tab_columns.rev_data_type_cd is 99
Table FSI_D_TERM_DEPOSITS.CUR_PAR_BAL did not meet the column requirements. Check Column data type
STEPS TO REPRODUCE
The issue can be reproduced at will with the following steps:
1. Run Instrument Table Validation
2. Check FSI_MESSAGE_LOG output for the same
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 |