Results for “data_set_id”

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

Overview

HXC_TIME_ATTRIBUTE_USAGES is a reference table within the Oracle Time and Labor Engine (HXC) product family. It records the association between a defined Time Attribute and the Time Building Block on which that attribute is used. In effect, it documents where and how individual time attributes are applied within the Time and Labor rule and building-block infrastructure, enabling the engine to resolve which attribute values are captured, evaluated, or passed downstream during time entry, approval, and payroll processing.

The table is owned by the HXC schema and is marked VALID in the ETRM 12.1.1 / 12.2.2 documentation set. Its documented physical footprint comprises eleven columns. From a heuristic Data Vault modeling perspective, the FK structure mined from the metadata suggests a link classification: the table sits between HXC_TIME_ATTRIBUTES and HXC_TIME_BUILDING_BLOCKS, carrying foreign key references to both rather than acting as an independent hub or a descriptive satellite. This classification should be treated as a modeling suggestion rather than a mandated design.

Key Information Stored

The table is anchored by a single-column surrogate primary key, TIME_ATTRIBUTE_USAGE_ID, enforced by the unique index HXC_TIME_ATTRIBUTE_USAGES_PK. No additional unique indexes are documented, so this primary key is the only documented business-key candidate; it is a system-generated surrogate rather than a natural key.

• TIME_ATTRIBUTE_USAGE_ID — Surrogate primary key uniquely identifying each usage record.
• TIME_ATTRIBUTE_ID — Foreign key to HXC_TIME_ATTRIBUTES, identifying which time attribute is being used.
• TIME_BUILDING_BLOCK_ID — Foreign key to HXC_TIME_BUILDING_BLOCKS, identifying the building block on which the attribute is applied.
• TIME_BUILDING_BLOCK_OVN — Object version number of the referenced building block, supporting optimistic locking and version alignment.
• OBJECT_VERSION_NUMBER — Standard EBS optimistic-locking column for the row itself.
• DATA_SET_ID — Identifies the data set (typically a legislative or business group context) to which the usage row belongs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the record and when.

Common Use Cases and Queries

Typical usage centres on tracing which attributes are configured against a given building block, or conversely locating all building blocks that consume a particular attribute.

• Attributes for a building block: SELECT tau.time_attribute_id FROM hxc_time_attribute_usages tau WHERE tau.time_building_block_id = :block_id;
• Building blocks consuming an attribute: SELECT tau.time_building_block_id FROM hxc_time_attribute_usages tau WHERE tau.time_attribute_id = :attr_id;
• Joined attribute descriptions: join to HXC_TIME_ATTRIBUTES on TIME_ATTRIBUTE_ID to render attribute names and types for configuration reports.
• Data set scoped reporting: filter on DATA_SET_ID when reporting across legislative data groups.
• Change auditing: use LAST_UPDATE_DATE and LAST_UPDATED_BY for configuration drift and audit trails.

Related Objects

• HXC_TIME_ATTRIBUTES — referenced on TIME_ATTRIBUTE_ID; holds the attribute definition.
• HXC_TIME_BUILDING_BLOCKS — referenced on TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN; holds building-block definitions.
• HXC_TIME_ATTRIBUTE_USAGES_BK — backup/interim table referencing TIME_ATTRIBUTE_USAGE_ID.
• HXC_TIME_ATTRIBUTE_USAGES_AR — archive table referencing TIME_ATTRIBUTE_USAGE_ID.
• HXC_TIME_ATTRIBUTE_USAGES_PK — primary key index enforcing uniqueness on TIME_ATTRIBUTE_USAGE_ID.