Search Results refresh_mv_sql




Overview
Explore in AI Chat

Overview

The APPS.HRI_OLTP_CONC_MV package is a materialized view maintenance utility within the Oracle E-Business Suite Human Resources Intelligence (HRI) OLTP reporting schema. It belongs to the family of HRI OLTP concurrent processing objects that support the Oracle HRMS Analytics and Operational Reporting (Daily Business Intelligence) infrastructure. Its business function is to provide a programmatic, concurrent-safe mechanism for refreshing the materialized views that underpin HRMS analytic dashboards and operational reports. Rather than requiring administrators to issue ad hoc DBMS_MVIEW.REFRESH calls manually, the package encapsulates the refresh logic so that it can be scheduled and executed reliably as part of the standard concurrent manager workload in EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes two documented entry points:

  • REFRESH_MV — The primary refresh driver. This procedure performs the actual refresh of one or more HRI OLTP materialized views, orchestrating the refresh operation through the Oracle-supplied materialized view utilities. It is the procedure normally targeted when the object is invoked from a concurrent program or scheduled job.
  • REFRESH_MV_SQL — A companion routine that generates or executes the SQL required to carry out the materialized view refresh. It supports the main refresh driver by constructing the appropriate refresh statement, allowing the refresh to be executed in a controlled, dynamically-generated manner.

No parameter signatures are documented in the ETRM metadata; the procedures should therefore be treated as internal implementation routines whose exact call interface is governed by the package specification. Because the package is classified as OTHER (not a public or open API), it is not intended for direct customer invocation without Oracle guidance.

Tables Accessed

The package references the following database objects through APPS synonyms:

  • FND_ORACLE_USERID — The Oracle Applications user identifier table. This reference is consistent with the HRI OLTP pattern of identifying the schema context under which materialized view refresh should execute, ensuring the correct APPS-owned objects are addressed.
  • DBMS_MVIEW — The Oracle-supplied PL/SQL package that performs materialized view refresh operations. HRI_OLTP_CONC_MV delegates the underlying refresh work to DBMS_MVIEW, using it to execute complete, fast, or force refreshes as appropriate to the target views.

In addition, the package body depends on SYS.STANDARD, the standard PL/SQL package present in every Oracle database. The package is self-referencing (it appears in its own dependency list), which is typical of packages that call sibling routines within the same body.

Usage Notes

HRI_OLTP_CONC_MV is typically invoked in one of three ways:

  • Scheduled concurrent programs — The most common invocation path. Administrators define a concurrent program whose executable calls REFRESH_MV, then attach it to a request set or schedule so that HRI materialized views are refreshed on a recurring basis (for example, nightly or weekly).
  • HRI OLTP administration flows — During setup or maintenance of HRMS analytics, Oracle-provided concurrent requests and administrative responsibilities may call this package to bring the reporting views current.
  • Custom code and scripts — Because the package is classified as OTHER rather than a supported public API, direct calls should be made only when following Oracle-provided guidance or documented refresh procedures. The package is referenced by no other Oracle EBS package (referenced-by count: 0), confirming it is a leaf utility intended for scheduling rather than a shared library.

Given that the ETRM documentation for this object is sparse (package and package body entries are empty in the metadata), implementers should inspect the package specification in the target environment before invoking it, and should validate behavior separately on 12.1.1 and 12.2.2, since refresh infrastructure and HRI content differ between those releases. Standard practice is to run refreshes during off-peak windows, as materialized view refresh on HRI OLTP objects can be resource-intensive.