Results for “to_grade_id”

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

Overview

GHR_PA_REQUEST_SHADOW is a table in the HR schema of Oracle E-Business Suite, belonging to the GHR - US Federal Human Resources product family. As its name and ETRM description indicate, the table stores all the columns of the corresponding record of GHR_PA_REQUESTS. It functions as a shadow, or mirrored companion, table to the primary personnel action request repository, preserving a duplicate image of the request row that supports federal personnel action processing, audit reconciliation, and historical comparisons without altering the base transaction data.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as hub-leaning. This heuristic is derived from the foreign key structure: the table is referenced by GHR_PA_REQUESTS through the PA_REQUEST_ID column, and it carries a single-column primary key, GHR_PA_REQUEST_SHADOW_PK, defined on PA_REQUEST_ID. In practice, this means the shadow table holds a stable, unique business key linking back to the originating personnel action request, making it well suited to a hub-style role rather than a transactional satellite. Analysts modeling this object for downstream warehouses should treat PA_REQUEST_ID as the durable identifier and the remaining descriptive columns as attributes that could be split into satellites based on change frequency and source system.

Key Information Stored

The table contains 62 documented columns in the 12.2.2 physical schema. The primary key of interest is PA_REQUEST_ID, which is both the surrogate identifier for the shadow row and the foreign key to GHR_PA_REQUESTS. Because it carries a unique index (GHR_PA_REQUEST_SHADOW_PK), it is also the documented business-key candidate across the relationship.

The remaining columns capture the substantive detail of the personnel action being mirrored. The most significant clusters include:

• Employee identity attributes: EMPLOYEE_FIRST_NAME, EMPLOYEE_LAST_NAME, EMPLOYEE_MIDDLE_NAMES, EMPLOYEE_DATE_OF_BIRTH, and EMPLOYEE_NATIONAL_IDENTIFIER.
• Position and grade context: TO_POSITION_ID, TO_OCC_CODE, TO_GRADE_OR_LEVEL, TO_GRADE_ID, TO_STEP_OR_RATE, and POSITION_OCCUPIED.
• Pay and premium indicators: TO_AP_PREMIUM_PAY_INDICATOR, TO_AUO_PREMIUM_PAY_INDICATOR, TO_RETENTION_ALLOWANCE, TO_STAFFING_DIFFERENTIAL, TO_SUPERVISORY_DIFFERENTIAL, and PAY_RATE_DETERMINANT.
• Employment category and status: TENURE, FLSA_CATEGORY, BARGAINING_UNIT_STATUS, SUPERVISORY_STATUS, WORK_SCHEDULE, PART_TIME_HOURS, RETIREMENT_PLAN, and VETERANS_PREFERENCE.
• Duty station and forwarding details: DUTY_STATION_ID, DUTY_STATION_LOCATION_ID, and the FORWARDING_ADDRESS_LINE columns along with FORWARDING_TOWN_OR_CITY, FORWARDING_POSTAL_CODE, and FORWARDING_COUNTRY_SHORT_NAME.
• Action and award data: FIRST_ACTION_LA_CODE1, SECOND_ACTION_LA_CODE1, AWARD_AMOUNT, AWARD_UOM, and AWARD_PERCENTAGE.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE.

The presence of both FROM-style and TO-style values (for example, TO_GRADE_OR_LEVEL paired with grade identifiers) reinforces the table's role as a comparison snapshot for a pending action.

Common Use Cases and Queries

The principal use case is reconciling the shadow record with its parent request in GHR_PA_REQUESTS to detect drift, validate applied changes, or reconstruct the state of a request before it was finalized. A representative join pattern is:

• SELECT r.PA_REQUEST_ID, r.REQUEST_STATUS, s.TO_POSITION_ID, s.TO_GRADE_OR_LEVEL, s.TENURE FROM GHR_PA_REQUESTS r JOIN GHR_PA_REQUEST_SHADOW s ON r.PA_REQUEST_ID = s.PA_REQUEST_ID WHERE r.LAST_UPDATE_DATE > :cutoff;

Additional scenarios include federal workforce reporting on veterans preference and tenure distributions, position-to-grade audit trails for staffing actions, and premium pay exposure analysis using the TO_AP and TO_AUO indicators. Analysts commonly filter on PA_REQUEST_ID to isolate a single action and on EMPLOYEE_NATIONAL_IDENTIFIER or name columns to trace an employee's action history. Because audit columns are duplicated, the shadow table also supports change-detection queries that compare LAST_UPDATE_DATE and CREATED_BY between the two tables.

Related Objects

The following objects are most significant in relation to GHR_PA_REQUEST_SHADOW, based on the documented foreign key and references:

• GHR_PA_REQUESTS — the parent personnel action request table. FK: GHR_PA_REQUESTS.GHR_PA_REQUESTS_PA_REQUEST_ID references GHR_PA_REQUEST_SHADOW, joined on PA_REQUEST_ID.
• GHR_PA_REQUEST_SHADOW_PK — the primary key constraint unique index on PA_REQUEST_ID.
• PER_ALL_PEOPLE_F / PER_ALL_ASSIGNMENTS_F — employee and assignment records commonly joined via the employee identifier attributes in the shadow row.
• HR_ALL_ORGANIZATION_UNITS / HR_LOCATIONS_ALL — duty station and location lookups for DUTY_STATION_ID and DUTY_STATION_LOCATION_ID.
• FND_LOOKUP_VALUES — reference lookups for code columns such as TENURE, FLSA_CATEGORY, WORK_SCHEDULE, and RETIREMENT_PLAN.
• HR_API or GHR personnel action APIs used to create and update GHR_PA_REQUESTS, which populate the shadow row.

Together these objects form the federal personnel action data model, with GHR_PA_REQUEST_SHADOW serving as the durable key-bearing mirror of each request.