5        OFSAA Features

Regulatory Reporting (REG REP) Solution configures the data hand-off structure to Lombard using metadata. The following sections provide details on datasets, measures, hierarchies, and Derived Entities. Multiple derived entities are linked to a specific regulatory schedule. You can modify the configuration using the OFSAA infrastructure. Additionally, the metadata route provides traceability from reporting elements to the data elements used.

This chapter provides an understanding of the AAI components used in the solution and dimensional mapping.

Topics:

·        OFSAA Infrastructure

·        Business Metadata

·        Derived Entity

·        Rules Framework Features

·        Dimension Mapping

OFSAA Infrastructure

OFSAA Infrastructure includes the facilities for creating and maintaining dimensional reference data, interest rate, and currency exchange rate data, and process tuning data. Additionally, OFSAA Infrastructure includes functionality for building and maintaining rules that can be used by any Oracle Financial Services Analytical Application. These common rule objects include:

1.     Expressions

2.     Hierarchies

3.     Filters

The analytical applications that you see on the Left-Hand Side (LHS) of the Financial Services Applications home page depending on your logon privileges and on the OFSAA modules that are installed for your environment.

Figure 51: Metadata Management Landing Page

Business Metadata

In addition to Derived Entity, REG REP uses the following OFSAA features to create the business metadata. For more information about the features,  see the OFS Analytical Applications Infrastructure User Guide.

·        Hierarchies: Some OFSAA dimensions support hierarchies. Hierarchies can be used to provide sophisticated stratification for either processing or reporting purposes. For example, an organizational hierarchy can start with a Division level containing Western Region, Eastern Region, and Southern Region; the next level down within the hierarchy can be state or county. A product hierarchy can begin with branches for Asset vs. Liability vs. Service products; under the Asset branch, you can define additional branches for Mortgage Lending, Commercial Lending, Consumer Lending, and so on.

·        Measures: Business Measure refers to a uniquely named data element of relevance that can be used to define views within the data warehouse. It typically implies aggregated information as opposed to information at a detailed granular level that is available before adequate transformations.

·        Business Processor: It refers to a uniquely named data element of relevance that can be used to define views within the data warehouse. It typically implies aggregated information as opposed to information at a detailed granular level that is available before adequate transformations.

·        Datasets: It refers to a group of tables whose inter-relationship is defined by specifying a join condition between the various tables. It is a basic building block to create a query and execute a data warehouse for a large number of functions and to generate reports.

Derived Entity

It is the primary component of OFSAA used for OFSDF Interface with Lombard Risk for RBI Regulatory Reporting Solution uses Derived Entity to create a physical materialized view which is then queried by Lombard using pre-set data hand-off templates. An Entity refers to a table in which data is stored. Derived Entity within the infrastructure system facilitates you to define entities that are populated through a series of data transformation processes resulting from an existing Data Set or a Source Application. An Entity can be used to define other Business Metadata such as measures, hierarchies, dimensions, data sets, and cubes.

Derived Entities comprise the following:

·        Measures

·        Hierarchies

·        Datasets

Ensure to define the above components within OFSAA before configuring the derived entity, and select Materialized View property in Derived Entity. This property creates the derived entity as materialized views.

1.     Navigate to path Oracle Financial Services Regulatory Reporting for Reserve Bank of India, select Metadata Management, and then select Derived Entity. The existing derived entities summary screen is displayed. You can add a new derived entity and Edit, View, Delete, or Copy an existing derived entity.

Figure 52: Derived Entity Summary Page

Derived Entities must have AS_OF_DATE and LEGAL_ENTITY as the mandatory dimensions. The rest of the structure of the derived entity can vary depending on the dimensions present. A metadata configuration table is present in AgileREPORTER to link the name of the column in the derived entity and dimension that is referred to in the dimension mapping process.

Derived entities have data for the Final Reporting Run only, which is reported to the Regulatory, and are refreshed for the latest hand-off date.

A metadata configuration table is maintained within AgileREPORTER to capture the derived entities that supply data for each schedule.

2.     Click the Add button to create a new Derived Entity.

Figure 53: Derived Entity User Interface

Topics:

·        Creating Derived Entity 

·        Saving Derived Entities 

·        Refreshing Derived Entities 

·        Adding a Hint to a Derived Entity 

Creating Derived Entity

Derived Entities must have Code, Short Description, and Source Type mandatory dimensions as shown in Error! Reference source not found.. The rest of the structure of the derived entity can vary depending on the dimensions present. A metadata configuration table is present in AgileREPORTER to link the name of the column in the derived entity and dimension that is referred to in the dimension mapping process.

Derived entities have data for the Final Reporting Run only, which is reported to the Regulatory, and are refreshed for the latest hand-off date.

A metadata configuration table is maintained within AgileREPORTER to capture the derived entities that supply data for each schedule.

Refer to OFS Analytical Applications Infrastructure User Guide in (OHC) documentation library for detailed steps on creating a derived entity.

Saving Derived Entities

After the server restart is complete, save all the derived entities manually using the OFSAAI User Interface (Oracle Financial Services Regulatory Reporting for Reserve Bank of India, select Metadata Management, and then select Derived Entity).

Topics:

Adjustments DE

The adjustments feature enables to adjust the differing values of the report systems. The Adjustments Derived Entity derives its values from the Adjustments Fact table (FCT_REG_REPORT_ADJUSTMENTS) that specifies the adjustment value and the seeded table (DIM_REG_REPORT_CELL) that specifies the cell ID / MDRM Code and the Report Code to which the MDRM belongs to. This ensures that there can be direct adjustments made to MDRM(s) such that the values from both the derived entities are traceable and efficiently reported.

