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 AFCS 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.

The user must manually execute a PMF Pipeline Result Area Entities Data Population to retrieve the data in the Result Area tables. Thefollowing Target tables Accounting Entries, Accounting Entries Header, Currency Exchange Rates, and General Ledger Data are used for data population in the result area.

Note:

Common Account Summary and Transaction Summary result area tables will be enhanced in future releases for data population.