3.3 Materialized View

You to create a derived entity based on a dataset, an entity or a union of derived entities. For union and union all options, the metadata used in the participating derived entities determine the columns of the physicalized materialized view. For union based derived entity, even if the participating derived entities have metadata in common, the resultant materialized view in database will ensure unique columns. The supported materialized views are:

• Application Materialized View: Aggregates application-level data across multiple dimensions, offering insights into application origination and approval processes.
• Credit Line Materialized View: Aggregates data at the credit line level, capturing associated account data across dimensions, allowing for detailed analysis of credit lines and their linked accounts.
• Account Materialized View (Accounts Not Linked to Credit Line): Provides aggregated measures for accounts that are independent of any credit line, enabling targeted insights into standalone account activity.
• Aggregate Materialized View (Accounts Not Linked to Credit Lines and Stand-alone Accounts): Merges data from both credit lines and standalone accounts, offering a consolidated view of all financial facilities extended by the institution.
• Account Materialized View (All Accounts): Aggregates data for all accounts, whether linked or unlinked to a credit line, supporting account-level analysis across a wide array of over 50 dimensions. This view enhances flexibility in reporting by enabling comprehensive account-level insights regardless of credit line linkages.

Note:

To customize or modify the derived entities, ensure that you make a copy of the derived entities and do your modifications on them since the default derived entities are overwritten with the new derived entities as part of the upcoming releases.

• To enable partition for the derived entity, turn on the toggle button in the Derived Entity Details page. For more information, see the Creating Derived Entity section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
• Ensure that you add the partition values for the Derived Entity definitions that are created with prebuilt table flag set as Y. For more information see the Adding Partition Values section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.

Note:

As part of the 8.1.2.7.1 release, ensure that you mark the reporting flag as 'Y' for the required run skey before running the BI population batch since the materialized views are refreshed in the BI population batch. The refresh happens for the run skey for which the reporting flag is marked as 'Y'. The refreshed materialized views contains data only for one run skey (of a date for which reporting flag is marked as 'Y').