Search Results ghr_pa_requests

Overview

The GHR_PA_REQUESTS table is a core data repository within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the central transactional table for managing the lifecycle of a Request to Personnel Action (RPA), which is the formal electronic document initiating a personnel change for a federal employee. Every personnel action, such as a promotion, transfer, or appointment, originates as a record in this table. Its primary role is to store all defining information about the request, including its nature, the employee's position and pay details before and after the action, and its routing and approval status within the system.

Key Information Stored

The table's structure is defined by its primary key, PA_REQUEST_ID, which uniquely identifies each request. A significant portion of its columns are foreign keys that establish critical relationships with other configuration and transactional tables in the GHR schema. Key data points stored include the Nature of Action (NOA) identifiers (FIRST_NOA_ID, SECOND_NOA_ID) linking to GHR_NATURE_OF_ACTIONS, and the associated NOA family code (NOA_FAMILY_CODE) from GHR_FAMILIES. It captures routing information via ROUTING_GROUP_ID and PERSONNEL_OFFICE_ID. The table also stores the "from" and "to" states of the personnel action, such as FROM_PAY_PLAN, TO_PAY_PLAN, TO_JOB_ID, TO_GRADE_ID, and TO_ORGANIZATION_ID. Furthermore, it maintains relationships to other RPAs for complex actions through columns like ALTERED_PA_REQUEST_ID, FIRST_NOA_PA_REQUEST_ID, and SECOND_NOA_PA_REQUEST_ID, which are self-referencing foreign keys to the same GHR_PA_REQUESTS table.

Common Use Cases and Queries

This table is fundamental for tracking, reporting, and auditing personnel actions. Common use cases include generating a list of all pending RPAs for a personnel office, auditing the history of actions for a specific employee, and reporting on the volume of actions by type or organization. A typical query might join GHR_PA_REQUESTS with GHR_NATURE_OF_ACTIONS and PER_ALL_PEOPLE_F to retrieve active requests. For example:

• SELECT pr.PA_REQUEST_ID, pr.REQUEST_NUMBER, noa.NOA_CODE, pp.FULL_NAME FROM HR.GHR_PA_REQUESTS pr JOIN HR.GHR_NATURE_OF_ACTIONS noa ON pr.FIRST_NOA_ID = noa.NATURE_OF_ACTION_ID JOIN APPS.PER_ALL_PEOPLE_F pp ON pr.PERSON_ID = pp.PERSON_ID WHERE pr.PERSONNEL_OFFICE_ID = :office_id AND SYSDATE BETWEEN pp.EFFECTIVE_START_DATE AND pp.EFFECTIVE_END_DATE;

Another critical pattern involves tracing the lineage of an altered action by joining the table to itself via the ALTERED_PA_REQUEST_ID column.

Related Objects

As indicated by its extensive foreign key relationships, GHR_PA_REQUESTS is a hub table with numerous dependencies. Key related objects include:

• Configuration Tables: GHR_NATURE_OF_ACTIONS, GHR_FAMILIES, GHR_ROUTING_GROUPS, GHR_PAY_PLANS, GHR_POIS.
• Core HR Tables: PER_JOBS, PER_GRADES, HR_ALL_ORGANIZATION_UNITS.
• Transactional Child Tables: GHR_PA_REMARKS (for comments), GHR_PA_HISTORY (for audit trails), GHR_EVENTS (for action events).
• Mass Transaction Tables: GHR_MASS_REALIGNMENT, GHR_MASS_SALARIES, GHR_MASS_TRANSFERS, which store details for bulk operations initiated via an RPA.
• Shadow Table: GHR_PA_REQUEST_SHADOW, which likely holds temporary or staging data related to the request.