Search Results insert_findings_increment_load




Overview
Explore in AI Chat

Overview

APPS.RCI_OPEN_REMED_SUMM_PKG is a PL/SQL package in the Oracle E-Business Suite (EBS) environment, declared with AUTHID CURRENT_USER. It forms part of Oracle's Enterprise Risk and Compliance (ETRM / GRC) module related to open findings and remediation activities. The package's core purpose is to support reporting and dashboard functionality, particularly for Oracle Daily Business Intelligence (DBI) and Profitability Manager (BIS_PMV) style page regions, by exposing KPI and detail result sets, as well as providing data load procedures to populate summary and transactional tables.

The package serves a dual role: it acts as a data provider for interactive dashboard pages (returning SQL and output via the BIS_QUERY_ATTRIBUTES_TBL structure), and as the backend for concurrent program data loads of findings and remediation records. The naming convention "OPEN_REMED_SUMM" indicates that it summarizes open remediation activities for reporting.

Key Procedures and Functions

The documented procedures include:

  • GET_KPI — Returns the source SQL and output attributes needed to render the top-level Key Performance Indicator region for the open remediation summary dashboard.
  • GET_OPEN_REMEDIATION_RESULT — Provides the SQL and result attributes for the open remediation results region.
  • GET_FINDINGS_DETAILS — Supplies the SQL and attributes to populate the detailed findings region.
  • GET_REMEDIATIONS_DETAILS — Supplies the SQL and attributes to populate the detailed remediation actions region.
  • OPEN_REMED_ACT_INITIAL_LOAD — Concurrent program entry point used to perform the initial full load of open remediation activity data.
  • OPEN_REMED_ACT_INCREMENT_LOAD / OPEN_REMED_ACT_INCREMENTAL_LOAD — Concurrent program entry points used to perform incremental (delta) loads of remediation activity data. The presence of both names in the source header suggests a documented and commented variant, with the active version reflecting the production interface.
  • FN_GET_BUCKET_ID — Calculates aging bucket identifiers based on an input age in days, returning four bucket values used for aging analysis of open items.
  • GET_LAST_DAY — Returns a formatted last-day value based on a supplied date identifier and type, used for period-bucketed reporting.
  • INSERT_FINDINGS_INITIAL_LOAD / INSERT_FINDINGS_INCREMENT_LOAD — Populate the findings fact tables during initial and incremental loads respectively.
  • INSERT_REMEDS_INITIAL_LOAD / INSERT_REMEDS_INCREMENT_LOAD — Populate the remediation fact tables during initial and incremental loads respectively.
  • CHECK_INITIAL_LOAD_SETUP — Validates that all prerequisites and setup conditions are met before an initial load can run. This is the procedure most relevant to the search term "check_initial_load_setup," and is typically invoked to prevent initial loads from executing when the environment is not properly configured.
  • ERR_MESG — A helper used to return standardized error messages to the calling concurrent program.

Tables Accessed

The package reads and writes via APPS synonyms. The RCI_OPEN_FINDINGS_F and RCI_OPEN_REMEDIATIONS_F tables are the primary fact tables for findings and remediation records, populated by the insert procedures and read by the GET_* detail procedures. RCI_DR_INC supports incremental data retrieval. Engineering change data is sourced from ENG_ENGINEERING_CHANGES, ENG_CHANGE_SUBJECTS, and ENG_CHANGE_OBJ_RELATIONSHIPS, linking remediation activities to engineering change orders. PLITBLM is a PL/SQL index-by table type used internally, not a physical data table.

Usage Notes

The GET_* procedures are invoked by Oracle DBI/BIS dashboard pages to dynamically build SQL for KPI and detail regions. The load procedures (OPEN_REMED_ACT_*_LOAD, INSERT_*_LOAD, CHECK_INITIAL_LOAD_SETUP) are typically registered as concurrent programs and executed from the Submit Requests form or via scheduled concurrent requests. CHECK_INITIAL_LOAD_SETUP should be run first when preparing an initial load, as it confirms prerequisite setup. Custom integrations should call these procedures only through the concurrent program framework, since they use the standard errbuf/retcode interface. Because the package is referenced by no other documented packages, it is a leaf-level reporting and load component rather than a shared utility.