Search Results hxc_time_attribute_usages




Overview
Explore in AI Chat

Overview

The HXC_TIME_ATTRIBUTE_USAGES table is a core data object within the Oracle E-Business Suite (EBS) Time and Labor Engine (HXC). It functions as a junction or mapping table, establishing the critical relationship between time entries and their descriptive attributes. In the Time and Labor architecture, a time entry is stored as a Time Building Block (TBB). This table links a specific TBB (representing a segment of worked time) to one or more Time Attributes, which provide the contextual details for that time, such as project number, task, expenditure type, or absence reason. Its role is fundamental to the system's ability to store richly detailed timecard information that can integrate with other EBS modules like Projects, Payroll, and Human Resources.

Key Information Stored

The table's structure is designed to manage the many-to-many relationship between building blocks and attributes. Its primary columns, as indicated by the metadata, are the foreign keys that create these links. The primary key is a unique identifier, TIME_ATTRIBUTE_USAGE_ID. The two most significant foreign key columns are TIME_BUILDING_BLOCK_ID (and its associated object version number, TIME_BUILDING_BLOCK_OVN) and TIME_ATTRIBUTE_ID. The TIME_BUILDING_BLOCK_ID references a specific time entry in the HXC_TIME_BUILDING_BLOCKS table, while the TIME_ATTRIBUTE_ID references a defined attribute in the HXC_TIME_ATTRIBUTES table. This pairing records that a particular attribute is "used by" or "attached to" a specific time building block.

Common Use Cases and Queries

A primary use case is retrieving all attribute details for a given time entry or a set of timecards for reporting or validation. For instance, an integration process to Oracle Projects would query this table to extract all project and task attributes attached to submitted time building blocks. A common reporting need is to list time entries with their associated project details. A sample SQL pattern would join HXC_TIME_ATTRIBUTE_USAGES to both the building block and attribute tables, often filtering on attribute names or timecard submission dates.

SELECT htb.time_building_block_id,
       hta.attribute_name,
       hta.attribute_value
  FROM hxc_time_attribute_usages htau,
       hxc_time_building_blocks htb,
       hxc_time_attributes hta
 WHERE htau.time_building_block_id = htb.time_building_block_id
   AND htau.time_attribute_id = hta.time_attribute_id
   AND hta.attribute_name = 'PROJECT_NUMBER'
   AND htb.scope = 'TIMECARD';

Related Objects

  • HXC_TIME_BUILDING_BLOCKS: This is the primary parent table, as defined by the foreign key. It stores the core time entry data (hours, date, resource).
  • HXC_TIME_ATTRIBUTES: The other primary parent table, referenced by the TIME_ATTRIBUTE_ID foreign key. It stores the actual attribute name-value pairs (e.g., PROJECT_NUMBER=100).
  • HXC_TIME_ATTRIBUTE_USAGES_PK: The primary key constraint on the TIME_ATTRIBUTE_USAGE_ID column, ensuring each mapping is unique.

Understanding the relationships between these three tables—HXC_TIME_BUILDING_BLOCKS, HXC_TIME_ATTRIBUTES, and HXC_TIME_ATTRIBUTE_USAGES—is essential for any technical work involving Time and Labor data extraction, migration, or extension.