Oracle Analytics Publisher Data Flow

If you run the report from the Oracle Argus Safety UI directly, the system passes only the Enterprise ID, Report Configuration, Print As, and Reg Report ID parameters. Other parameters are picked up if no default values are provided at the BIP level.

1. Navigate to the BIP report that displays the parameter page.
2. Select the mandatory parameter ENTERPRISE ID.

   This selection executes the associated LOV query.

   The selected value is verified by the query present in the CFG_RPT_AGG_PARMS table for the parameter.

   After verification, the enterprise ID is set for the session.

3. Select the mandatory parameter REPORT_CONFIGURATION.

   This parameter determines whether the report will be in the Data Lock Point (DLP).

   If the case series parameters are not selected, the default case series associated with this report configuration is set automatically.

   This parameter is an LOV and the query present in the CFG_RPT_AGG_PARMS table for the parameter validates the selected value.

4. Input the other parameters, and click Submit.

   This invokes the Before data trigger that calls the f_beforedata function of the pkg_agg_rpt package.

This function:

1. Sets up all parameter values from the Oracle Analytics Publisher to Package variables.
2. Validates whether the mandatory parameters have been supplied.
3. Checks if the user's access has expired.
4. Determines whether the BIP report call is made from the Oracle Argus Safety UI or from the BIP console.
5. Handles case, study, or site security.
6. Finds the BIP report job.
7. Inserts records in CMN_REG_REPORTS.
8. Inserts records in PER_RPT_QUEUE and PER_RPT_STATUS.
9. Obtains the default values of all parameters using CFG_RPT_AGG_PARAMS.
10. Determines whether the report is DLP.
11. Populates the data for listedness, drugs, events, event to drugs, and case data.
12. After the case data has been populated, fills in the health authority details and drug names.
13. Sets up the lexical parameters, if any.
14. Based on the persist data common switches, fills in the data for MART tables:
    1. PERSIST_BIP_DATA: whether data from GTT needs to be moved to RM tables.
    2. PERSIST_DURATION: number of days for which the data is to be left at RM tables.

This results in the package filling in the complete data for data sets.

1. After the PLSQL code is complete, the BI report internally generates the data XML, renders the pages, and stores the output in its repository data.
2. The database job calls the pkg_rpt_util.p_fetchrptoutput function, which obtains the list of reports that are run based on the RPT_AGG_BIP_JOB table.
3. The database then queries the BIP Metadata Repository (MDR) and verifies that the report is complete. If the report has failed, the database updates the failure status and proceeds to the next report.
4. If the report is successful, the database checks if the Draft/Final tables are updated.
5. The system copies the report output blob to the reporting tables. It updates CMN_REG_REPORTS and the corresponding records in the PER_RPT_QUEUE and PER_RPT_STATUS tables.

After this operation is complete, you can view the report output in BIP and Oracle Argus Safety.

Note:

The report output in BIP might be completed earlier than in Oracle Argus Safety UI. This is because the job picks up the output and pushes it to the Argus database.