Search Results ghr_pa_request_shadow




Overview
Explore in AI Chat

Overview

The GHR_PA_REQUEST_SHADOW table is a core data object within the Oracle E-Business Suite US Federal Human Resources (GHR) module. As its name and description indicate, this table functions as a shadow or mirror repository, storing a complete copy of all columns from a corresponding record in the primary GHR_PA_REQUESTS table. Its primary role is to support data integrity, auditing, and complex transaction processing within the federal personnel action workflow. By maintaining a synchronized duplicate, the system can facilitate operations like comparison, rollback, or historical tracking of personnel action requests, which are critical for compliance and reporting in the federal sector.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the table's definition states it stores "all the columns of the corresponding record of GHR_PA_REQUESTS." Therefore, its structure is a direct replica of the GHR_PA_REQUESTS table. The documented primary key is the column PA_REQUEST_ID, which uniquely identifies each shadow record and corresponds to the primary key of its source request. This ensures a strict one-to-one relationship between a request and its shadow copy. The data held encompasses the entire state of a personnel action request at the point of shadowing, which may include details on the employee, action type, effective dates, organizational assignment, and all associated approval and processing attributes.

Common Use Cases and Queries

A primary use case is auditing and change tracking. By comparing a current record in GHR_PA_REQUESTS with its archived state in GHR_PA_REQUEST_SHADOW, users or processes can identify precisely which fields were modified during a transaction. This is vital for compliance audits. Another common scenario is supporting complex, multi-step approval workflows where the system may need to preserve a snapshot before applying further validations or updates. A typical query would involve joining the two tables on the PA_REQUEST_ID to perform a column-by-column comparison.

SELECT *
FROM ghr_pa_requests req
JOIN ghr_pa_request_shadow shd ON req.pa_request_id = shd.pa_request_id
WHERE req.pa_request_id = :request_id;

This pattern is fundamental for generating detailed audit reports on personnel action history.

Related Objects

The table has a direct and documented foreign key relationship with the primary GHR_PA_REQUESTS table, as per the provided metadata.

  • Primary Table (Parent): GHR_PA_REQUESTS
  • Foreign Key Relationship: The column GHR_PA_REQUEST_SHADOW.PA_REQUEST_ID is a foreign key referencing GHR_PA_REQUESTS.PA_REQUEST_ID. The constraint is named GHR_PA_REQUESTS.GHR_PA_REQUESTS_PA_REQUEST_ID.
  • Primary Key: The table's primary key constraint is named GHR_PA_REQUEST_SHADOW_PK on the PA_REQUEST_ID column.

This relationship is the table's sole defining structural dependency, anchoring every shadow record to a single, specific personnel action request in the main transaction table.