Search Results locality_worked




Overview
Explore in AI Chat

Overview

HXT_BATCH_SUM_HOURS_V is a reporting view in the Oracle E-Business Suite Time and Labor module (HXT). It consolidates timecard data into batch summaries of hours worked, presenting one row per combination of date worked, batch, assignment, element, and cost allocation. The view is designed to support payroll costing, labor distribution, and integration scenarios where time entered against batches must be flattened into hours, rates, and accounting flexfield segments. Because it exposes both raw hours and the associated hourly rate, rate multiple, and cost allocation keyflex, it serves as a bridge between timecard capture in HXT and downstream payroll or general ledger costing.

In EBS 12.1.1 and 12.2.2 the object resides in the APPS schema and is invoked by concurrent programs and custom reporting that need summarized rather than transactional detail. The ETRM metadata notes the view is "Not implemented in this database" for the documented instance, meaning the definition is supplied for reference only and may be absent or renamed depending on patch level and localization.

Underlying Base Objects

The view text joins several base tables. The documented joins are:

Although the ETRM metadata records "Referenced base objects: none documented," the embedded view text confirms these eight tables. The outer joins to PCAK, LOC, and FFVR (denoted by the (+) operator) indicate that cost allocation, location, and rate code are optional on a given hours row.

Key Columns

  • DATE_WORKED — the work date driving per-day reporting.
  • BATCH_ID — the timecard batch grouping the hours.
  • ASSIGNMENT_NUMBER — the employee assignment for the work.
  • ELEMENT_NAME — the payroll element to which hours are attributed.
  • FROM_DATE / TO_DATE — derived effective bounds, computed as the latest of PPD start, element start, and assignment start, and the earliest of the corresponding end dates.
  • RATE_MULTIPLE, HOURLY_RATE — the multiplier and rate applied to hours.
  • COST_ALLOCATION_KEYFLEX_ID and SEGMENT1–SEGMENT30 — the costing flexfield and its individual segments.
  • LOCALITY_WORKED — location code from HR_LOCATIONS.
  • RATE_CODE — flex value describing the rate.
  • SEPARATE_CHECK_FLAG, TAX_SEPARATELY_FLAG — flags for separate check and separate tax processing.
  • AMOUNT, HOURS — the monetary amount and hours worked.

Common Use Cases and Queries

Typical uses include validating batch hours before payroll costing, reconciling cost allocation across assignments, and feeding downstream GL or project costing interfaces. A representative query:

SELECT batch_id, assignment_number, element_name, date_worked, hours, amount FROM hxt_batch_sum_hours_v WHERE date_worked BETWEEN :p_start AND :p_end ORDER BY batch_id, assignment_number, date_worked;

For costing analysis, selecting segment columns and locality supports labor distribution review. Because the view is documented as not implemented in the reference database, verify object existence and column names against the target instance prior to use.