This chapter provides an understanding of the prerequisites, general, and data preparation assumptions and logging into the application.
Topics:
· Accessing the OFSDF Interface with RBI Interface
· Organization of the Interface for User Roles
OFS Regulatory Reporting for Reserve Bank of India with Lombard Risk Integration allows you to perform the following activities:
· Manage Data Loading and Transformation from various source systems to staging, processing, and results.
· Manage relevant OFSAA metadata for regulatory reporting purposes. This includes creating, modifying, and viewing the metadata used in reporting.
· View the report metadata for mapping.
· Drill down from AgileREPORTER to OFSAA results area.
For detailed prerequisites and instructions on installing this Interim Release, see the Oracle Financial Services Regulatory Reporting for Reserve Bank of India Lombard Risk Integration Pack Installation Guide Release 8.1.1.0.0.
OFSDF interface with Lombard Risk for RBI is a reporting application and it does not perform any risk/stress calculations. The following are the assumptions for the application:
· Data required for risk and compliance regulatory report templates are available in FSDF as per data requirements.
· Lombard Risk Reporter Portal supports other non-risk and non-compliance related regulatory templates and Oracle Financial Services Analytical Application (OFSAA) may not supply all the necessary data for such reports.
· Textual and other related portions of reports like personal details, contact details, Yes / No choices must be updated on Report Portal directly and FSDF does not have a placeholder for it.
· Data provided is post reconciliation to ensure that accuracy of data being reported (non-prescribed by regulators) are performed in OFSAA using various components General Ledger (GL) reconciliation, data quality checks, and variance reporting.
· Validity checks such as edit checks, cross-validation checks, and so on prescribed by the regulator are performed within the AgileREPORTER.
· All monetary amounts are expected to be positive in number, except valuation outputs which can be positive or negative. Rules are constructed assuming the negative sign of valuation amounts wherever applicable.
· The application populates a few specific dimension tables, known as seeded / sample tables as part of the installation script. Since they are used in the metadata, changes in data values have an impact on overall functioning.
· All percentage data are expected in decimal format meaning 9% must be provided as 9 and not 0.09.
· For data provided as of date, such as the last day of the quarter of the reporting year: Quarterly and Year to Date (YTD) report for the given date display the same value for those measures which are of as of the date in nature. For example the Annual and Quarterly Balance Sheet and BASEL report generated as of 31-MAR show the same values for all measures such as Account Balance.
· Account Balances such as End of Period Balances are expected to be provided as Net of (without) Unearned Income.
· RCA III - Mkt Risk Specific-CDS: As per the reporting requirement, we must use Fct_reg_market_risk_exposures.f_cds_undrly_party_cre_nbfc flag to identify CDS counterparty type. DM change for the same is handled in subsequent model. To support template for 8.0.5.1.0 releases, use the unused column, Fct_reg_market_risk_exposures.V_eff_credit_score_source. This column is populated from Basel tables, that is, Fct_market_risk_exposures.f_cds_undrly_party_cre_nbfc.
· RCA III - CR On BS excl. Sec: Reporting in this schedule is as per Asset Class (for example Domestic PSE, Foreign Bank, and so on) for Pre CRM amount and CRM Amount. There is no separate reporting for Non-Sec Covered Amount / RWA (Covered by mitigant) anywhere in the template. So we are assuming the following:
· If the mitigant is Guarantor or Credit Derivative, then the amount covered by that mitigant will be reported as per Effective Asset Class in its respective line in the template. So, each reporting line will have two parts added to it for the Amount of Exposure column. The first part will report Exposure based on Original Asset Class to report Uncovered RWA, the second part will report Exposure based on Mitigant's Effective Asset Class to report Covered RWA column.
· RCA III - Securitization Related Schedules: Regarding RW reporting of Unrated Eligible Liquidity Facilities in Line 1.2 and 1.2 of all 4 schedules related to securitization exposures, RW is taken as maximum RW assigned to any of the Unrated Eligible Liquidity Facilities. RCA III template issued by RBI has only one cell for the reporting of RW of such unrated facilities. If a reporting bank has more than one such facility, the maximum RW assigned to any one of these facilities is reported. This is taken as the interpretation of the template.
· RCA III - Securitization Related Schedules: Line Items 1.1. III, 1.1. IV, 2.1. III, and 2.1. IV is not mapped for all 4 schedules related to securitization exposures. The reason behind not mapping these is that they are already covered in 1.2 and 2.2.
· RCA III - Capital Structure Schedules: Some line Items are not mapped in Capital Schedules. The following table explains the reason for not mapping these line items.
Line Item |
Comments |
|---|---|
The shortfall in regulatory capital instruments in the unconsolidated entities - Amounts subject to Pre-Basel III Treatment. |
For this line, there is no amount subject to Pre-Basel III Treatment. |
Regulatory adjustments applied to Common Equity Tier 1 in respect of amounts subject to Pre-Basel III treatment (please specify the details in the remarks column). |
All items falling under this category are already captured in previous reporting lines of the template, hence null mapping for this line. |
The shortfall in the Additional Tier 1 capital of majority-owned financial entities that are not consolidated with the bank. |
As per our interpretation of RBI Basel Guidelines, the deduction must be from CET1 alone, and not from respective Tier (CET1, AT1, and T2). |
Regulatory adjustments applied to Additional Tier 1 in respect of amounts subject to Pre-Basel III treatment (please specify the details in the remarks column). |
All items falling under this category are already captured in previous reporting lines of the template, hence null mapping for this line. |
Regulatory adjustments applied to Additional Tier 1 due to insufficient Tier 2 to cover deductions - Amounts subject to Pre-Basel III Treatment. |
For this line, there is no amount subject to Pre-Basel III Treatment. |
The shortfall in the Tier 2 capital of majority-owned financial entities that are not consolidated with the bank. |
As per our interpretation of RBI Basel Guidelines, the deduction must be from CET1 alone, and not from respective Tier (CET1, AT1, and T2). |
Regulatory adjustments applied to Tier 2 capital in respect of amounts subject to Pre-Basel III treatment (please specify the details in the remarks column). |
All items falling under this category are already captured in previous reporting lines of the template, hence null mapping for this line. |
· CRILC Section 1 - Line In case SMA-0 under SMA, the reason thereof: is not mapped as this is expected to be a user input field, where you can directly update the SMA reason.
· ALE - Section 2 Part F1 and F2 - Line b) Credit event payments (cash-settled): is interpreted to be derived from subsequent two lines paid and received.
After the application is installed and configured, to access the OFSDF Interface with Lombard Risk for RBI application you need to log into the OFSAAI environment using the OFSAAI login page.
To access application, follow these steps:
1. Enter the OFSAAI URL in your browser. The OFSAAI login page is displayed.
Figure 2: OFSAAI Log In
2. Select the desired language from the Language drop-down list.
3. Enter your User ID and Password. When you log into OFSAAI, the OFSAAI Applications page is displayed. Select Financial Services Data Foundation.
Figure 3: OFSAAI Application Page
4. Select the Financial Services Data Foundation option to navigate to the FSDF application or select the Oracle Financial Services Regulatory Reporting for Reserve Bank of India to navigate to the OFS REG REP RBI application.
This section explains the various features used by an analyst. It describes the organization of the user interface and provides step-by-step instructions for navigating through the application to carry out these activities.
To access the Process Execution Summary, the following roles must be assigned to the user:
1. Modify Run Parameters
2. Approve Reporting Flag
3. Override Reporting Flag
4. Request Reporting Flag
5. Run Reporting Flag
6. View Run Details
Data Analysts are expected to perform the following activities:
1. Executing Batch to Refresh Derived Entities
2. Drill down from AgileREPORTER to OFSDF
Regulatory Report Analysts are expected to perform the following activities:
1. Drill down from AgileREPORTER to OFSDF
2. Using Metadata Browser to check schedule wise metadata
3. Using Metadata Browser to check metadata usage across schedules
Topics:
· Reporting Flag for Run through Process Execution Summary
· Executing Batch to Resave Derived Entities
· Executing Batch to Refresh Derived Entities
· Report Verification - Drill Down from AgileREPORTER to OFSAA Results Area
· Retrieving the Returns from AgileREPORTER
This section provides information on the Runs that are applicable for RBI. The Process Execution Summary is launched once the Runs are executed from the Processing Modelling Framework. The following figure displays the Process Execution Summary with the data that is retrieved from the Process Modeler.
Various applications provide data for regulatory reporting. You must mark specific executions for regulatory reporting as the final run.
1. After logging into OFSAAI applications page, navigate to Oracle Financial Services Regulatory Reporting for Reserve Bank of India and select Process Execution Summary.
Figure 4: Process Execution Summary Screen
2. Scroll towards the right and click Filter, select the Run Pipeline from the available pipeline selection list. Click OK.
Figure 5: Pipeline Selection Screen
3. After the Run execution, the Process Execution Summary is generated in the list format as illustrated in the following steps. The summary page displays the Process Names for which the Run Parameters are generated.
4. Scroll towards
the right and click View 
in the Process Name
row.
Figure 6: Process Execution Summary View Screen
You can view the detailed definition of a Run on a read-only mode. The Process Execution Details page displays the execution details for the selected Execution Key with the color band displaying the status of each Execution Key.
Figure 7: Process Execution Details Screen
The execution keys and the corresponding execution details are as follows:
· Process Description: The RBI Regulatory Common Process Run appears as the process description when the user executes the Regulatory Run.
· MIS Date: The extraction date is displayed in this field.
· Start Time: It displays the Execution Date and the Execution Time when the Execution Run starts.
· End Time: It displays the End Execution Date and Execution Time.
· Process Execution Key: Unique identifier assigned to each Process Execution.
· Approval Status: It displays the Approval status of the Execution as Completed, Failed, or Ongoing.
· Process Monitor: This helps to show the run definition as defined in the process modeling framework. There are four icons in the Process Monitor as follows:
§ PMF
Launch: Click View 
to
view the Process flow associated with the selected run.
§ Request
Report Flag: To request for a Reporting Run, select an Execution
ID in the Process Execution Summary page and click the Request Report
Flag 
.
A dialog box will appear for you to input your comments. Click Submit
and the status of this Run is displayed in the Reporting Flag section.
Only a successful execution can be requested for reporting. For the selected
Run and Execution date, there can be only one reporting flag.
§ Approve
Report Flag: After submitting the Reporting Run in the earlier
section, the Approve Report Flag 
is
enabled. When you click the Approve Report Flag, a dialog box is displayed
with User Comments and Approver Comments. The Approver can update the
comments in the Approver Comments field and then click Approve or Reject.
§ Override
Report Flag: Any reporting execution can be overwritten with another
execution. Select a successfully triggered batch in the Process Execution
Summary page. The Override Report Flag 
is enabled if an
execution is already marked as a Reporting Flag. You can override the
execution by updating your comments. This must be approved by the approver
and the procedure is similar to the procedure detailed in the Approve
Report Flag for a Run section.
To request, approve, and override a flag for the process execution, perform the following steps:
1. Navigate to Oracle Financial Services Regulatory Reporting for Reserve Bank of India and select Process Execution Summary.
Figure 8: Process Execution Summary Page
2. Scroll towards the right and click Filter, select the Run Pipeline from the available pipeline selection list. Click OK.
Figure 9: Process Execution Summary Filter Search Result Pane
3. Scroll towards
the right and click View in the Process Name
row.
4. Select Request
Report Flag to
request a report flag for the selected run execution.
5. Enter information in the Comments field and click Submit. The request report flag for a run is saved successfully.
To approve the report flag, perform the following steps:
1. Navigate to the Process Execution Summary page and select the process name for which the report flag must be approved.
2. Click Approve
to
approve the request.
3. Enter the information in the Approve Request Flag page.
4. Click Approve to approve the requested report flag.
To override the report flag for a successful run, perform the following steps:
1. Navigate to the Process Execution Summary page and select the process name for which the report flag must be overridden.
2. Click Override
Report Flag to
override the report flag.
3. Enter the information in the Override Report Flag window.
4. Click Override to override the requested report flag.
5. Click Approve
Report Flag to
approve the override report flag request.
6. Enter the information in the Approver Comments field and click Approve and the report flag is overridden successfully.
To execute the batch to resave derived entities, follow the below steps:
1. Navigate Financial Services Data Foundation, then select Operations, and then select Batch Execution.
2. Select the batch <<INFODOM>>_RBI_<<REPORT NAME>>_RESAVEDE to resave all the DEs used in that <<REPORT NAME>>.
Figure 10: Batch Execution Screen
3. Monitor the status of the batch using the Batch Monitor link.
Figure 11: Batch Monitor Screen
4. The batches available for this release are:
RESAVE Batch |
Description |
|---|---|
<<INFODOM>>_RBI_ADJUSTMENT_RESAVEDE |
This batch resaves the RRS RBI ADJUSTMENT Derived Entities |
<<INFODOM>>_RBI_BSRII_RESAVEDE |
This batch resaves the RRS RBI BSRII Derived Entities |
<<INFODOM>>_RBI_BSRVII_RESAVEDE |
This batch resaves the RRS RBI BSRVII Derived Entities |
<<INFODOM>>_RBI_CICDP_RESAVEDE |
This batch resaves the RRS RBI CICDP Derived Entities |
<<INFODOM>>_RBI_CRILC_RESAVEDE |
This batch resaves the RRS RBI CRILC Derived Entities |
<<INFODOM>>_RBI_CUSTAT_RESAVEDE |
This batch resaves the RRS RBI CUSTAT Derived Entities |
<<INFODOM>>_RBI_DSB3ROR_RESAVEDE |
This batch resaves the RRS RBI DSB3ROR Derived Entities |
<<INFODOM>>_RBI_DSBIALE_RESAVEDE |
This batch resaves the RRS RBI DSBIALE Derived Entities |
<<INFODOM>>_RBI_EXPI_RESAVEDE |
This batch resaves the RRS RBI EXPI Derived Entities |
<<INFODOM>>_RBI_FORMAS42_RESAVEDE |
This batch resaves the RRS RBI FORMAS42 Derived Entities |
<<INFODOM>>_RBI_FORMVIII_RESAVEDE |
This batch resaves the RRS RBI FORMVIII Derived Entities |
<<INFODOM>>_RBI_FORMX_RESAVEDE |
This batch resaves the RRS RBI FORMX Derived Entities |
<<INFODOM>>_RBI_GTCAII_RESAVEDE |
This batch resaves the RRS RBI GTCAII Derived Entities |
<<INFODOM>>_RBI_IRS_RESAVEDE |
This batch resaves the RRS RBI IRS Derived Entities |
<<INFODOM>>_RBI_LCRBLR_RESAVEDE |
This batch resaves the RRS RBI LCRBLR Derived Entities |
<<INFODOM>>_RBI_LEVRATIO_RESAVEDE |
This batch resaves the RRS RBI Leverage Ratio Derived Entities |
<<INFODOM>>_RBI_LR_RESAVEDE |
This batch resaves the RRS RBI LR Derived Entities |
<<INFODOM>>_RBI_PCSTAT_RESAVEDE |
This batch resaves the RRS RBI PCSTAT Derived Entities |
<<INFODOM>>_RBI_RAQ_RESAVEDE |
This batch resaves the RRS RBI RAQ Derived Entities |
<<INFODOM>>_RBI_RBSIXBRL_RESAVEDE |
This batch resaves the RRS RBI RBSIXBRL Derived Entities |
<<INFODOM>>_RBI_RBSTR1_RESAVEDE |
This batch resaves the RRS RBI RBSTR1 Derived Entities |
<<INFODOM>>_RBI_RBSTR3_RESAVEDE |
This batch resaves the RRS RBI RBSTR3 Derived Entities |
<<INFODOM>>_RBI_RCAIII_RESAVEDE |
This batch resaves the RRS RBI RCAIII Derived Entities |
<<INFODOM>>_RBI_RETCGR_RESAVEDE |
This batch resaves the RRS RBI RETCGR Derived Entities |
<<INFODOM>>_RBI_RLC_RESAVEDE |
This batch resaves the RRS RBI RLC Derived Entities |
<<INFODOM>>_RBI_SAQLO1_RESAVEDE |
This batch resaves the RRS RBI SAQLO1 Derived Entities |
<<INFODOM>>_RBI_SAQLO2_RESAVEDE |
This batch resaves the RRS RBI SAQLO2 Derived Entities |
<<INFODOM>>_RBI_SLIPPAGE_RESAVEDE |
This batch resaves the RRS RBI SLIPPAGE Derived Entities |
<<INFODOM>>_RBI_SLR_RESAVEDE |
This batch resaves the RRS RBI SLR Derived Entities |
To execute the batch to refresh derived entities, follow the below steps:
1. Navigate to Financial Services Data Foundation, then select Operations, and then select Batch Execution.
2. Select the batch <<INFODOM>>_RBI_<<REPORT NAME>>_REFRESH to refresh all the DEs used in that <<REPORT NAME>>.
REFRESH Batch |
Description |
|---|---|
<<INFODOM>>_RBI_ADJUSTMENT_REFRESH |
This batch refreshes the RRS RBI ADJUSTMENT Derived Entities |
<<INFODOM>>_RBI_BSRII_REFRESH |
This batch refreshes the RRS RBI BSRII Derived Entities |
<<INFODOM>>_RBI_BSRVII_REFRESH |
This batch refreshes the RRS RBI BSRVII Derived Entities |
<<INFODOM>>_RBI_CICDP_REFRESH |
This batch refreshes the RRS RBI CICDP Derived Entities |
<<INFODOM>>_RBI_CRILC_REFRESH |
This batch refreshes the RRS RBI CRILC Derived Entities |
<<INFODOM>>_RBI_CUSTAT_REFRESH |
This batch refreshes the RRS RBI CUSTAT Derived Entities |
<<INFODOM>>_RBI_DSB3ROR_REFRESH |
This batch refreshes the RRS RBI DSB3ROR Derived Entities |
<<INFODOM>>_RBI_DSBIALE_REFRESH |
This batch refreshes the RRS RBI DSBIALE Derived Entities |
<<INFODOM>>_RBI_EXPI_REFRESH |
This batch refreshes the RRS RBI EXPI Derived Entities |
<<INFODOM>>_RBI_FORMAS42_REFRESH |
This batch refreshes the RRS RBI FORMAS42 Derived Entities |
<<INFODOM>>_RBI_FORMVIII_REFRESH |
This batch refreshes the RRS RBI FORMVIII Derived Entities |
<<INFODOM>>_RBI_FORMX_REFRESH |
This batch refreshes the RRS RBI FORMX Derived Entities |
<<INFODOM>>_RBI_GTCAII_REFRESH |
This batch refreshes the RRS RBI GTCAII Derived Entities |
<<INFODOM>>_RBI_IRS_REFRESH |
This batch refreshes the RRS RBI IRS Derived Entities |
<<INFODOM>>_RBI_LCRBLR_REFRESH |
This batch refreshes the RRS RBI LCRBLR Derived Entities |
<<INFODOM>>_RBI_LEVRATIO_REFRESH |
This batch refreshes the RRS RBI Leverage Ratio Derived Entities |
<<INFODOM>>_RBI_LR_REFRESH |
This batch refreshes the RRS RBI LR Derived Entities |
<<INFODOM>>_RBI_PCSTAT_REFRESH |
This batch refreshes the RRS RBI PCSTAT Derived Entities |
<<INFODOM>>_RBI_RAQ_REFRESH |
This batch refreshes the RRS RBI RAQ Derived Entities |
<<INFODOM>>_RBI_RBSIXBRL_REFRESH |
This batch refreshes the RRS RBI RBSIXBRL Derived Entities |
<<INFODOM>>_RBI_RBSTR1_REFRESH |
This batch refreshes the RRS RBI RBSTR1 Derived Entities |
<<INFODOM>>_RBI_RBSTR3_REFRESH |
This batch refreshes the RRS RBI RBSTR3 Derived Entities |
<<INFODOM>>_RBI_RCAIII_REFRESH |
This batch refreshes the RRS RBI RCAIII Derived Entities |
<<INFODOM>>_RBI_RETCGR_REFRESH |
This batch refreshes the RRS RBI RETCGR Derived Entities |
<<INFODOM>>_RBI_RLC_REFRESH |
This batch refreshes the RRS RBI RLC Derived Entities |
<<INFODOM>>_RBI_SAQLO1_REFRESH |
This batch refreshes the RRS RBI SAQLO1 Derived Entities |
<<INFODOM>>_RBI_SAQLO2_REFRESH |
This batch refreshes the RRS RBI SAQLO2 Derived Entities |
<<INFODOM>>_RBI_SLIPPAGE_REFRESH |
This batch refreshes the RRS RBI SLIPPAGE Derived Entities |
<<INFODOM>>_RBI_SLR_REFRESH |
This batch refreshes the RRS RBI SLR Derived Entities |
Drill down functionality enables the user to view the accounts included in the aggregation. Following these steps to drill down from AgileREPORTER to OFSAA:
1. Log in to the AgileREPORTER.
Figure 12: AgileREPORTER Login Page
2. The user can view the list of reports on the main page. Click any report name in the Returns column, for example, FORMVIII.
Figure 13: AgileREPORTER Main Page
3. The schedule list is displayed on the left-hand side. Click any schedule name, for example, AnnexI_P2.
Figure 14: AgileREPORTER Page Displaying List of Schedules
4. Click any cell to drill down.
Figure 15: AgileREPORTER Schedule Details Page
5. Error! Reference source not found. displays drill down for the first cell in Column F. The OFSAA icon is displayed. Click the OFSAA icon to view how this cell was populated from OFSAA results. You are redirected to the OFSAA drill-down page.
Figure 16: AgileREPORTER Drill Down
6. Click the OFSAA icon, to view how this cell was populated (provides information about the amounts reported in a cell) from OFSAA results. You are redirected to the OFSAA Drill down page.
7. Click the Column Selector button on the header of the second table.
NOTE:
Select the required Data Source, from the Available
Attributes list and click Move 
.
You can press the Ctrl key and click Move for
multiple selections to map all the listed Data Sources to the application.
Select the required Data Source, from the Selected
Attributes list and click Remove 
to
remove the mapped Data Source from the application.
8. Expand Dataset and select the Attribute to be shown in the Drill down. Click Apply.
9. Click Export to export the report details.
The Retrieve Return functionality in AgileREPORTER fetches data from OFSAA derived entities and embeds them on AgileREPORTER templates. This runs the decision table process in Lombard Risk. You can view the relevant OFSAA data on various schedules of the AgileREPORTER using this functionality.
Figure 17: Retrieve Returns Page
This section helps you to navigate through the Metadata Browser and guides you in tracing the source of the metadata. The Metadata Browser function allows you to view and analyze all aspects of the metadata used in the OFSAAI. It provides extensive browsing capabilities of metadata, helps in tracking the impact of changes to metadata, and trace through to the source of originating data.
Metadata Browser (Object and Application View) provides a common repository of metadata objects created in OFSAAI and applications hosted in OFSAAI. Using this view, you can identify the usage of base objects in higher-level objects and the mapping of Objects to Application, thus enabling traceability. It also allows you to view the data flow and the workflow of the application and understand the usage of objects within the application.
The new visualization of Metadata Browser (MDB) supports the Application view and Object view. In the Application view, you can browse through the metadata created using the applications hosted in OFSAAI. In the Object view, you can view the metadata created in OFSAAI.
To access the Metadata Browser (Object and Application View), your role must be mapped to the SCR_MDB function.
Analysts review the metadata used for a particular report schedule to verify the data. Data verification can require looking for metadata used in a given schedule or it can be scheduled in which particular metadata is used. Data Analysts and Reporting Analysts perform the report verification. Metadata refers to business measures, hierarchies, data sets, derived entities used for a given schedule.
To use MDB for schedule-wise metadata, and to use MDB for metadata wise schedule, identify the metadata used, perform the following steps:
1. You can verify the data for related data elements in results using this information. Navigate to Catalog of Objects, select OFSAA Metamodel, select Reporting Metadata, and then select Reports. The MDB Reporting Metadata screen is displayed.
Figure 18: MDB - Reporting Metadata Page
2. Click the object view SLRP9 to view the list of schedules. The Reporting Metadata Schedule View page is displayed.
Figure 19: MDB - Reporting Metadata - Schedule View
You can view the following information in the Schedule Details page:
§ Depends On: This section displays the metadata used in a given schedule.
§ Used In: This section displays the Reports in which this schedule is used.
§ Applications: This section displays the applications in which this schedule is used.
3. Click Details to view the dependency and usage information such as the Object Name and the Object Type.
Figure 20: MDB - Reporting Metadata - Schedule View 1
4. From the Schedule View page, click the Dependency tab to view the report tree structure.
Figure 21: MDB - Reporting Metadata Tree Structure Page
Starting from common metadata used across the application, you may want to know the list of reports or derived entities this metadata has used. Let us take an example of a measure. To identify how value is computed, perform the following steps to trace it back to the metadata.
This section provides information on the Business metadata objects which include Base Metadata and Derived Metadata.
The following are the steps to perform to view the Base metadata details. For example, Measures.
1. To view the measures, navigate to Catalog of Objects, select OFSAA Metamodel, select Business Metadata, select Base Metadata, and then select Measures. The MDB Business Metadata page is displayed.
Figure 22: MDB - Business Metadata - Measure View Page
2. Click the Measure that you wish to view. The MDB Business Metadata Measure Details page is displayed.
Figure 23: MDB - Business Metadata Measure Details Page
You can view the following information on this page:
§ Measure Properties: It provides information on the properties of Business measures. For example, aggregation function, Measure Data Type, Business Exclusions, Filter, and Rollup Type.
§ It depends on: This section displays all the object names and their types, such as Entities, Columns, and so on.
§ Used In: This section displays the Objects in which this schedule is used.
§ Applications: This section displays the applications in which this schedule is used.
3. Click Details to view the measure dependency and usage information.
Figure 24: Measure Dependency and Usage Details Page
4. From the Measure Details page, click the Dependency tab to view the measure tree structure.
Figure 25: Business Metadata Measure Tree Page
NOTE:
The similar steps as mentioned in this section are applicable for other metadata such as Business Metadata (Hierarchies, Measures, Variables, and so on) and Derived Metadata (Dimensions, Filters, and so on), Process Metadata (Process, Rules, and so on) and Data Foundation (Target Model, Sources, Connectors, and so on).
The following are the steps to perform to view the Derived Metadata details. For example, Derived Entities.
1. To view the schedule-wise derived entities, navigate to Catalog of Objects, select OFSAA Metamodel, select Business Metadata, select Derived Metadata, and then select Derived Entities.
Figure 26: MDB - Business Metadata Derived Entity Page
2. Click the Derived Entity that you wish to view. The Derived Entity Details page is displayed.
Figure 27: Derived Entity Details Page
You can view the following information on this page:
§ Derived Entity Properties: It provides information on properties of derived entities, such as Source Type, Aggregate Flag, and Materialized View.
§ It depends on: This section displays all the object names and their types, such as Dataset, Hierarchy, and so on.
§ Used In: This section displays the Objects in which this schedule is used.
§ Applications: This section displays the applications in which this schedule is used.
3. Click Details to view the derived entity dependency and usage information.
Figure 28: Derived Entity Dependency and Usage Page
4. From the Derived Entity Details page, click the Dependency tab to view the Derived Entity tree structure.
Figure 29: Derived Entity Tree Structure Page
For more information about the Metadata and its usage, see the OFSAA Metadata Browser User Guide.