Results for “hxc_time_attribute_usages_bk”

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

Overview

HXC_TIME_ATTRIBUTE_USAGES_BK is a backup (shadow) table in the HXC schema, the Time and Labor Engine module of Oracle E-Business Suite. It mirrors the structure of the primary HXC_TIME_ATTRIBUTE_USAGES table and stores the association between time attributes and the time building blocks that consume them. The "_BK" suffix identifies this as a backup table, typically populated by concurrent programs, upgrade drivers, or data-fix scripts before destructive operations are applied to the primary table, allowing rollback or forensic comparison if the operation fails or produces unexpected results.

The ETRM-supplied Data Vault classification for this object is standalone, mined heuristically from its foreign-key structure. Under a Data Vault modeling lens, this suggests the table behaves as a satellite-like structure: it carries descriptive and auditable attributes surrounding a business relationship, rather than acting as an independent hub of business keys or a link resolving many-to-many relationships. This is a modeling suggestion only; the physical table remains a conventional Oracle relational table with two outbound foreign keys.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• TIME_ATTRIBUTE_USAGE_ID — surrogate primary key of the usage record; also the FK back to HXC_TIME_ATTRIBUTE_USAGES.
• TIME_ATTRIBUTE_ID — FK to HXC_TIME_ATTRIBUTES, identifying the attribute being used.
• TIME_BUILDING_BLOCK_ID — identifies the time building block that consumes the attribute.
• TIME_BUILDING_BLOCK_OVN — object version number of the referenced building block, used for optimistic locking and concurrency validation.
• OBJECT_VERSION_NUMBER — row-level version stamp supporting EBS optimistic locking.
• DATA_SET_ID — multi-tenant / data-set discriminator used by HXC for configuration scoping.
• PROCESS_ID — references the batch or processing context that created or last touched the row.
• SEQNO — ordering sequence for the usage entry.
• CREATED_BY, CREATION_DATE — standard EBS audit creation columns.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit update columns.

The surrogate key is TIME_ATTRIBUTE_USAGE_ID. Business-key uniqueness is not formally documented for this backup table; in the primary table the natural candidate key is the combination of TIME_ATTRIBUTE_ID and TIME_BUILDING_BLOCK_ID.

Common Use Cases and Queries

Because this is a backup table, the principal use cases are recovery, reconciliation, and audit. A typical recovery query compares surviving rows against the backup:

• Row-count reconciliation: SELECT COUNT(*) FROM HXC.HXC_TIME_ATTRIBUTE_USAGES_BK; versus the primary table.
• Orphan detection after a failed purge: outer-join the backup to HXC_TIME_ATTRIBUTES on TIME_ATTRIBUTE_ID to list attributes whose usages disappeared.
• Point-in-time audit: filter on CREATION_DATE or LAST_UPDATE_DATE to reconstruct which usages existed before a deployment or upgrade window.
• Impact analysis: join to HXC_TIME_BUILDING_BLOCK to see which building blocks were affected by a scripted change.
• Restore pattern: insert surviving backup rows back into the primary table where TIME_ATTRIBUTE_USAGE_ID no longer exists.

Related Objects

• HXC_TIME_ATTRIBUTE_USAGES — primary table; joined on TIME_ATTRIBUTE_USAGE_ID.
• HXC_TIME_ATTRIBUTES — attribute definitions; joined on TIME_ATTRIBUTE_ID.
• HXC_TIME_BUILDING_BLOCKS — consuming blocks referenced via TIME_BUILDING_BLOCK_ID.
• HXC_TIME_BUILDING_BLOCK_USAGES — parallel usage mapping for building blocks.
• HXC_TIME_ATTRIBUTE_USAGES_BK variants and HXC shadow tables — created by the same backup programs.
• HXC_TIME_ATTRIBUTES_BK — corresponding backup for attribute definitions.
• EBS concurrent programs and FND_* audited jobs that populate PROCESS_ID and DATA_SET_ID.