Results for “hxc_timecards_v”

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

Overview

HXC_TIMECARDS_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Time and Labor Engine (HXC) product. It presents a filtered, business-oriented projection of timecard records stored in the Time and Labor building block infrastructure. Rather than exposing the full population of time building blocks, the view restricts its output to rows that represent person-level timecards within an open date range, thereby delivering a clean result set suitable for reporting, integration, and downstream processing.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as a stable interface for extracting timecard headers without requiring the consumer to understand the internal scoping, typing, and date-effectivity conventions of the underlying building block model. Because it is a view and not a table, it carries no independent storage and reflects the current state of the base data at query time.

Underlying Base Objects

The view is defined over the HXC_TIME_BUILDING_BLOCKS base object (referenced in the ETRM metadata as the HXC_TIME_BUILDING_BLOCKS synonym) and also references the HR_GENERAL package, specifically the HR_GENERAL.END_OF_TIME constant. Its defining query filters the base table on three predicates: SCOPE = 'TIMECARD', TYPE = 'RANGE', and RESOURCE_TYPE = 'PERSON', and further constrains DATE_TO to equal HR_GENERAL.END_OF_TIME.

• HXC_TIME_BUILDING_BLOCKS — the core Time and Labor structure that stores building blocks of time for persons, assignments, and other resource types across defined scopes and date ranges.
• HR_GENERAL (PACKAGE) — supplies END_OF_TIME, the sentinel date value indicating that a record is the currently effective version rather than a historical, date-tracked predecessor.

By applying these filters, the view isolates the active timecard-range building blocks belonging to persons and excludes superseded or non-timecard records.

Key Columns

The columns surfaced by the view map to the building block attributes, with the ETRM column listing prefixed by TCRD_:

• TCRD_TIME_BUILDING_BLOCK_ID — primary identifier of the timecard building block.
• TCRD_OBJECT_VERSION_NUMBER — optimistic locking / versioning column used to detect concurrent updates.
• TCRD_START_TIME and TCRD_STOP_TIME — the start and end of the timecard's range.
• TCRD_PARENT_BUILDING_BLOCK_ID and TCRD_PARENT_BUILDING_BLOCK_OVN — link to the parent block and its version, supporting hierarchical time structures.
• TCRD_APPROVAL_STATUS — approval state of the timecard.
• TCRD_RESOURCE_ID and TCRD_RESOURCE_TYPE — the owning resource; for this view, the resource type is consistently PERSON.
• TCRD_COMMENT_TEXT — free-form comments.
• TCRD_SUBMISSION_DATE — the timecard submission date.

Common Use Cases and Queries

Typical uses include timecard reporting, integration extracts, and status monitoring. A representative query returns timecards for a given person and date window:

SELECT tcrd_time_building_block_id, tcrd_resource_id, tcrd_start_time, tcrd_stop_time, tcrd_approval_status, tcrd_submission_date FROM apps.hxc_timecards_v WHERE tcrd_resource_id = :p_person_id AND tcrd_start_time >= :p_from AND tcrd_stop_time <= :p_to;

Other scenarios include listing all timecards pending approval by filtering on TCRD_APPROVAL_STATUS, or joining TCRD_RESOURCE_ID to PER_ALL_PEOPLE_F to resolve person names. Because the view already restricts rows to currently effective person timecards, most consumers can query it directly without additional effectivity logic.