9 Technical Documents
This chapter covers the following topics:
-
Asset Liability Management
Cloud Service Data Requirement: This document contains detail of account,
ledger, reference, and market data needed to deliver business functionality. They
are required at a pre-defined granularity / format and can come from your source
systems and external data providers.
Table 9-1 STAGE and INSTRUMENT Tables
STAGE_TABLE_NAME INSTRUMENT_TABLE_NAME INSTRUMENT_TYPE_CODE NAME STG_ASSET FSI_D_ASSET COMMLOANS Commercial Loans CONSLOANS Consumer Loans MORTGAGES Mortgages INVESTMENT Investments ABS Asset Backed Securities CCARDS Credit Cards CREDITLINES Credit Lines LEASES Leases LOANCONTRACTS Loan Contracts STG_ASSET, STG_LIABILITY FSI_D_ASSET,FSI_D_LIABILITY MMCONTRACTS Money Market Contracts STG_LIABILITY FSI_D_LIABILITY ANNUITYCONTRACTS Annuity Contracts BORROWINGS Borrowings DEPOSITS Deposits CASA Checking and Savings WHOLESALEFUNDING Wholesale Funding TD Term Deposits RETIREMENTACCOUNTS Retirement Accounts STG_LEDGER_INSTRUMENT FSI_D_LEDGER_INSTRUMENT LEDGERINSTRUMENTS Ledger Instruments STG_FEE_BASED_SERVICE FSI_D_FEE_BASED_SERVICE MERCHANTCARDS Merchant Cards MUTUALFUNDS Mutual Funds OTHERSERVICES Other Services TRUSTS Trusts STG_DERIVATIVE FSI_D_DERIVATIVE FRA Forward Rate Agreements FXCONTRACTS Foreign Exchange Contracts OPTIONS Caps, Floors, Collars SWAPS Interest Rate Swap FXSWAP Foreign Exchange Swap STG_OFF_BALANCE_SHEET FSI_D_OFF_BALANCE_SHEET GUARANTEES Guarantees STG_LOAN_COMMITMENTS FSI_D_LOAN_COMMITMENTS RATELOCK Rate Lock Commitments While loading data into Instrument tables, we need to remember:
- If the user is providing a valid
Instrument_type_code
value in the loaded Instrument data file, the record gets loaded into Stage Instrument table, and also in the Processing Instrument table with the correspondingInstrument_type_cd
value. The list of validInstrument_type_code
values. is specified in table 8-1. - If the user is providing an invalid
Instrument_type_code
value in the loaded Instrument data file, the record gets loaded into Stage Instrument table with the invalidInstrument_type_code
, but the record gets rejected when the data loading happens from Stage table into Processing Instrument table. Thus, users need to take care that they use only valid values forInstrument_type_code
, as specified in table 8-1. Note: Table 8-1 is a limited set and extension beyond this list is not allowed. - If column
Instrument_type_code
is included in Instrument data file but the user is not providing value for it, the concerned records will get rejected as it is a not null column. If columnInstrument_type_code
is not included in Instrument data file, the value ofInstrument_type_code
is defaulted as ‘NA’ in Stage table. When this record gets loaded into the Processing table, the value forInstrument_type_cd
will be inserted as -1 (Default). - Refer PBSM Data Requirement file
to know mandatory and optional entity-attributes for your cloud
service. When mandatory attributes like
ISO_CURRENCY_CD
are not given in input data file, the records will get rejected by the respective loader programs while moving from Stage to Processing tables. The records will normally not get rejected during data movement from File to Stage tables.
- If the user is providing a valid
- Reference Guide: The Reference Guide emphasizes business analysis and provides definitions, analytical concepts, processes, and calculations used in the Oracle Financial Services Cash Flow Engine (CFE). The information provided includes data requirements, payment and repricing event logic, calculation formulas, and various methodologies used to produce cash flows.
- Data Dictionary: This guide contains detailed information necessary for correct data population, including field definitions, and recommended default values for the cash flow processing fields.
- FRC Analytics - Exporting Files from Oracle Analytics: This document helps you to use Oracle Analytics Server (OAS) to aggregate the data to required level and downloading it from Object Storage.