Results for “hxt_hdp_det_hours_worked_v”

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

Overview

The HXT_HDP_DET_HOURS_WORKED_V view is a reporting object within the Oracle E-Business Suite Time and Labor (HXT) module. It presents a consolidated, date-level summary of detailed hours worked, filtered to specific earning categories. In the 12.1.1 and 12.2.2 releases, this view is owned by the APPS schema and holds a VALID status. Its principal role is to provide a lightweight aggregation layer over detailed time entry data, making it suitable for downstream reporting, payroll-facing extracts, and integration with dependent applications that require summed hours per timecard and work date rather than the raw transactional detail.

Because the view applies NVL(SUM(...), 0) aggregation, it guarantees a numeric, non-null hours value for each qualifying grouping, which simplifies consumption in report templates and interfaces where null handling would otherwise be required.

Underlying Base Objects

The view is defined over three referenced objects as documented in the ETRM metadata:

• HXT_DET_HOURS_WORKED (VIEW) — supplies the core transactional hours, element type, timecard identifier (TIM_ID), and work date (DATE_WORKED).
• HXT_PAY_ELEMENT_TYPES_F_DDF_V (VIEW) — a descriptive flexfield view over element types, used here to restrict results to specific earning categories.
• PAY_ELEMENT_TYPES_F (SYNONYM) — the effective-dated base definition of payroll element types, joined for validity window checking.

The join logic links each detail hours record to its element type on ELEMENT_TYPE_ID, and enforces that DATE_WORKED falls between the element type's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE for both the base and DDF views. This ensures date-valid element configuration is respected throughout the aggregation.

Key Columns

• DET_TIM_ID — the detail timecard identifier (aliased from DHW.TIM_ID). It identifies the timecard to which the summed hours belong.
• DET_DATE — the date on which the hours were worked (aliased from DHW.DATE_WORKED). It forms the second grouping key.
• DET_HOURS — the total hours worked for the given timecard and date, computed as NVL(SUM(DHW.HOURS),0). The NVL guarantees zero rather than null when no detail rows aggregate.

Common Use Cases and Queries

This view is typically used as a foundation for reporting regular and overtime totals per timecard per day. Because the definition restricts HXT_EARNING_CATEGORY to REG or OVT, it isolates standard and overtime earnings, excluding other earning categories such as leave or premium codes. A representative query retrieving totals for a specific timecard is:

• SELECT det_tim_id, det_date, det_hours FROM apps.hxt_hdp_det_hours_worked_v WHERE det_tim_id = :p_tim_id ORDER BY det_date;
• SELECT det_tim_id, SUM(det_hours) FROM apps.hxt_hdp_det_hours_worked_v GROUP BY det_tim_id;

Typical applications include reconciliation of reported time against payroll element entries, daily labour summaries for interface files, and audit reports validating that timecard hours map correctly to date-effective earning categories.