Results for “timecard_id”

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

Overview

HXC_TIMECARD_HOURS_V is a reporting view owned by the APPS schema within the HXC – Time and Labor Engine product of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). The view presents aggregated timecard hour totals for a time building block, expressed across standardized hour categories. Its primary purpose is to expose timecard hour summaries in a form that is directly consumable by Oracle Time and Labor (OTL) reporting, Oracle Payroll time processing, and external downstream integrations that require normalized hour figures rather than raw time entry rows.

The view is significant because time entries in OTL are stored at a granular level, while payroll and costing processes typically require summarized hours by category. HXC_TIMECARD_HOURS_V bridges that gap by returning a single consolidated row per time building block. The column names exposed to consumers—REGULAR_HOURS, PREMIUM_HOURS, NON_WORKED_HOURS, and TOTAL_HOURS—align directly with the hour buckets used throughout OTL and Payroll, making the view suitable for both ad hoc querying and programmatic extraction. This is the object most frequently referenced when a user searches for "total_hours," since TOTAL_HOURS is the column that returns the combined hour figure for a timecard.

Underlying Base Objects

The view is defined over the following documented base objects:

• HXC_TIME_BUILDING_BLOCKS (referenced in the schema as a synonym) – the core OTL table that stores individual time building blocks. Each block represents a unit of time entry, and the view selects from it using TIME_BUILDING_BLOCK_ID as the driving key.
• HXC_TIME_CATEGORY_UTILS_PKG – an OTL PL/SQL package containing the function CATEGORY_TIMECARD_HRS_IND, which computes the hour value for a given category. The view calls this function multiple times to derive each hour column.

Critically, the view does not simply join to a table of pre-summarized hours. Instead, its SELECT list invokes CATEGORY_TIMECARD_HRS_IND four times, passing literal category identifiers and the block identifiers. The mapping of function calls to output columns follows this pattern:

• TOTAL1 → REGULAR_HOURS
• TOTAL2 → PREMIUM_HOURS
• TOTAL3 → NON_WORKED_HOURS
• NULL → TOTAL_HOURS (the catch-all total across all categories)

The view also carries OBJECT_VERSION_NUMBER from the building block, surfaced as TIMECARD_OVN. Because the hour figures are computed at query time through a PL/SQL package function rather than stored physically, the view reflects current timecard state and is not a materialized snapshot.

Key Columns

• TIMECARD_ID – the identifier of the time building block (TIME_BUILDING_BLOCK_ID). This is the primary correlation key back to the underlying timecard data.
• TIMECARD_OVN – the object version number from HXC_TIME_BUILDING_BLOCKS, used for optimistic locking and change detection.
• REGULAR_HOURS – hours classified in the regular category (TOTAL1).
• PREMIUM_HOURS – hours classified in the premium category (TOTAL2), typically overtime or shift differential.
• NON_WORKED_HOURS – hours classified as non-worked (TOTAL3), such as vacation, sick, or other absence time.
• TOTAL_HOURS – the aggregate of all category hours for the block (category argument NULL), which is the value most commonly sought by users searching for "total_hours."

Common Use Cases and Queries

The view supports timecard hour reconciliation, payroll prepayment verification, and integration extracts. A typical retrieval of total hours for a specific block is:

• SELECT timecard_id, total_hours FROM apps.hxc_timecard_hours_v WHERE timecard_id = :p_block_id;

To report all four hour categories for a set of blocks, query the full column list and filter by TIMECARD_ID range or by join to the building block table:

• SELECT h.timecard_id, h.regular_hours, h.premium_hours, h.non_worked_hours, h.total_hours FROM apps.hxc_timecard_hours_v h, apps.hxc_time_building_blocks b WHERE h.timecard_id = b.time_building_block_id AND b.date_from BETWEEN :p_start AND :p_end;

Because the hour columns are computed through HXC_TIME_CATEGORY_UTILS_PKG, queries against this view should be limited to targeted result sets; large unfiltered scans invoke the package function repeatedly and can be expensive. When summarized totals are needed for extensive date ranges, restrict by the driving building-block keys or pre-filter using HXC_TIME_BUILDING_BLOCKS before joining. The view remains valid and available in both 12.1.1 and 12.2.2, with no structural differences documented between the two releases.