Search Results hxt_sum_hours_worked




Overview
Explore in AI Chat

Overview

HXT_SUM_HOURS_WORKED is an Oracle E-Business Suite (EBS) view owned by the APPS schema and defined in the HXT – Time and Labor product module. It exposes summarized hours-worked records generated by the Time and Labor time collection and timecard processing flows, presenting the data in a reporting-friendly format suitable for payroll costing, project charging, and downstream integration.

The view is a date-effective (temporal) view: it is defined over the base table HXT_SUM_HOURS_WORKED_F and filters rows so that only records whose effective date range contains the current session's effective date are visible. Because it resolves the effective date from FND_SESSIONS using USERENV('SESSIONID'), the view returns the record version that is in force "as of" the user's current session context rather than the full history held in the underlying table. This is the standard Oracle pattern for date-tracked (datetracked) entities. In 12.1.1 and 12.2.2 the view is reported as VALID, and its structure is stable across both releases.

Underlying Base Objects

The documented base objects referenced by the view are:

  • HXT_SUM_HOURS_WORKED_F (synonym) — the "_F" (full) date-effective table that stores the complete history of summarized hours-worked rows, including each effective start and end date.
  • FND_SESSIONS (synonym) — the Applications session table, queried to obtain the effective date associated with the current session ID.

The view text selects all columns of the base table and applies the effective-date predicate:

EFFECTIVE_START_DATE <= (session effective date) AND EFFECTIVE_END_DATE >= (session effective date)

Consequently, for every logical record the view returns exactly one row — the version effective at the session date — while the underlying table may hold multiple historical versions. Applications code and reports should query the view rather than the _F table to obtain the "current" version without writing date-effective predicates themselves.

Key Columns

Common Use Cases and Queries

The view is typically queried by custom reports, extracts, and integration interfaces that require summarized hours and associated amounts for a given assignment or date range, using the session-effective version of the data. Typical filters include assignment, date worked, and line status.

  • Time and Labor to Payroll reconciliation of summarized hours and amounts.
  • Project costing extracts keyed on PROJECT_ID and assignment.
  • Ad-hoc reporting on hours worked, rates, and earning elements.
  • Feeding downstream interfaces requiring effective-dated "current" rows.

Sample query:

SELECT assignment_id,
       date_worked,
       SUM(hours)     AS total_hours,
       SUM(amount)    AS total_amount
FROM   apps.hxt_sum_hours_worked
WHERE  date_worked BETWEEN :p_start_date AND :p_end_date
AND    line_status = 'A'
GROUP  BY assignment_id, date_worked
ORDER  BY assignment_id, date_worked;

Because the view performs the effective-date resolution automatically, no additional date-effective predicate is required; users should avoid joining directly to HXT_SUM_HOURS_WORKED_F unless historical versions are explicitly needed.