Search Results hxt_tim_summary_fmv




Overview
Explore in AI Chat

Overview

HXT_TIM_SUMMARY_FMV is a read-only Oracle EBS view owned by the APPS schema, classified under the HXT (Time and Labor) product family. In Oracle EBS 12.1.1 and 12.2.2 it exposes a consolidated, denormalized snapshot of timecard activity, linking each timecard record to the assignment, organization, payroll, time period, rotation plan, and approver context in which it was processed. The "_FMV" suffix conventionally denotes a "Flat/Formatted Materialized View" style object intended primarily for reporting and integration rather than for transactional processing.

Rather than forcing report developers to join the underlying HR and Time and Labor tables manually, the view pre-resolves the effective-dated relationships between people, assignments, time periods, and payrolls. This makes it a convenient single source for approved timecard summaries, approval audit trails, and organization-level time reporting. Because the view references only other views, synonyms, and packaged functions (not tables directly), it is a logical reporting layer, and its data always reflects the current state of the base tables at query time.

Underlying Base Objects

The view is defined over the following documented base objects:

The joins rely heavily on the BETWEEN effective-date pattern, ensuring that each row reflects only the person, assignment, and rotation-plan versions valid as of the time period end date. The approver person is joined with an outer join, so timecards with no approver still appear.

Key Columns

Common Use Cases and Queries

This view is typically used for timecard approval reporting, organization roll-ups, and payroll-period reconciliation extracts.

  • Approved timecards by organization: filter on ORGANIZATION_ID and APPROVED_TIMESTAMP IS NOT NULL to list approved entries.
  • Approval audit trail: select EMPLOYEE_NUMBER, FULL_NAME, APPROV_PERSON_NAME, APPROVED_TIMESTAMP ordered by END_DATE.
  • Payroll reconciliation: group by PAYROLL_NAME and END_DATE to count timecards per period.

Sample query:

SELECT employee_number, full_name, organization_name, payroll_name, end_date, approv_person_name, approved_timestamp FROM apps.hxt_tim_summary_fmv WHERE organization_id = :org_id AND approved_timestamp IS NOT NULL ORDER BY end_date;

Because the view performs several effective-dated joins, queries should always constrain ORGANIZATION_ID or a business-group column to maintain acceptable performance in large multi-org environments.