Results for “hxc_time_attribute_usages_ar”

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

Overview

HXC_TIME_ATTRIBUTE_USAGES_AR is the archive table for the Time Attribute Usages entity within the Oracle E-Business Suite Time and Labor Engine (HXC) module. The Time and Labor Engine provides the core infrastructure through which Oracle Time and Labor captures, validates, and processes timecard entries and other time-related transactions. The operational table HXC_TIME_ATTRIBUTE_USAGES records the association between a time attribute definition and the time building blocks to which that attribute is applied. Its archive counterpart, HXC_TIME_ATTRIBUTE_USAGES_AR, preserves the same association records after they have been moved out of the live operational set, typically through an archival or purge process.

The archived content mirrors the operational definition, holding one row per time attribute usage. From a Data Vault modeling perspective, the mined metadata classifies this object as standalone, meaning it does not itself act as a hub or link in a strict Data Vault sense; it is best treated as a satellite-style historical archive that retains attributes associated with a time attribute usage identifier. The table is owned by the HXC schema and is documented as a valid object in both Oracle EBS 12.1.1 and 12.2.2 releases, with a documented physical schema of eleven columns in 12.2.2.

Key Information Stored

The primary surrogate key is TIME_ATTRIBUTE_USAGE_ID, enforced by the unique index HXC_TIME_ATTR_USAGES_AR_PK. This column is the business-key candidate for the archive row and also carries a documented foreign key back to HXC_TIME_ATTRIBUTE_USAGES, allowing the archived row to be traced to the originating operational record.

• TIME_ATTRIBUTE_USAGE_ID — surrogate primary key and unique index column; identifies each archived usage record.
• TIME_ATTRIBUTE_ID — foreign key to HXC_TIME_ATTRIBUTES; identifies the time attribute definition being applied.
• TIME_BUILDING_BLOCK_ID — identifies the time building block to which the attribute usage applies.
• TIME_BUILDING_BLOCK_OVN — object version number of the associated time building block, supporting concurrency consistency.
• DATA_SET_ID — identifies the data set (business group / legislation context) to which the record belongs.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework during updates.

The remaining columns are the standard Oracle Applications audit and WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These record the user and timestamp of row creation and last modification, which is essential for audit and reconciliation reporting on archived data.

Common Use Cases and Queries

The principal use of this table is historical and audit reporting. Because live usage rows are purged from HXC_TIME_ATTRIBUTE_USAGES, this archive retains the evidence required for compliance, dispute resolution, and trend analysis. A typical reconciliation query joins the archive to its operational parent to identify which records have been archived:

SELECT a.time_attribute_usage_id, a.time_attribute_id, a.time_building_block_id
FROM hxc.hxc_time_attribute_usages_ar a
WHERE a.time_attribute_id = :p_attribute_id;

Administrators also use the archive to confirm that a purge completed successfully, and to reconstruct the attribute usage history for a specific time building block by joining TIME_BUILDING_BLOCK_ID back to the appropriate building block table. Because the table is typically not exposed through standard concurrent programs or forms, access is generally limited to DBA-style query reporting and custom extracts.

Related Objects

• HXC_TIME_ATTRIBUTE_USAGES — the operational source table; joined on TIME_ATTRIBUTE_USAGE_ID.
• HXC_TIME_ATTRIBUTES — referenced via TIME_ATTRIBUTE_ID; defines the attribute swept into the archive.
• Time building block tables — referenced via TIME_BUILDING_BLOCK_ID and TIME_BUILDING_BLOCK_OVN; these anchor the usage to a specific timecard building block.
• HXC_TIME_ATTRIBUTE_USAGES_AR_PK — the unique index enforcing the surrogate key.

In practice, HXC_TIME_ATTRIBUTE_USAGES_AR should be treated as a dependent archive of HXC_TIME_ATTRIBUTE_USAGES, and any reporting solution should reconcile the two tables on TIME_ATTRIBUTE_USAGE_ID to obtain a complete view of attribute usage across the live and archived lifecycle.