Results for “program_name”

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

Overview

GHR_PROCESS_LOG_V2 is a database view owned by the APPS schema in Oracle E-Business Suite, documented under the GHR - US Federal Human Resources product family. ETRM records its status as VALID, and it is catalogued as an object of type VIEW. As stated in the object description, the view is based on the GHR_PROCESS_LOG table and is used by the process log form. Its purpose is therefore not to introduce new business data but to project a distinct, de-duplicated subset of the process log records into the shape required by the concurrent processing log user interface.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view sits between the physical log table populated by GHR processes and the Forms-based process log form that end users and administrators invoke to review the outcome of those processes. Because it exposes only three columns, it is deliberately narrow: it supports browsing and filtering of logged process runs rather than detailed diagnostic inspection of every message row. The DISTINCT keyword in the defining query means the view collapses repeated combinations of program name, log date, and message name into a single row, giving the form a concise summary list instead of a verbose event stream. Reporting and integration consumers that need the same summarized perspective can query the view directly, though it is first and foremost an application-support object.

Underlying Base Objects

ETRM documents exactly one referenced base object for this view: GHR_PROCESS_LOG, which is recorded as a SYNONYM in the metadata extract. The synonym ultimately resolves to the underlying application table, since the view text itself selects from GHR_PROCESS_LOG. The view definition is:

• SELECT DISTINCT PROGRAM_NAME, TRUNC(LOG_DATE) LOG_DATE, MESSAGE_NAME FROM GHR_PROCESS_LOG

The relationship to the base object is therefore a straightforward one-to-many projection: every row returned by the view is derived from one or more rows in GHR_PROCESS_LOG. No joins, unions, or subqueries are documented, and no additional base tables are referenced. The single transformation applied by the view is twofold — column restriction and date normalization via TRUNC — with DISTINCT row elimination applied across the resulting three-column projection. Because the synonym layer sits beneath the view, any re-pointing of GHR_PROCESS_LOG at the database level would transparently affect the view's contents, which is standard behavior for APPS-owned synonyms in EBS.

Key Columns

The view exposes three columns, each documented in the ETRM column listing. Their meanings are consistent with the underlying log table:

• PROGRAM_NAME — Identifies the concurrent program or GHR process that produced the log entry. This is the primary grouping attribute used by the process log form to separate one process run from another.
• LOG_DATE — The date of the log entry, exposed after TRUNC so that the time component is stripped. This normalization is what allows DISTINCT to collapse multiple same-day entries for a program into a single row, and it supports date-range filtering in the form.
• MESSAGE_NAME — The message identifier associated with the logged event, typically resolving to an Oracle message via the message dictionary. It conveys the nature of the logged condition rather than free-form text.

Because the column alias LOG_DATE is applied to TRUNC(LOG_DATE), consumers should note that no time-of-day information is available from this view. Precision beyond the day must be obtained from the base table directly.

Common Use Cases and Queries

The principal consumer is the GHR process log form, which uses the view to render a compact list of program runs and the messages they emitted on a given day. Beyond the form, the view is useful for monitoring and light reporting. Typical patterns include listing all processes that logged messages on a specific date, tracking which messages a given program has raised over time, and identifying days on which particular processes produced output. Representative statements include:

• SELECT program_name, log_date, message_name FROM ghr_process_log_v2 WHERE log_date = TRUNC(SYSDATE);
• SELECT DISTINCT program_name FROM ghr_process_log_v2 WHERE message_name = :p_message_name;
• SELECT program_name, log_date, COUNT(*) FROM ghr_process_log_v2 GROUP BY program_name, log_date ORDER BY log_date DESC;

Because the view returns summarized data, it is unsuitable for reconstructing the exact sequence of events within a run; for chronological reconstruction or timestamp-level auditing, query GHR_PROCESS_LOG directly. Query performance is generally acceptable for form-level browsing, but the DISTINCT and TRUNC operations mean the view will not benefit from indexes defined on the raw column, so large-volume reporting should be planned with that limitation in mind.