Refreshing Derived Entities

The complete Derived Entities can be refreshed as a whole or incrementally for selected periods. See the  OFS_DE_INCREMENTAL_MV_REFRESH in (OHC) documentation library for detailed steps to incrementally refresh derived entities.

Implementing the Adjustment Feature

Perform the following steps to implement the Adjustment feature:

1.     Identify the Cell ID for the report and line item where an adjustment has to be implemented.

For example:

Report: DSBIALE

Line Item: I.1 Cash on hand

Cell ID: RBIDSBIALEP001R0020C0020

The report currently displays a Total value = 69,337,000.00 for the identified cell as shown in the following figure. Now, the requirement is to adjust this amount to 69,338,000.00

Figure 54: Before Adjustment Details Window

2.     FCT_REG_REPORT_ADJUSTMENTS: This table must be populated with the requisite Adjustment Amount and other related columns.

For example:

N_ADJUSTED_AMT - 1000

The corresponding N_CELL_SKEY value must be picked from DIM_REG_REPORT_CELL for the respective CELL_ID.

Also, the following columns must be updated accordingly:

N_ENTITY_SKEY,

N_RUN_SKEY,

N_MIS_DATE_SKEY

3.     Execute the resave batch for Adjustments (<<INFODOM>>_RBI_ADJUSTMENT_RESAVE), to save the Adjustment derived entity - DEADJ001.

4.     The retrieved report should reflect the amount after adjustments, as shown in the following figure. (69,337,000.00 +10000) = 69,338,000.00

NOTE:   

The Adjustment amount can be negative and to achieve a subtracted amount.

Figure 55: Adjusted Amount Details Window

NOTE:   

The Adjustment feature works only for fixed grid cells (Open Y cells are not supported).

Adding a Hint to a Derived Entity

Perform the following steps to add a Hint to a Derived Entity:

1.     To add a Hint in a DE, perform the following steps:

a.     Log in to OFSAA application GUI.

b.     Navigate to Oracle Financial Services Regulatory Reporting for Reserve Bank of India, select Metadata Management, and then select Derived Entity. The Summary Screen is displayed as follows.

Figure 56: Derived Entity Summary Page

c.     Enter the DE Code and click Search. The corresponding DE Code and details are displayed.

Figure 57: Derived Entity Selection Page

d.     Select the DE Code and click Edit. The DE details are displayed.

Figure 58: Derived Entity Edit Page

e.     Enter the Hint for the DE and click Save.

2.     To execute the Hint added in the DE, perform the following steps:

a.     Navigate to Financial Services Data Foundation, then select Operations, and then select Batch Execution. The Batch Execution screen is displayed.

Figure 59: Batch Execution Summary Page

b.     Enter the Batch Description Like and click Search.

Figure 60: Batch Execution Selection Page

c.     Select the modified or required DE for Batch Execution under the Batch Details.

Figure 61: Batch Execution Edit Details Page

d.     Select the Date and click Execute Batch. After execution, the DDL reflects the Hint added to the DE.

Rules Framework Features

OFSDF Interface with Lombard Risk for RBI uses the following Rules Run Framework of OFSAA. For more information about the features, see the OFS Analytical Applications Infrastructure User Guide.

·        Rules: Financial institutions require constant monitoring and measurement of risk to conform to prevalent regulatory and supervisory standards. Such measurement often entails significant computations and validations with an organizations data. Data must be transformed to support such measurements and calculations. The data transformation is achieved through a set of defined rules. 
REG REP uses Rules for reclassification of dimensions.

Dimension Mapping

Each cell reference is mapped to a set of dimensions and measures. This mapping is documented in excel and then converted to a Decision table through an offline utility provided by AgileREPORTER. A decision table is a metadata object within AgileREPORTER that stores the criteria for deriving value for each cell reference. The metadata is packaged for regulatory reports as part of the OFS Risk Regulatory Solution. The decision table process within AgileREPORTER reads the metadata and derived entity published by OFSAA to populate data required for returns for the specified date and legal entity.

The following table is an example of dimension mapping. Each cell reference is mapped to a set of dimension members and measures. If a dimension is left empty for a cell reference, it indicates that it is not participating in the mapping process. If there are multiple mappings for a cell reference, then the value of this cell can come from any of these criteria.

The decision mapping table is processed against the contents of the derived entity to reporting data. Each record of the derived entity is matched against the criteria specified in the decision table to identify the cell reference and derive return data (such as cell reference and cell value).

The following table is derived after converting the dimension member and measure names into corresponding dimension member codes (not surrogate keys) and measure codes. This decision table mapping is provided for each decision table in excel format as per the template. AgileREPORTER converts the decision table mapping present in excel into configuration entries within their schema.

NOTE:   

All the dimension member codes that are used in the decision table are pre-seeded by OFSAA and cannot be modified. Therefore, if you have other member codes in the dimension, then you must re-classify them by using re-classification rule post load, or value-code mapping during load.

Decision tables must be prepared closer to the report submission period. In some cases, reclassification of multiple dimensions that result in a single unified reporting dimension must be performed to address the complexity of the decision table. Reclassification rule is defined in OFSAA and packaged as part of the OFSAA Risk Regulatory Reporting Solution.

In some cases, certain sections of the schedule or the entire schedule can be a list of data rows without any mapping to a fixed set of dimension members. For example, Top 20 counterparties, List of Available for Sale (AFS) - securities. In such cases, since there are no cell references, decision table mapping specifies the names of dimensions and measures of derived entities in the sheet column or row column of the template.

NOTE:   

As a part of the solution, metadata exists as ready-to-use or  pre-configured with the installer.