Search Results hxc_resource_timecards_v




Overview
Explore in AI Chat

Overview

HXC_RESOURCE_TIMECARDS_V is a reporting view owned by the APPS schema within the HXC – Time and Labor Engine product of Oracle E-Business Suite. It presents a denormalized, read-optimized projection of timecard data that consolidates information from the Time and Labor summary and building-block tables together with lookup-based status decoding and data set availability flags. Its principal role is to expose timecard header information—resource identity, approval status, period boundaries, recorded hours, submission timing, and associated comments—in a form suitable for direct consumption by reports, concurrent programs, and external integrations without requiring the caller to replicate the underlying join logic.

The view is registered as VALID in both the 12.1.1 and 12.2.2 releases, and the ETRM metadata documents it as a stable, supported object for reporting purposes. Because the view encapsulates multiple decode and existence-check subqueries, it shields report authors from having to resolve approval-status lookups and offline data set conditions themselves.

Underlying Base Objects

The view's documented dependency chain includes the following referenced objects:

  • HXC_TIMECARD_SUMMARY (SYNONYM) – The driving table, supplying timecard identifiers, version numbers, resource references, approval status, period timestamps, recorded hours, submission dates, and the HAS_REASONS indicator.
  • HXC_TIME_BUILDING_BLOCKS (SYNONYM) – Joined in an outer-join fashion via TIMECARD_ID and OBJECT_VERSION_NUMBER to supply COMMENT_TEXT, preserving timecard rows even where no comment block exists.
  • HXC_DATA_SETS (SYNONYM) – Queried by two scalar EXISTS subqueries to determine whether the timecard's stop time falls inside an off-line, restore-in-progress, or backup-in-progress data set, and whether any such data set exists at all.
  • HR_GENERAL (PACKAGE) – Invoked as HR_GENERAL.DECODE_LOOKUP against the HXC_APPROVAL_STATUS lookup type to translate raw status codes into descriptive text.
  • DUAL (SYNONYM) – Used to wrap the EXISTS predicates in an inline SELECT for the DECODE expression.

Because the definition relies on HR_GENERAL.DECODE_LOOKUP, the effective status names reflect the lookup values configured in the target instance.

Key Columns

  • TIMECARD_ID – Primary identifier for the timecard; the join key to downstream and dependent timecard objects.
  • TIMECARD_OVN – Object version number, supporting optimistic concurrency and version-specific queries.
  • RESOURCE_ID – Identifies the person or resource to whom the timecard belongs.
  • STATUS_CODE / STATUS_NAME – The raw approval status code and its decoded, human-readable equivalent (truncated to 80 characters).
  • PERIOD_STARTS / PERIOD_ENDS – The start and stop timestamps bounding the recorded work, mapped from START_TIME and STOP_TIME.
  • HOURS_WORKED – Recorded hours on the timecard, sourced from RECORDED_HOURS.
  • SUBMISSION_DATE – Timestamp indicating when the timecard was submitted.
  • TIMECARD_COMMENT – Free-text comment drawn from the related building block, if present.
  • REASON_INFO – Populated when the HAS_REASONS flag is set, indicating associated reason data.
  • DATA_SET_STATUS – Returns OFF_LINE when the stop time falls within an off-line or in-progress data set; otherwise OTHERS.
  • OFFLINE_EXISTS – Returns OFFLINE_EXISTS or OFFLINE_NOTEXISTS depending on whether any qualifying data set is present in the system.

Common Use Cases and Queries

Typical scenarios include timecard status dashboards, submission audits, resource utilization reports, and integration extracts that feed external payroll or project systems.

  • Listing decoded statuses for a resource's timecards within a date range.
  • Detecting timecards that intersect off-line data set windows before scheduling extracts.
  • Auditing submitted hours and submission lag against period boundaries.

A representative query:

SELECT TIMECARD_ID, RESOURCE_ID, STATUS_NAME, PERIOD_STARTS, PERIOD_ENDS, HOURS_WORKED, SUBMISSION_DATE, DATA_SET_STATUS FROM APPS.HXC_RESOURCE_TIMECARDS_V WHERE RESOURCE_ID = :p_resource_id AND PERIOD_STARTS >= :p_from_date ORDER BY PERIOD_STARTS DESC;

Because HXC_DATA_SETS is evaluated per row, filtering on OFFLINE_EXISTS is best applied after range and resource predicates have reduced the result set.