Search Results hxc_time_building_blocks




Overview
Explore in AI Chat

Overview

The HXC_TIME_BUILDING_BLOCKS table is the core transactional data store for Oracle E-Business Suite Time and Labor (HXC). It serves as the fundamental repository for all timecard entries, representing the atomic units of recorded work time. Each row in this table constitutes a "building block," which can be a single day, a shift, or a detailed line within a timecard. The table's structure supports a hierarchical model, allowing blocks to be nested (e.g., a daily block containing multiple detail line blocks), which is essential for representing complex time entry and approval workflows. Its central role in the Time and Labor engine makes it critical for all processes involving time entry, validation, approval, and transfer to downstream systems like Payroll.

Key Information Stored

The table's primary identifier is the TIME_BUILDING_BLOCK_ID, uniquely defining each block. The OBJECT_VERSION_NUMBER (OVN) column works in conjunction with the ID to enforce optimistic locking and data integrity during concurrent updates. Key structural columns include PARENT_BUILDING_BLOCK_ID and PARENT_BUILDING_BLOCK_OVN, which establish the parent-child relationships between blocks, forming the timecard hierarchy. The APPROVAL_STYLE_ID links the block to its defined approval process in the HXC_APPROVAL_STYLES table. While the provided metadata does not list all columns, typical attributes stored would include resource (employee) ID, date, hours, time entry status, and creation metadata, which are linked via the HXC_TIME_ATTRIBUTE_USAGES table.

Common Use Cases and Queries

This table is central to reporting, data fixes, and integration audits. Common scenarios include tracing the approval chain of a timecard, identifying time entries for a specific employee within a date range, or diagnosing errors flagged against time blocks. A typical query pattern involves joining to related attribute tables to retrieve the actual time values and descriptive information.

  • Sample Query: Find top-level timecard blocks for an employee:
    SELECT time_building_block_id, object_version_number
    FROM hxc_time_building_blocks
    WHERE resource_id = :p_employee_id
    AND parent_building_block_id IS NULL
    AND DATE BETWEEN :p_start_date AND :p_end_date;
  • Reporting Use Case: Generating a report of all time blocks currently in an error state by joining with the HXC_ERRORS table using the TIME_BUILDING_BLOCK_ID and OVN.

Related Objects

The HXC_TIME_BUILDING_BLOCKS table has extensive relationships within the Time and Labor schema, as indicated by its foreign keys. Key dependencies include:

  • HXC_TIME_ATTRIBUTE_USAGES: Stores the actual attribute values (hours, project, task) for each time building block.
  • HXC_TRANSACTION_DETAILS: Tracks the history of changes made to each building block for auditing and processing.
  • HXC_LOCKS: Manages concurrent user access and editing locks on specific time blocks.
  • HXC_ERRORS: Holds validation and processing errors associated with a block.
  • Self-Referential Foreign Key: The table references itself to maintain the parent-child hierarchy of timecard components.
  • HXC_APPROVAL_STYLES: Defines the approval workflow applied to the time entry.