Results for “hxc_time_attributes_pk”

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

Overview

HXC_TIME_ATTRIBUTES is a key configuration table within the Oracle Time and Labor Engine (HXC) product family, present in both Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description defines it as "Time Attributes - attributes for a building block," indicating that it stores the descriptive attribute definitions that qualify building block information types used throughout the Time and Labor rules engine. The table resides in the HXC schema and is classified as VALID, with 36 documented columns in the ETRM 12.2.2 physical schema.

From a Data Vault modeling perspective, the metadata's heuristic classification places this table as hub-leaning. This suggests that HXC_TIME_ATTRIBUTES behaves primarily as a hub entity, anchored by a stable surrogate primary key (TIME_ATTRIBUTE_ID) and referenced by multiple dependent tables. Practitioners designing downstream data marts or integration models may find it useful to treat this table as the central business entity around which satellite attributes and link relationships are organized.

Key Information Stored

The table's primary key is defined by the unique index HXC_TIME_ATTRIBUTES_PK on the TIME_ATTRIBUTE_ID column, which serves as the surrogate identifier for each time attribute record. This column is the only documented unique index, making it the sole business-key candidate surfaced in the metadata.

The most significant columns include:

• TIME_ATTRIBUTE_ID — the surrogate primary key uniquely identifying each attribute record.
• BLD_BLK_INFO_TYPE_ID — a foreign key to HXC_BLD_BLK_INFO_TYPES, tying the attribute to its parent building block information type.
• ATTRIBUTE_CATEGORY — the descriptive category (flexfield context) used to qualify the attribute set.
• ATTRIBUTE1 through ATTRIBUTE30 — a 30-segment descriptive flexfield (DFF) column set, the standard Oracle EBS pattern for storing user-defined attribute values without schema changes.
• OBJECT_VERSION_NUMBER — the standard optimistic locking / row versioning column used for concurrent update control.
• CONSOLIDATED_FLAG — indicates consolidation status of the record.
• DATA_SET_ID — associates the row with a specific data set, supporting multi-set and localization partitioning.

The absence of additional unique indexes beyond the primary key indicates that uniqueness is enforced at the surrogate level rather than through natural business keys documented in this repository.

Common Use Cases and Queries

Typical usage centers on reporting and validating the attribute definitions configured against building block information types. A common query joins the attribute table to its parent type:

• SELECT t.TIME_ATTRIBUTE_ID, t.BLD_BLK_INFO_TYPE_ID, t.ATTRIBUTE_CATEGORY, t.ATTRIBUTE1 FROM HXC_TIME_ATTRIBUTES t WHERE t.BLD_BLK_INFO_TYPE_ID = :p_type_id;

Analysts often inspect the DFF segments (ATTRIBUTE1–ATTRIBUTE30) conditionally on ATTRIBUTE_CATEGORY to reconstruct user-defined attribute meaning. Integrators use the DATA_SET_ID and CONSOLIDATED_FLAG columns to filter records for specific data set or consolidation scenarios. Because the table is referenced by error and usage tables, diagnostics frequently join to HXC_ERRORS and HXC_TIME_ATTRIBUTE_USAGES to trace how a given attribute participates in processing.

Related Objects

The documented foreign key relationships identify the following significant related objects:

• HXC_BLD_BLK_INFO_TYPES — referenced via HXC_TIME_ATTRIBUTES.BLD_BLK_INFO_TYPE_ID; the parent type definition.
• HXC_TIME_ATTRIBUTE_USAGES — references this table via TIME_ATTRIBUTE_ID; records where attributes are applied.
• HXC_ERRORS — references this table via TIME_ATTRIBUTE_ID; captures processing errors associated with attributes.
• HXC_TIME_ATTRIBUTES_BK, HXC_TIME_ATTRIBUTES_AR — backup and audit shadow tables mirroring the base structure.
• HXC_TIME_ATTRIBUTE_USAGES_BK, HXC_TIME_ATTRIBUTE_USAGES_AR — backup and audit shadow tables for usages.

These relationships confirm HXC_TIME_ATTRIBUTES as a hub-like reference entity supporting the Time and Labor Engine's building block configuration and validation logic.