Search Results hxt_prev_wage_base_pk




Overview
Explore in AI Chat

Overview

HXT_PREV_WAGE_BASE is a table in the HXT schema, owned by the Oracle Time and Labor module. Its documented purpose is to store the details of the prevailing wage rate base. In Oracle EBS 12.1.1 and 12.2.2, this table supports prevailing wage and certified payroll requirements, allowing the application to derive the applicable base wage rates that govern how time is evaluated for a given contract, project, or building.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. Because no foreign key relationships were mined, it is best treated as a standalone reference or lookup table rather than a hub, link, or satellite within a classic Data Vault structure. The table holds descriptive and rate-related attributes keyed by a prevailing wage code, which suggests it functions as a rate-definition source rather than a transactional fact. It is date-effective, meaning records are versioned by effective start and end dates, which allows historical rate bases to be preserved and queried for the correct point in time.

Key Information Stored

The table contains 13 documented columns. The primary key is defined by the HXT_PREV_WAGE_BASE_PK constraint over three columns, which together form both the surrogate and the business key:

The business-key candidate is the same unique index, HXT_PREV_WAGE_BASE_PK (PREV_WAGE_CODE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE), so there is no separate surrogate identifier beyond this composite key.

The remaining documented columns hold the rate amounts and contextual attributes:

Common Use Cases and Queries

This table is typically queried to resolve the effective prevailing wage rate for a given code and date, for example when validating timecard entries or producing certified payroll output. A point-in-time lookup uses the effective date range:

SELECT prev_wage_code, reg_amt, ovt_15_amt, ovt_20_amt, fbe_amt
FROM hxt_prev_wage_base
WHERE prev_wage_code = :code
AND :as_of_date BETWEEN effective_start_date AND effective_end_date;

Reporting use cases include listing all active prevailing wage bases, joining by CONTRACT_NUMBER or PROJECT_NUMBER to associated assignments, and filtering on PRINT_FLAG to control which records appear in printed outputs. Historical comparison queries exploit the date-effective columns to examine how a rate changed over time.

Related Objects

The documented metadata classifies this table as standalone with no mined foreign keys, so formal referential relationships are limited. Logical associations are expected through the prevailing wage code and through the contract, project, and building identifiers that appear in the column list. Consumers typically include Time and Labor timecard and prevailing wage validation logic, and reporting that references HXT_PREV_WAGE_BASE_PK for point-in-time rate resolution. Because the object is standalone, joins should be constructed on the shared business identifiers (PREV_WAGE_CODE, CONTRACT_NUMBER, PROJECT_NUMBER, BUILDING_NUMBER) rather than on undocumented foreign keys.