Results for “hxc_time_attributes_ar”

50+ results




Overview
Explore in AI Chat

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

Overview

The HXC_TIME_ATTRIBUTES_AR table, owned by the HXC schema within the Oracle Time and Labor Engine (HXC) product, serves as the archive repository for time attribute records. Its documented description is "Time Attributes Archive." In Oracle EBS 12.1.1 and 12.2.2, this table preserves historical or archived copies of the descriptive and flexible attribute data associated with time records, allowing the operational table HXC_TIME_ATTRIBUTES to remain lean while retaining referential history for audit, reconciliation, and reporting purposes.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a standalone entity rather than a true hub, link, or satellite. Because its relationships are consolidated into a small number of outbound references and it carries no downstream dependents, treating it as a standalone archive entity—analogous to a satellite snapshot rather than a joined hub—is a reasonable heuristic when designing downstream models. This classification is a modeling suggestion only, derived from the FK topology documented in ETRM 12.2.2.

Key Information Stored

The table is documented with 36 physical columns. The most significant are:

  • TIME_ATTRIBUTE_ID — The surrogate primary key, enforced by the unique index HXC_TIME_ATTRIBUTES_AR_PK. It also acts as the foreign-key link back to HXC_TIME_ATTRIBUTES, establishing the archive-to-operational relationship.
  • ATTRIBUTE_CATEGORY — The descriptive category (flexfield context) under which the flexible attribute values are grouped.
  • ATTRIBUTE1 through ATTRIBUTE30 — Thirty generic descriptive flexfield (DFF) segments holding user-defined time attribute values. These carry the bulk of the archived payload.
  • BLD_BLK_INFO_TYPE_ID — A foreign key to HXC_BLD_BLK_INFO_TYPES that identifies the build-block information type associated with the attribute set.
  • OBJECT_VERSION_NUMBER — The optimistic-locking version counter used to detect concurrent updates.
  • CONSOLIDATED_FLAG — A flag indicating whether the archived record has been consolidated.
  • DATA_SET_ID — Identifies the data set (business group or data grouping) to which the record belongs, supporting multi-tenant partitioning within the HXC engine.

The documented unique index HXC_TIME_ATTRIBUTES_AR_PK(TIME_ATTRIBUTE_ID) is the business-key candidate that uniquely identifies each archived attribute row.

Common Use Cases and Queries

Typical usage centers on reconciling archived attribute data against the live HXC_TIME_ATTRIBUTES table, and on extracting DFF values for historical reporting.

  • Reconciliation of archived versus current records by joining on the shared TIME_ATTRIBUTE_ID.
  • Reporting on flexible attribute values by pivoting ATTRIBUTE1–ATTRIBUTE30 for a given ATTRIBUTE_CATEGORY.
  • Filtering archived rows by DATA_SET_ID for data-set-specific audits.
  • Identifying build-block attribute histories through BLD_BLK_INFO_TYPE_ID.

A representative query pattern:

SELECT a.TIME_ATTRIBUTE_ID, a.ATTRIBUTE_CATEGORY, a.ATTRIBUTE1, a.CONSOLIDATED_FLAG FROM HXC.HXC_TIME_ATTRIBUTES_AR a WHERE a.DATA_SET_ID = :data_set_id AND a.OBJECT_VERSION_NUMBER = (SELECT MAX(b.OBJECT_VERSION_NUMBER) FROM HXC.HXC_TIME_ATTRIBUTES_AR b WHERE b.TIME_ATTRIBUTE_ID = a.TIME_ATTRIBUTE_ID);

Related Objects

  • HXC_TIME_ATTRIBUTES — Joined on TIME_ATTRIBUTE_ID; the operational source table from which archive rows are derived.
  • HXC_BLD_BLK_INFO_TYPES — Joined on BLD_BLK_INFO_TYPE_ID; provides the build-block information type definition.
  • HXC_TIME_ATTRIBUTES_AR_PK — The unique index enforcing the primary key on TIME_ATTRIBUTE_ID.
  • HXC_TIME_ATTRIBUTES_ARS-class archive staging objects and related HXC archive tables that follow the same _AR naming convention.
  • Time and Labor DFF value-set views that decode ATTRIBUTE_CATEGORY and the ATTRIBUTE1–30 segments.

Because the table is documented as standalone with no downstream dependents, its role is primarily archival and read-oriented within the HXC Time and Labor Engine.