Results for “hxc_time_attributes_bk”

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

Overview

HXC_TIME_ATTRIBUTES_BK is a backup table in the HXC (Time and Labor Engine) product schema of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to hold a backup copy of HXC_TIME_ATTRIBUTES during consolidation processing. Time attributes in HXC store the descriptive, flexfield-style context that qualifies a time record—typically the DFF segments (ATTRIBUTE1 through ATTRIBUTE30) attached to a time entry, along with process tracking and reference columns. The "_BK" suffix denotes a shadow or archival copy rather than an operational table consumed by the Time and Labor runtime. It exists primarily to protect attribute data during destructive consolidation routines, allowing recovery if a consolidation run needs to be reversed or audited.

In ETRM release 12.2.2 the table is documented with 38 columns in the HXC schema and a single unique index, HXC_TIME_ATTRIBUTES_BK_PK, on TIME_ATTRIBUTE_ID. A heuristic Data Vault classification mined from the foreign-key structure labels this object as a standalone table; as a modeling suggestion it behaves most like a satellite or staging copy, since it does not anchor a hub of shared business keys but instead duplicates descriptive attribute context around a time attribute identifier. It carries no independent historical versioning semantics of its own—row lifetime is bounded by the consolidation cycle that created it.

Key Information Stored

The most significant columns documented for this object are:

• TIME_ATTRIBUTE_ID — the surrogate primary key and the unique index column (HXC_TIME_ATTRIBUTES_BK_PK). It is also the FK reference back to HXC_TIME_ATTRIBUTES, so it preserves the identity of the source row being backed up.
• PROCESS_ID — identifies the consolidation or batch process run that copied the rows into this backup table.
• SEQNO — sequencing value supporting ordered retrieval of the backup set.
• ATTRIBUTE_CATEGORY — the descriptive flexfield context name, qualifying how the DFF segments are interpreted.
• ATTRIBUTE1 – ATTRIBUTE30 — the descriptive flexfield segment values carried over verbatim from HXC_TIME_ATTRIBUTES. These make up the bulk of the 38 columns and hold the customer-configured time-entry context.
• BLD_BLK_INFO_TYPE_ID — reference to HXC_BLD_BLK_INFO_TYPES, governing the block/build information type associated with the attribute row.
• OBJECT_VERSION_NUMBER — the optimistic locking version column used by OAF-based maintenance, retained in the backup for traceability.
• CONSOLIDATED_FLAG — indicates whether the source row had already been processed by consolidation at the time of backup.
• DATA_SET_ID — associates the row with a specific data set partition, relevant in multi-set or multi-organization configurations.

The surrogate key (TIME_ATTRIBUTE_ID) is distinct from any business-key candidate here; the only documented unique index on this table is the primary key itself, and there is no alternate unique constraint documented. Business identity effectively derives from the parent HXC_TIME_ATTRIBUTES record.

Common Use Cases and Queries

The principal use case is forensic: recovering or reconciling time attribute data after a consolidation run has modified or removed rows in HXC_TIME_ATTRIBUTES. DBAs and support analysts compare the backup against the live table to detect lost or altered DFF segments.

A typical reconciliation query joins the backup to the live table on the shared surrogate key:

• SELECT b.TIME_ATTRIBUTE_ID, b.ATTRIBUTE_CATEGORY, b.ATTRIBUTE1, t.ATTRIBUTE1 live_attr1 FROM hxc_time_attributes_bk b, hxc_time_attributes t WHERE b.time_attribute_id = t.time_attribute_id AND NVL(b.attribute1,'#') <> NVL(t.attribute1,'#');
• Process-scoped extraction: SELECT * FROM hxc_time_attributes_bk WHERE process_id = :p_process_id ORDER BY seqno;
• Data set audit: SELECT data_set_id, consolidated_flag, COUNT(*) FROM hxc_time_attributes_bk GROUP BY data_set_id, consolidated_flag;

Reporting use cases include validating that consolidation preserved DFF values, sizing the backup population before purging old consolidation cycles, and tracing BLD_BLK_INFO_TYPE_ID distributions through the join to HXC_BLD_BLK_INFO_TYPES. Because the table is a transient copy, queries should always be scoped by PROCESS_ID or run date rather than treated as a stable reporting source.

Related Objects

The most significant objects related to HXC_TIME_ATTRIBUTES_BK, based on the documented foreign keys and Time and Labor schema:

• HXC_TIME_ATTRIBUTES — the source table this object backs up; joined on TIME_ATTRIBUTE_ID, which is both the PK of the backup and the referenced key.
• HXC_BLD_BLK_INFO_TYPES — referenced via BLD_BLK_INFO_TYPE_ID; supplies the block information type definition.
• HXC_TIME_ATTRIBUTES_BK_PK — the unique index enforcing the primary key on TIME_ATTRIBUTE_ID.
• HXC_TIME_ENTRIES / HXC_TIME_ENTRY_ITEMS — the parent time entry tables whose attributes ultimately flow through HXC_TIME_ATTRIBUTES, providing the operational context for the backed-up flexfield values.
• HXC_CONSOLIDATION / HXC_BATCH processes — the consolidation and batch routines referenced by PROCESS_ID that determine when rows appear and when they may be purged.
• HXC_TIME_ATTRIBUTES_TL / DFF metadata (FND_DESCR_FLEX_COLUMN_USAGES) — defines the meaning of ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 as configured for the Time and Labor descriptive flexfield.

Because the table is standalone with only two outgoing references, its dependency graph is narrow; impact analysis should focus on the consolidation programs that populate it and the reconciliation reporting that consumes it.