8 Technical Documents

This chapter covers the following topics:

• Data Requirements: 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 8-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	DERIVATIVES	Derivatives
  		FRA	Forward Rate Agreements
  		FUTURES	Futures
  		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:

  1. 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 corresponding Instrument_type_cd value. The list of valid Instrument_type_code values. is specified in table 8-1.
  2. 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 invalid Instrument_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 for Instrument_type_code, as specified in table 8-1. Note: Table 8-1 is a limited set and extension beyond this list is not allowed.
  3. 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 column Instrument_type_code is not included in Instrument data file, the value of Instrument_type_code is defaulted as ‘NA’ in Stage table. When this record gets loaded into the Processing table, the value for Instrument_type_cd will be inserted as -1 (Default).

     Note:

     PFTCS engine execution uses valid Instrument_type_code values to partition the Instrument dataset and thereby improves execution performance for rules that use Instrument_type_code as a filter. If customer is not providing the value for Instrument_type_code, the engine will scan all Instrument records as the execution would be based out of the default partition alone, that is, -1.
• Reporting Data Model: Please refer to the Doc ID: 2869409.1 to retrieve the Profitability and Balance Sheet Management Cloud Service Glossary of the Reporting Data Model (RPD Subject Areas).