17.1 Prerequisites

The following executions must be performed before using the Metadata Report utility:

1. Before executing MDB Publish and Data Elements Wrapper Batch, ensure the following:
   1. Tablespace Requirement:
      1. Ensure that the USERS tablespace have a minimum of 150 GB available.
      2. Ensure that the TEMP tablespace is a minimum of 45 GB available.
   2. Execute the following Gather Stat command for the mentioned tables:

      BEGIN 
      DBMS_STATS.GATHER_TABLE_STATS(USER, 'TABLE_NAME'); 
      END;

      1. Atomic Schema:

         FSI_M_CELL_DETAILS 
         FSI_DE_SEEDED_DIMENSIONS
         FSI_DE_TABLE_APPLICATION_MAP
         FSI_DE_PP_TABLE_LIST
         FSI_DE_METADATA_SEEDED_VW_MAP
         FSI_DE_PP_TABLE_REPORT_MAP
         Config Schema:
         AAI_OBJECT_B
         AAI_OBJECT_TL
         AAI_DMT_DEFINITION
         AAI_DMT_DEF_SOURCE_ENTITY
         AAI_DMT_MAPPING_DETAILS
         PR2_RULES_B
         PR2_RULE_MAP
         PR2_RULE_OBJECT
         PR2_RULE_OBJECT_MEMBER
         PR2_OBJECT_TL
         PR2_OBJECT_TRACE
         BATCH_MASTER
         BATCH_TASK_MASTER
         BATCH_PARAMETER_MASTER
         METADATA_MASTER
         METADATA_ELEMENT_MASTER
         METADATA_LOCALE_MASTER
         METADATA_TYPE_MASTER
         METADATA_ATTRIBUTE_MASTER

2. MDB Publish: To publish the MDB, follow these steps:
   1. Log in to Oracle Financial Services Analytical Applications interface with your credentials.
   2. From the LHS Menu, click Financial Services Data Foundation, and then click Metadata Browser.
   3. Click the Publish button on the Metadata Browser screen.

      Figure 17-1 Metadata Browser

      
      

      

      
      
   4. Click OK.
   5. Click the Refresh button to view the latest status.
3. After Executing MDB Publish and Data Element Wrapper Batch, ensure the following:
   1. Execute the following Gather Stat command for the mentioned tables:

      BEGIN 
      DBMS_STATS.GATHER_TABLE_STATS(USER, 'TABLE_NAME'); 
      END;

      1. Atomic Schema:

         FSI_DE_REPORT_LINEAGE_BASE
         FSI_DE_REPORT_LINEAGE_DETL
         FSI_DE_METADATA_TGT_MEMBER
         FSI_DE_METADATA_SRC_MEMBER
         FSI_DE_REPORT_TARGET_MEMBER
         FSI_DE_REPORT_SOURCE_MEMBER

4. Logs: MDB logs are generated under deployed area /Context_Name/logs/MDB_XXXX.log

   Data Elements Wrapper Execution: After MDB Publish is completed successfully with the message “Metadata publishing is finished.” in the /Context_Name/logs/MDB_XXXX.log, you must execute the Data Elements Utility with the following seeded batch to get the Data Lineage for each Metadata in OFSAA:

   <INFODOM>_POP_DATA_ELEMENTS_DGS

   This execution requires adequate tablespace. Ensure that your Atomic Schema is having enough table space in TEMP and USERS.

   1. Parameters used in <INFODOM>_POP_DATA_ELEMENTS_DGS Batch

      The default parameters used in the <INFODOM>_POP_DATA_ELEMENTS_DGS batch are:

      Excluding Irrelevant Data Flows from Lineage Reports: For each Run, some of the Data Mappings can be functionally irrelevant. For these cases for any Run, the customer can opt for removing these Data Flow from Lineage Reports as an exclusion by inputting the same in the FSI_DE_RUN_FLOW_REMOVAL table.

      Enabling Reports for REPORT Parsing: Every execution for REPORT Parsing requires a minimum of one Report to be enabled in the FSI_DE_POP_REPORT_LIST table in the Atomic Schema. By default, the following Reports are enabled for US FED Jurisdiction.

      Table 17-2 Dashboard ID Details

      DASHBOARD ID	JURISDICTION CODE	REPORT CODE	INCLUDE REPORT
      1	USFED	FRY-9C	Y
      2	USFED	FRY-9LP	Y
      3	USFED	FRY-11	Y
      4	USFED	FRY-11s	Y
      5	USFED	FR-2314	Y
      6	USFED	FR-2314s	Y
      7	USFED	FFIEC-031	Y
      8	USFED	FFIEC-041	Y
      9	USFED	FRY-7N	Y
      10	USFED	FRY-7NS	Y

      By Default All Dashboards are enabled and if you wish to parse particular Dashboards, modify the FSI_DE_POP_REPORT_LIST table in the Atomic Schema by enabling/disabling the “Include Report Column”.