Search Results p_phase_code

Overview

The APPS.BIS_RS_PROG_RUN_HISTORY_PKG package body provides the data-access layer for the BIS_RS_PROG_RUN_HISTORY table, a repository that records the lifecycle of concurrent program and request-set executions within Oracle E-Business Suite. The package encapsulates the standard insert, update, and delete operations required to maintain an audit trail of request activity, capturing both the operational status and the phase of each request as it moves through the concurrent manager. In Oracle EBS 12.1.1 and 12.2.2, this table and its maintenance package are relevant to the Oracle Business Intelligence System (BIS) reporting and collection framework, where historical run information supports performance analysis, diagnostics, and reporting on program execution.

The package is classified as an OTHER API, meaning it is an internal utility rather than a formally published public API. Its header identifies it as a development object (BISPRTHB.pls, version 120.0), and it is referenced by one other package, indicating its role as a supporting component rather than a top-level integration point.

Key Procedures and Functions

The documented package exposes three procedures:

• INSERT_ROW — Inserts a new execution-history record into BIS_RS_PROG_RUN_HISTORY. It accepts the request-set request ID, stage request ID, request ID, program ID, program application ID, status code, phase code, start and completion dates, creation and last-update audit columns, and a completion-text value. The routine performs a COMMIT after the insertion and traps exceptions through BIS_COLLECTION_UTILITIES.put_line before re-raising the error.
• UPDATE_ROW — Updates an existing history record. It employs default NULL values for several optional parameters (program ID, program application ID, status code, phase code, completion date, and completion text) and dynamically builds a SET clause, allowing callers to update only selected columns. It returns a BOOLEAN indicating success or failure and validates that the mandatory keys — set request ID, request ID, last-update date, and last-updated-by — are not null before proceeding.
• DELETE_ROW — Removes a history record from the table. The metadata confirms its existence as the third documented program unit, consistent with the insert/update/delete triad typical of EBS table-maintenance packages.

The parameter p_phase_code appears in the insert signature and the update signature, corresponding to the Phase_Code column of the history table. In EBS concurrent processing, phase codes represent the broad stage of a request (for example, Pending, Running, Completed, Inactive), distinguishing it from the finer-grained status code.

Tables Accessed

The package operates exclusively on BIS_RS_PROG_RUN_HISTORY, accessed through the APPS synonym. This table stores one row per recorded program or request-set execution, keyed by a combination of set request ID and request ID. The insert routine populates all columns; the update routine modifies selected columns dynamically. No other base tables are referenced within the documented source.

Usage Notes

Because this package is classified as OTHER and is referenced by only one other package, it is best treated as an internal helper rather than a general-purpose integration API. It is typically invoked by the collection or reporting logic that populates the BIS run-history data, not directly by forms or standard concurrent program submissions. Custom developers should exercise caution: the INSERT_ROW routine issues an unconditional COMMIT, which may interfere with surrounding transactional logic, and UPDATE_ROW builds dynamic SQL, requiring careful handling of the nullable parameters. Where an equivalent supported API exists in 12.2.2, that interface should be preferred over direct calls to this package.