Search Results pqh_gsp_process_log




Overview
Explore in AI Chat

Overview

PQH_GSP_PROCESS_LOG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an OTHER API within the ETRM repository. Its documented header declares AUTHID CURRENT_USER, meaning every procedure executes with the privileges of the calling schema rather than the definer, so all referenced objects must be resolvable through APPS synonyms or grants held by the invoker.

The package belongs to the PQH (Public Sector/Position Management) family and serves a logging and audit role for the GSP processing flow. Its name and procedures indicate that it captures lifecycle information for batch or transactional processing runs, writing structured rows into PQH_PROCESS_LOG so that later reconciliation, error diagnosis, and audit reporting can be performed. The source header identifies revision 115.2, dated 2003/10/10, which confirms it is a long-standing component carried forward unchanged into the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented interface exposes exactly two procedures.

  • START_LOG — Initializes a log entry. It accepts an input transaction identifier, a transaction name, and a module code. Invoking it establishes the parent log record that subsequent detail rows attach to, giving the run a header-level identity (who or what ran, which module, and under which transaction ID).
  • LOG_PROCESS_DTLS — Records detail-level entries against an established log. Its parameters describe a master transaction ID, a subordinate transaction ID, a module code, an optional context string, a message type code, message text, and an effective date. This procedure is the workhorse for capturing informational, warning, and error messages produced while processing assignments, grades, or progression steps.

No functions are documented. Parameter lists must not be assumed beyond what the header shows; callers should treat the procedure signatures as published and stable.

Tables Accessed

The repository lists the following objects referenced through APPS synonyms:

  • PQH_PROCESS_LOG — the primary target. Both procedures write here; START_LOG creates the header row and LOG_PROCESS_DTLS appends detail rows.
  • PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — the core HR assignment and person entities, read to associate log entries with the employee and assignment being processed.
  • PER_GRADES and PER_SPINAL_POINTS — grade and spinal point definitions used in grade progression (GSP) evaluation.
  • BEN_PGM_F and BEN_COPY_ENTITY_RESULTS — benefits program and entity-copy result tables, indicating integration with benefits processing triggered alongside or derived from GSP activity.

Usage Notes

The package is referenced by seven other packages, which is the dominant consumption pattern: internal PQH and benefits packages call START_LOG when a processing unit begins and LOG_PROCESS_DTLS as each step or error occurs. It is not exposed as a form-level user API and is not intended for direct end-user invocation.

Typical invocation contexts include concurrent programs that perform grade step progression, benefits enrollment or copy routines, and custom extensions that must record their activity in the same audit trail. Because of AUTHID CURRENT_USER, custom callers must reference the procedures with the APPS prefix (for example, APPS.PQH_GSP_PROCESS_LOG.START_LOG) and ensure the invoker holds execute privilege and synonym access to PQH_PROCESS_LOG. The optional p_Context parameter on LOG_PROCESS_DTLS allows callers to pass free-form diagnostic context. In 12.1.1 and 12.2.2, the object remains an APPS-owned, non-versioned package with no online patching-specific differences beyond the standard APPS synonym and editioning handling applied to all seeded code.