Results for “hxc_time_building_blocks”

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

Overview

HXC_TIME_BUILDING_BLOCKS is the central transactional table in the Oracle EBS Time and Labor Engine (HXC) product. It stores the atomic units of recorded time — the "building blocks" — that the Time and Labor Engine assembles into timecards, evaluates against rules, and ultimately passes to payroll, projects, and other downstream consumers. Each row represents a discrete block of time (or a measurable quantity) with a defined type, measure, and scope, and may itself be a parent container for child blocks through a self-referencing parent-child hierarchy. The table is owned by the HXC schema and contains 25 documented columns in Oracle EBS 12.2.2, with a parallel structure in 12.1.1.

From a Data Vault modeling perspective, the mined relationship data classifies this table as hub-leaning. This heuristic suggests treating TIME_BUILDING_BLOCK_ID as a durable business key hub, with the surrounding descriptive and status attributes (type, measure, approval status, timestamps) modeled as an associated satellite. The self-referencing parent link and the many inbound foreign keys reinforce the table's role as a hub at the center of the HXC transactional network.

Key Information Stored

The primary key, HXC_TIME_BUILDING_BLOCKS_PK, is a composite surrogate key on (TIME_BUILDING_BLOCK_ID, OBJECT_VERSION_NUMBER). This is the only documented unique index and thus the sole business-key candidate; OBJECT_VERSION_NUMBER supports optimistic locking during concurrent updates. The most significant columns are:

• TIME_BUILDING_BLOCK_ID — the surrogate identifier for each time block; the join anchor for the entire HXC schema.
• TYPE and MEASURE — classify the block (for example, a time entry versus a quantity) and the measurable quantity it carries.
• START_TIME, STOP_TIME, DATE_FROM, DATE_TO — the temporal boundaries of the block and its effective dating window.
• UNIT_OF_MEASURE — the unit in which the measure is expressed.
• PARENT_BUILDING_BLOCK_ID and PARENT_BUILDING_BLOCK_OVN — the self-referencing foreign key that establishes the parent-child hierarchy of blocks, paired with the parent's version number.
• RESOURCE_ID and RESOURCE_TYPE — identify the worker, resource, or entity to which the block belongs.
• SCOPE — defines the scope level of the block within the time model.
• APPROVAL_STATUS and APPROVAL_STYLE_ID — the approval state of the block and the foreign key to HXC_APPROVAL_STYLES that governs its routing.
• COMMENT_TEXT — free-form annotation attached to the block.
• APPLICATION_SET_ID and DATA_SET_ID — multi-tenant partitioning of the data within the application set.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and TRANSLATION_DISPLAY_KEY — standard auditing columns and the translation display key for multilingual rendering.

Common Use Cases and Queries

Typical reporting and integration scenarios query blocks by resource and time window to reconstruct timecards or feed payroll:

• Retrieve all blocks for a resource within a period: SELECT * FROM hxc.hxc_time_building_blocks WHERE resource_id = :p_resource AND start_time >= :p_from AND stop_time <= :p_to;
• Reconstruct the hierarchy of parent and child blocks using the self-join: SELECT c.* FROM hxc_time_building_blocks c, hxc_time_building_blocks p WHERE c.parent_building_block_id = p.time_building_block_id AND c.parent_building_block_ovn = p.object_version_number;
• Filter by approval state to isolate pending or rejected entries: WHERE approval_status = :p_status, joined to HXC_APPROVAL_STYLES on APPROVAL_STYLE_ID.
• Join to HXC_TIME_ATTRIBUTE_USAGES to report on attribute values captured against each block, and to HXC_ERRORS to surface validation failures that blocked processing.
• Use HXC_TRANSACTION_DETAILS to correlate a block to its originating transaction, and HXC_LOCKS to detect blocks currently held under a lock.

Related Objects

The table participates in a dense network of documented foreign-key relationships:

• HXC_APPROVAL_STYLES — referenced by HXC_TIME_BUILDING_BLOCKS.APPROVAL_STYLE_ID; supplies the approval routing definition.
• HXC_TIME_BUILDING_BLOCKS (self) — referenced by PARENT_BUILDING_BLOCK_ID and PARENT_BUILDING_BLOCK_OVN, forming the block hierarchy.
• HXC_ERRORS — references TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN; holds processing errors for a block.
• HXC_LOCKS — references TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN; tracks concurrent locking of blocks.
• HXC_TIME_ATTRIBUTE_USAGES — references TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN; stores attribute usage captured per block.
• HXC_TRANSACTION_DETAILS — references TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN; links each block to its source transaction.

Collectively, these dependencies establish HXC_TIME_BUILDING_BLOCKS as the principal hub from which the Time and Labor Engine derives timecards, approvals, error handling, and downstream payroll and project accounting data.