Results for “p_completion_text”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_RS_RUN_HISTORY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the BIS (Business Intelligence System) product family, whose objects underpin the Oracle Daily Business Intelligence and E-Business Intelligence reporting infrastructure. Specifically, this package manages the persistence of run history records for request sets that refresh BIS reporting structures.

In the ETRM metadata the package is classified as an "OTHER" API, meaning it is not exposed as a formally supported public interface but functions as an internal data access layer. It is declared with AUTHID CURRENT_USER, so execution privileges are resolved against the calling schema rather than the definer. Its central business purpose is to record when a request-set refresh was submitted, when it completed, and its phase and status codes, thereby allowing administrators and reporting components to audit and review historical refresh activity. The header comment indicates the source file is BISRSTHS.pls, last revised in June 2005, and the package is marked "noship," meaning it is not shipped directly to customers but deployed as a dependency of the BIS schema objects.

Key Procedures and Functions

• Insert_Row — A procedure that creates a new run history record for a request set refresh. It captures identifiers for the request set and its application, the request identifier, the refresh type, start and completion dates, phase and status codes, standard audit columns, and a completion text field. This is the primary entry point for recording a refresh execution.
• Update_Row — A function returning a BOOLEAN that modifies an existing run history record. It accepts the request identifier as the key and permits updating request set identifiers, dates, phase and status codes, audit columns, and completion text. Defaulted parameters allow callers to update only the attributes that have changed during a refresh cycle.
• Delete_Row — A procedure that removes run history records, accepting a last update date parameter used to scope the deletion. This supports housekeeping and purging of obsolete history rows.

The documented interface comprises three routines in total, consistent with the ETRM procedure list for this package.

Tables Accessed

The package operates against a single base table, BIS_RS_RUN_HISTORY, referenced through an APPS synonym. This table stores the run history of request set refreshes: request set and application identifiers, request identifiers, refresh type, start and completion timestamps, phase and status codes, completion text, and the standard who-columns (creation date, created by, last update date, last updated by). Insert_Row writes new rows to this table, Update_Row amends them in place as a refresh progresses or completes, and Delete_Row purges rows. No other tables are documented as referenced by this package.

Usage Notes

The package is invoked programmatically rather than interactively. Typical invocation paths include the BIS request-set refresh concurrent programs, which call Insert_Row when a refresh is submitted and Update_Row as phase and status codes change, and the BIS administration forms, which read run history rows to present refresh status to users. The ETRM metadata records that the package is referenced by one other package, indicating a layered dependency within the BIS code stack. Custom code should avoid calling these routines directly because the API is classified as OTHER and is subject to change across patch levels; supported extensions should instead use documented BIS public interfaces. The defaulted parameters on Update_Row and the AUTHID CURRENT_USER clause both reflect the package's role as an internal utility driven by sibling BIS components.