Results for “hxtfv_det_hours_worked”

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

Overview

HXTFV_DET_HOURS_WORKED is a VALID database view owned by the APPS schema in Oracle E-Business Suite, defined under the HXT – Time and Labor product module. It presents detailed hours worked information at the individual timecard line level, joining the core detailed hours fact table (HXT_DET_HOURS_WORKED_F) with assignment, person, and time-related descriptive entities to yield a fully denormalized reporting structure. The view exposes both descriptive business attributes (business group, person name, assignment number, project/task, shift, element, earning policy) and numerous surrogate identifiers, including the RATE_CODE_ID column, which is surfaced from DHW.FFV_RATE_CODE_ID. In EBS 12.1.1 and 12.2.2, this view serves as a reporting and integration layer for Time and Labor data, allowing BI Publisher reports, OBIEE extracts, and custom concurrent programs to retrieve detailed timecard hours without reconstructing multi-table joins manually. Because it is a view rather than a table, it always reflects current transactional data subject to the underlying date-effective and business-group security logic embedded in its definition.

Underlying Base Objects

Per the documented metadata for 12.2.2, the view is defined over the following objects: HR_ALL_ORGANIZATION_UNITS_TL, HR_GENERAL (package), HR_LOCATIONS_ALL_TL, HR_SECURITY (package), HXT_DET_HOURS_WORKED_F, HXT_EARNING_POLICIES, HXT_PROJECTS, HXT_SHIFTS, HXT_TASKS, PAY_ELEMENT_TYPES_F_TL, PER_ALL_PEOPLE_F, and PER_ASSIGNMENTS_F (itself a view). The primary driving table is HXT_DET_HOURS_WORKED_F, which supplies the core hours, amounts, rates, and ID columns. PER_ASSIGNMENTS_F and PER_ALL_PEOPLE_F provide assignment and person context, while HXT_EARNING_POLICIES, HXT_SHIFTS, HXT_TASKS, HXT_PROJECTS, and PAY_ELEMENT_TYPES_F_TL supply descriptive lookups. HR_GENERAL.DECODE_LOOKUP performs on-the-fly decoding of lookup codes such as pay status, tax rule, and earning reason. HR_SECURITY is referenced to enforce organizational/business-group access, and HR_LOCATIONS_ALL_TL and HR_ALL_ORGANIZATION_UNITS_TL supply location and business group naming.

Key Columns

• Identifying columns: DET_HOURS_WORKED_ID, SUM_HOURS_WORKED_ID (parent), TIMECARD_ID, ASSIGNMENT_ID.
• Descriptive context: BUSINESS_GROUP_NAME, PERSON_NAME, ASSIGNMENT_NUMBER, EARNING_POLICY, ELEMENT_NAME, SHIFT_NAME, LOCATION_CODE, PROJECT_NUMBER/PROJECT_NAME, TASK_NUMBER/TASK_NAME.
• Time and amounts: DATE_WORKED, HOURS, TIME_IN, TIME_OUT, ACTUAL_TIME_IN, ACTUAL_TIME_OUT, AMOUNT, HOURLY_RATE, RATE_MULTIPLE.
• Decoded lookups: TAX_RULE, EARN_REASON, PAY_STATUS, PA_STATUS, LINE_STATUS.
• ID columns: BUSINESS_GROUP_ID, ORGANIZATION_ID, JOB_ID, ELEMENT_TYPE_ID, EARNING_POLICY_ID, COST_CENTER_ID, LABOR_ACCOUNT_ID, RATE_CODE_ID (from FFV_RATE_CODE_ID), PROJECT_ID, TASK_ID, LOCATION_ID, SHIFT_ID, RETRO_LINE_ID, RETRO_BATCH_ID, PBL_LINE_ID.

Common Use Cases and Queries

Typical scenarios include extracting timecard detail for payroll reconciliation, reporting hours by project/task, and exporting rate code information for costing. A representative query filtering on rate code is:

• SELECT person_name, date_worked, hours, hourly_rate, rate_multiple FROM apps.hxtfv_det_hours_worked WHERE rate_code_id = :p_rate_code_id AND date_worked BETWEEN :p_from AND :p_to;
• SELECT project_number, task_number, SUM(hours) FROM apps.hxtfv_det_hours_worked WHERE date_worked >= :p_start GROUP BY project_number, task_number;
• SELECT person_name, pay_status, SUM(amount) FROM apps.hxtfv_det_hours_worked WHERE business_group_id = :p_bg GROUP BY person_name, pay_status;

Applications should apply business-group and security filters consistent with HR_SECURITY to respect data access rules.