Search Results hxt_det_hours_worked_x




Overview
Explore in AI Chat

Overview

APPS.HXT_DET_HOURS_WORKED_X is a business-facing view in the Oracle E-Business Suite Time and Labor module (product code HXT). It exposes detailed timecard line data — reported hours, time entry in/out values, and the associated payroll, project accounting, and geographic attributes — in a single denormalized result set suitable for reporting, extracts, and downstream integration. The view is documented as VALID in the APPS schema and conforms to the standard EBS convention of suffixing reportable views with _X, distinguishing them from the underlying transactional _F (facts) tables that carry effective-dated, audit-stamped rows.

The defining characteristic of this view is its date-bounded filter. The view definition restricts the result set to rows where EFFECTIVE_START_DATE <= TRUNC(SYSDATE) and EFFECTIVE_END_DATE >= TRUNC(SYSDATE). In practice, this means the view returns only the currently effective version of each timecard detail line, shielding the consumer from the multi-version history that accumulates in the base table as records are corrected, reversed, or adjusted. Consumers can therefore query the view without writing their own effective-dating predicates.

Underlying Base Objects

The view is defined exclusively over HXT_DET_HOURS_WORKED_F, referenced in the metadata as a synonym. No joins to other tables are present in the documented view text: the SELECT list simply projects the columns of the base table, in the same order, with the effective-dating filter applied in the WHERE clause. All columns are passed through unmodified, so data types, lookups, and semantics for any given column are inherited directly from the base table.

Because the view is a thin projection, it does not introduce calculated columns, aggregation, or denormalization of foreign keys into descriptive values. Any enrichment (for example, resolving ASSIGNMENT_ID to a person or PROJECT_ID to a project number) must be performed by the consuming query against the appropriate EBS tables.

Key Columns

Common Use Cases and Queries

Typical uses include reporting currently effective timecard detail for an assignment or date range, validating hours with geographic attributes before payroll or project cost transfer, and extracting time data for external warehouses or tax reporting. A representative query retrieving hours worked with location attributes is:

SELECT h.ID, h.ASSIGNMENT_ID, h.DATE_WORKED, h.HOURS,
       h.STATE_NAME, h.COUNTY_NAME, h.CITY_NAME,
       h.PAY_STATUS, h.PA_STATUS
FROM   APPS.HXT_DET_HOURS_WORKED_X h
WHERE  h.DATE_WORKED BETWEEN :p_start_date AND :p_end_date
AND    h.ASSIGNMENT_ID = :p_assignment_id
ORDER BY h.DATE_WORKED;

SELECT STATE_NAME, SUM(HOURS) total_hours
FROM   APPS.HXT_DET_HOURS_WORKED_X
WHERE  DATE_WORKED BETWEEN :p_start_date AND :p_end_date
GROUP BY STATE_NAME;

Because the view applies an implicit SYSDATE-based filter, queries cannot retrieve historical or future-dated versions; consumers requiring that behavior must query HXT_DET_HOURS_WORKED_F directly with their own effective-date predicates.