Results for “state_or_country_code”

50+ results




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

Overview

GHR_DUTY_STATIONS_F is a date-tracked (datetrack) table in the HR schema that stores information about duty stations for the Oracle E-Business Suite US Federal Human Resources (GHR) product. Within Oracle EBS 12.1.1 and 12.2.2, a duty station represents the geographic location to which an employee is assigned, and it drives federal locality pay, leave accrual, and reporting determinations. The table is owned by the HR schema and carries a VALID status in the documented ETRM 12.2.2 physical schema, which records 19 columns.

The _F suffix denotes a "full" datetracked table in the HR datetrack model, meaning every change to a duty station produces a new effective-dated row rather than an in-place update. The table is heavily surrogate-keyed and versioned, with the primary key GHR_DUTY_STATIONS_F_PK and the unique key GHR_DUTY_STATIONS_F_UK both including EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and ZD_EDITION_NAME, confirming the multi-version nature of the data. From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone; heuristically, it behaves as a satellite-style reference/version record attached to the duty station business key, since no foreign-key dependencies to other tables were detected in the documented schema.

Key Information Stored

The table's most important columns fall into identity, classification, and audit categories:

The distinction between the surrogate primary key (DUTY_STATION_ID) and the business-key candidate (DUTY_STATION_CODE) is important when joining to functional data, which typically references the code rather than the surrogate ID.

Common Use Cases and Queries

Typical uses include validating locality pay assignments, reporting on the geographic distribution of employees, and reconciling duty station codes against federal locality pay schedules. A representative date-effective query is:

  • SELECT duty_station_code, name, locality_pay_area_id FROM hr.ghr_duty_stations_f WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
  • SELECT * FROM hr.ghr_duty_stations_f WHERE duty_station_code = 'XYZ' ORDER BY effective_start_date DESC;
  • SELECT s.name, COUNT(e.employee_number) FROM hr.ghr_duty_stations_f s, hr.per_all_assignments_f e WHERE s.duty_station_code = e.duty_station_code AND TRUNC(SYSDATE) BETWEEN s.effective_start_date AND s.effective_end_date GROUP BY s.name;

Typical output-oriented reports list duty station names, their MSA/CMSA codes, and associated locality pay area codes, allowing users to audit federal pay errors. Because the table is datetracked, queries should always filter on the effective date range or use the current effective row.

Related Objects

Because the documented FK relationship data classifies GHR_DUTY_STATIONS_F as standalone, direct FK references are limited; however, the following objects are functionally significant in the GHR localization and locality-pay model:

  • GHR_LOCALITY_PAY_AREA_F — locality pay area definitions referenced via LOCALITY_PAY_AREA_ID.
  • GHR_LEO_PAY_AREA — Law Enforcement Officer pay areas referenced via LEO_PAY_AREA_CODE.
  • HR_LOCATIONS_ALL_F — geographic location data that frequently overlaps duty station definitions.
  • PER_ALL_ASSIGNMENTS_F — assignment records referencing the duty station on an employee assignment.
  • PER_ALL_PEOPLE_F — person records tied to assignments.
  • PAY_FEDERAL_LOCALITY_RULES — payroll rules that consume duty station locality data.
  • GHR duty station APIs and concurrent programs used to load and maintain duty station records with datetrack validation.

These objects are commonly joined through DUTY_STATION_ID or DUTY_STATION_CODE to produce federal pay and location reporting.