Search Results ghr_process_log_n1

Overview

The HR.GHR_PROCESS_LOG table is a core logging and audit table within the Oracle E-Business Suite (EBS) Global Human Resources (GHR) module for versions 12.1.1 and 12.2.2. It functions as a centralized repository for capturing detailed operational logs from various batch and background processes. Its primary role is to provide a persistent audit trail for critical HR operations, enabling system administrators and functional users to monitor process execution, diagnose errors, and verify the completion of automated tasks. As indicated by the metadata, it specifically logs information for processes such as Auto Within Grade Increases (WGI), future action processing, and mass personnel actions, which are essential for maintaining accurate and compliant employee records.

Key Information Stored

The table's structure is designed to capture both process context and output. The key columns include:

• PROCESS_LOG_ID: The mandatory primary key, uniquely identifying each log entry. This value is populated from the sequence GHR_PROCESS_LOG_S.
• PROGRAM_NAME: Identifies the specific batch program or process (e.g., a concurrent request) that generated the log entry.
• LOG_TEXT: Contains the detailed output or message from the process, with a capacity of up to 2000 characters. This is often where error details or status summaries are recorded.
• MESSAGE_NAME: Stores the name of a predefined Oracle Application error message, facilitating standardized error lookup and translation.
• LOG_DATE: The timestamp when the log entry was created, indicating when the event occurred within the process.
• Standard Who Columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN): Provide audit information on who created or last modified the row and when.

Common Use Cases and Queries

This table is primarily used for troubleshooting and process verification. A common scenario involves investigating a failed or problematic batch process. An administrator would query the log for entries related to a specific program run within a given timeframe. The following sample query pattern is fundamental for such analysis, often filtered by PROGRAM_NAME and LOG_DATE:

SELECT PROGRAM_NAME, LOG_DATE, MESSAGE_NAME, LOG_TEXT
FROM HR.GHR_PROCESS_LOG
WHERE PROGRAM_NAME = 'GHR_AUTO_WGI_PROC'
AND LOG_DATE > TRUNC(SYSDATE-1)
ORDER BY LOG_DATE DESC;

For reporting, the table can be used to generate summaries of process execution history or error frequency across different programs. Identifying recurring errors by joining on MESSAGE_NAME to the application messages table (FND_NEW_MESSAGES) is another advanced troubleshooting use case.

Related Objects

Based on the provided metadata, the primary relationship for this table is defined by its unique primary key constraint. The table is designed as a standalone audit entity with no foreign key dependencies on other objects, but it is referenced by other database objects.

• Primary Key: The table is defined with the primary key constraint GHR_PROCESS_LOG_PK on the column PROCESS_LOG_ID. This key ensures the uniqueness of each log entry.
• Sequence: The primary key values are generated by the sequence GHR_PROCESS_LOG_S, which is a critical related object for data insertion.
• Indexes: Besides the primary key index (GHR_PROCESS_LOG_PK), a non-unique index (GHR_PROCESS_LOG_N1) exists on PROGRAM_NAME, LOG_DATE, and MESSAGE_NAME to optimize query performance for the most common lookups.
• Dependencies: The documentation states that HR.GHR_PROCESS_LOG is referenced by another object named GHR_PROCESS_LOG# (the exact nature of this object is not detailed but is typically a database trigger). The table itself does not reference any other database objects.