Search Results table_name

Overview

The HR.GHR_PA_HISTORY table is a core audit and history tracking table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the HRMS module. It functions as a centralized log for transactional changes made to key person and assignment-related tables, primarily as part of the Position Administration (PA) and Retroactive Pay (RPA) processes. Its role is to provide a detailed, immutable record of Data Manipulation Language (DML) operations, enabling traceability, audit compliance, and support for retroactive processing by storing the context of each change, including the process date and the specific Retroactive Pay Adjustment (RPA) request that triggered it.

Key Information Stored

The table's structure is designed to capture the who, what, when, and why of a transaction. The primary key is the system-generated PA_HISTORY_ID. Critical columns include TABLE_NAME, which identifies the source table (e.g., PER_PEOPLE_F, PER_ASSIGNMENTS_F), and INFORMATION1 through INFORMATION5, which store specific identifiers from the changed record, such as the PERSON_ID or ASSIGNMENT_ID. The EFFECTIVE_DATE of the change, the PERSON_ID, and the ASSIGNMENT_ID are also directly stored. Foreign key columns PA_REQUEST_ID and ALTERED_PA_REQUEST_ID link to the GHR_PA_REQUESTS table, directly associating history entries with specific RPA processes. The NATURE_OF_ACTION_ID further classifies the type of DML operation performed.

Common Use Cases and Queries

This table is essential for auditing, troubleshooting, and generating historical reports. A common use case is tracing all changes made to a specific person's assignment due to a retroactive pay adjustment. Another is identifying all transactional activity on a given date for compliance reporting. Sample queries include:

• Retrieving the change history for a specific assignment: SELECT * FROM hr.ghr_pa_history WHERE table_name = 'PER_ASSIGNMENTS_F' AND assignment_id = <id> ORDER BY effective_date;
• Finding all history records created by a specific RPA request for audit: SELECT * FROM hr.ghr_pa_history WHERE pa_request_id = <request_id>;
• Reporting on all changes to key tables within a date range: SELECT table_name, COUNT(*) FROM hr.ghr_pa_history WHERE process_date BETWEEN :p_start_date AND :p_end_date GROUP BY table_name;

Related Objects

HR.GHR_PA_HISTORY has integral relationships with several key EBS objects. Its primary foreign key relationships are with the GHR_PA_REQUESTS table, linking history entries to the originating and altered retroactive pay requests. The table's indexes, particularly GHR_PA_HISTORY_N1 through GHR_PA_HISTORY_N4, are optimized for queries filtering on TABLE_NAME, PERSON_ID, ASSIGNMENT_ID, and EFFECTIVE_DATE. Fundamentally, it is a dependent object that audits changes to the core tables listed in its documentation, including PER_PEOPLE_F, PER_ASSIGNMENTS_F, PAY_ELEMENT_ENTRIES_F, and related extra information tables.