2.4.3.1.2 Result Entity

It is a Unified Reporting or a Consumption layer. Analytical results can be simple to complex, contain quantitative and qualitative measures of a bank's Risk, Compliance, Customer and Financial Performance. The Reporting layer is a Dimensional Data Model spanning these key analytical functions. It forms the foundation of OFSAA Business Intelligence Applications but can clearly be used as the result data store for any equivalent engines and processes provided by other vendors, or custom built solutions. By providing a Single Data Repository for reporting needs, this layer provides a foundation for departmental as well as Cross-Departmental and Cross-Functional Reporting. Additionally, the schema of the reporting area is specifically built for Financial Services Analytics. As an illustration, the reporting area has a Run Dimension that is shared across all BI/reporting use cases. Similarly, the aggregation of shared measures/reporting into a common set of output structures (Account Summary) allows for Cross-Functional Reporting, which is increasingly the norm in Financial Institutions.

It is also the layer where all the input data sourced by the user through Staging Entities are persisted and available for reporting and consumption.

Along with the definition or structure of these entities, the catalog also provides mapping metadata to populate these entities from sourcing to PMF Data Pipeline.

Currently, this layer has entities to persist Journal, General Ledger Account, Transactions and Contract Data to cater to the needs of the DFCS solution.

Note:

For any existing extractions defined on Journal, Journal Header, and General Ledger Account Data, re-select the grain, entity, and attributes and save. This will enable extraction from the Persistence layer.

Note:

This is applicable only for the Banking domain. The PMF pipeline Account Load Run Map Population execution should have completed before executing the below step. This step is required for Common Account Summary and Transaction Summary data population.

Based on the domain (Life Insurance, Annuity, Retirement, General insurance (Property and Casualty), Health insurance, and Reinsurance issued) selected in the Add Domain page under Administration, domain specific Result Area Entities are populated.

The user must manually execute a PMF Pipeline Result Area Entities Data Population to populate data in the Result Area tables.

Note:

This is specific to Banking domain. The following Target tables Accounting Entries, Accounting Entries Header, Currency Exchange Rates, General Ledger Data, Common Account Summary and Transaction Summary are used for data population in the result area.

The user must manually execute a PMF Pipeline PPN to Result Area Entities Population to retrieve the data in the Result Area tables. The Decomposed Journals to Accounting Entries data population is performed through this pipeline.

The user must manually execute a PMF Pipeline Data Service Result Area Data Population to retrieve the data in the Result Area tables. The persistence of day and period-to-date movement information is performed through this pipeline.

Note:

The As of Date parameter value passed while executing PMF Pipeline Data Service Result Area Data Population filters on Effective Date attribute in the source entity.

The user must manually execute a PMF Pipeline Management Ledger As Of Date Results Population to retrieve the data in the Result Entity Management Ledger Period Balance And Movement. The management Ledger to result area As of Date data population is performed through this pipeline.

Note:

The As of Date parameter value passed while executing PMF Pipeline Management Ledger As Of Date Results Population filters on MIS Date attribute in the source entity.

The user must manually execute a PMF Pipeline Management Ledger Latest Effective Date Balance Results Population to map the data in the Result Entity Management Ledger Period Balance And Movement for latest effective dates. The result area Latest Effective Date data population is performed through this pipeline.

Note:

You must execute the Management Ledger As Of Date Results Population and Management Ledger Effective Date for historical dates to view reports from earlier periods. This must be executed in the same sequence for every As of Date.

The user must manually execute a PMF Pipeline Revaluation Entries Results Population to retrieve the data in the Result Entity Accounting Entries. The revaluation entries to result area data population is performed through this pipeline.

Note:

Select the As of Date parameter value as the execution date and Data Source parameter value as NA while executing PMF Pipeline Revaluation Entries Results Population filters on MIS Date attribute in the source entity.