5 Run Chart Execution

The execution of Run Chart starts by running the Data Foundation Processes.

Due to confidentiality reasons, the Run Charts are only available on My Oracle Support. For more information, seeOther Documents.

In case of an integrated environment, if the DIM_DATES table has intermittent records, then the user should clean up the DIM_DATES table by temporarily disabling the FKs (Foreign Keys) and then execute the OOTB Seeded Run: RN_DATES for the entire range.

To get the correct LTV Values, the Customer needs to execute the Run Chart from earliest Start Date across all accounts.

• The Data Foundation Processes
  • Reference Data Load (Dimensions): The Reference Data Load is needed to load all the Dimensions.
  • Currency Conversion Load: This loads the Exchange Rate Data.
  • Party Load: This loads all the Dimensions related to Party like DIM_PARTY, DIM_CUSTOMER along with MLS Tables and Derived Entities.
  • Account Load (Dimension + Facts): This loads all the relevant Dimensions and Fact Data for the Instrument Tables.
  • Party Facts Load: This Loads Facts at the granularity of Party like FCT_COMMON_CUSTOMER_SUMMARY, FCT_CRM_CUSTOMER_SUMMARY, and so on.
  • Transaction Data Load (Dimension + Facts): This loads detailed Account Transaction Data and the Summaries.
  • Application Data Load: This loads data that is part of the information provided by Customers while applying for a particular Product.
  • Opportunity Data Load: This loads data corresponding to potential Business Opportunities and leads that are available to the Bank along with the conversion stages.
  • Management Data Load: This loads data corresponding to the Banks Client Relationship Managers and their corresponding Professional Hierarchies.
• PFT Integration
• FTP Integration
• Profitability Load
• Projections (ARIMA Model)
• Reporting Line Correlation (Regression Model)
• Segmentation

This ends the Base Run Chart Execution.