Results for “locality_pay_area_code”

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

Overview

GHR_LOCALITY_PAY_AREAS_F is a date-tracked (effective-dated) reference table owned by the HR schema in Oracle E-Business Suite, delivered as part of the GHR — US Federal Human Resources product family. It stores the definition and attributes of locality pay areas, the geographic zones used under the US federal pay system to apply locality-based pay adjustments to employees covered by General Schedule (GS) and related pay plans. Each row represents a single locality pay area as it exists over a defined span of time, allowing the application to resolve the correct adjustment percentage applicable to a given pay period.

The _F suffix denotes a "full" / date-tracked (non-"_A" non-"_B") table that carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns and is validated against a corresponding date-tracked view. The heuristic Data Vault classification mined from the FK structure is standalone, meaning no foreign key relationships were detected in the documented metadata. As a modeling suggestion, this object is best treated as a reference hub (the LOCALITY_PAY_AREA_ID and LOCALITY_PAY_AREA_CODE identifiers) combined with an inline satellite carrying the descriptive and percentage attributes across the effective date range.

Key Information Stored

The table documents 15 columns. The most significant are:

• LOCALITY_PAY_AREA_ID — Surrogate primary key component. System-generated numeric identifier for the locality pay area, independent of any change to the descriptive text.
• LOCALITY_PAY_AREA_CODE — The user-facing business identifier, the column users reference as locality_pay_area_code. Forms part of the unique business key GHR_LOCALITY_PAY_AREAS_F_UK.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked validity window. Both the primary key GHR_LOCALITY_PAY_AREAS_F_PK and the unique key include these columns, so the same area may appear in multiple rows across time with evolving attributes.
• ADJUSTMENT_PERCENTAGE — The standard locality pay percentage applied to base pay for the area.
• LEO_ADJUSTMENT_PERCENTAGE — The equivalent adjustment for Law Enforcement Officer (LEO) pay schedules, which differ from the standard GS adjustment.
• ABBREVIATION, SHORT_NAME, LONG_NAME — Descriptive text fields used in listings, forms, and reports at varying levels of verbosity.
• ZD_EDITION_NAME — Enterprise Data Management / editioning column forming part of both unique indexes in 12.2.2.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY.

The surrogate key is LOCALITY_PAY_AREA_ID plus the effective dates; the business key candidate is LOCALITY_PAY_AREA_CODE plus the effective dates (and ZD_EDITION_NAME).

Common Use Cases and Queries

The table is most commonly queried to retrieve the effective locality adjustment percentage for an employee given an assignment date. A typical pattern joins the employee's duty location or geographic mapping to this table on the effective range:

• Resolve the active locality record as of a date: WHERE :eff_date BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE.
• Look up a specific area by code: WHERE LOCALITY_PAY_AREA_CODE = :code.
• Compare standard vs. LEO adjustment percentages for a given area for pay-plan modeling.
• Drive validations or LOVs in federal pay forms, where the code is the visible value and the ID the hidden surrogate.
• Feed reporting on locality pay changes over time, using the effective dates to reconstruct historical rates.

Because rows are date-tracked, virtually every query must include an effective-date predicate to avoid returning overlapping or obsolete definitions.

Related Objects

The documented FK structure classifies the object as standalone, so no enforced foreign keys were mined. In practice, other GHR objects and federal pay processing reference this table by its business code and ID. Significant dependents and companions include:

• Locality pay area assignment or mapping tables that link duty stations, geographic locations, or positions to a LOCALITY_PAY_AREA_ID.
• GHR employee assignment and pay-determination entities that consume ADJUSTMENT_PERCENTAGE and LEO_ADJUSTMENT_PERCENTAGE.
• The date-tracked view counterparts (the "_F" table's associated _V / _A view) used by forms and LOVs, resolved on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
• Federal pay plan and pay table objects whose scheduled rates are combined with the locality adjustment at run time.
• Reference/validation objects surfaced through GHR lookup values keyed on LOCALITY_PAY_AREA_CODE.

These relationships should be confirmed against the actual FK inventory in the target instance, as the provided metadata classifies the object as standalone.