Results for “alias_type_component_id”

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

Overview

HXC_ALIAS_TYPE_COMPONENTS is a Time and Labor Engine (HXC) configuration table that defines the individual components belonging to an alternate name type (alias type). Each row links a component to its parent alias type and to a mapping component that supplies the transformation logic used to derive the alternate name. In this way, the table acts as the bridge between the definition of an alias type and the mapping rules that determine how alias values are constructed from source data.

From a Data Vault modeling perspective, the mined relationship structure classifies this object heuristically as a link. It resolves a many-to-many association between HXC_ALIAS_TYPES and HXC_MAPPING_COMPONENTS through the foreign keys ALIAS_TYPE_ID and MAPPING_COMPONENT_ID. This classification is a modeling suggestion only; the physical object is a standard EBS transactional configuration table with audit and edition columns.

Key Information Stored

The table is owned by the HXC schema and contains 12 documented columns in the 12.2.2 physical schema. The most significant of these are listed below.

• ALIAS_TYPE_COMPONENT_ID — Surrogate primary key, enforced by HXC_ALIAS_TYPE_COMPONENTS_PK. It uniquely identifies each component row.
• ALIAS_TYPE_ID — Foreign key to HXC_ALIAS_TYPES. Identifies the parent alternate name type to which the component belongs.
• MAPPING_COMPONENT_ID — Foreign key to HXC_MAPPING_COMPONENTS. Points to the mapping component that defines how the component value is generated or transformed.
• COMPONENT_NAME — The descriptive name of the component within the alias type.
• COMPONENT_TYPE — Classifies the component, allowing the engine to interpret its role during alias derivation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording the most recent modification.
• CREATION_DATE, CREATED_BY — Audit columns recording initial row creation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to detect concurrent updates.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching; it forms part of the unique index HXC_ALIAS_TYPE_COMPONENTS_PK (ALIAS_TYPE_COMPONENT_ID, ZD_EDITION_NAME).

The business-key candidate identified in the metadata is the composite of ALIAS_TYPE_COMPONENT_ID and ZD_EDITION_NAME. Because ALIAS_TYPE_COMPONENT_ID is itself a generated surrogate, the effective business identity of a component is best understood as the combination of its parent alias type and its mapping component reference.

Common Use Cases and Queries

Typical usage centers on configuration review, troubleshooting alias generation, and impact analysis before changing mapping definitions. A common query pattern joins the table to its two parents to render a complete picture of a configured alias type.

• Listing all components for a given alias type, joined to HXC_MAPPING_COMPONENTS to show the transformation applied.
• Identifying which alias types depend on a specific mapping component, to assess the impact of modifying or retiring that mapping.
• Auditing recently changed configurations using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Validating edition integrity by filtering on ZD_EDITION_NAME during or after an online patching cycle.

A representative pattern is: select c.alias_type_component_id, c.component_name, c.component_type, t.alias_type_name, m.mapping_component_name from hxc_alias_type_components c join hxc_alias_types t on t.alias_type_id = c.alias_type_id join hxc_mapping_components m on m.mapping_component_id = c.mapping_component_id, with an optional predicate on alias_type_id or mapping_component_id for targeted analysis.

Related Objects

The following objects are most significant in relation to HXC_ALIAS_TYPE_COMPONENTS, based on the documented foreign keys and surrounding HXC configuration model.

• HXC_ALIAS_TYPES — Parent table joined via ALIAS_TYPE_ID.
• HXC_MAPPING_COMPONENTS — Referenced table joined via MAPPING_COMPONENT_ID.
• HXC_ALIAS_TYPE_COMPONENTS_PK — Primary key index over ALIAS_TYPE_COMPONENT_ID and ZD_EDITION_NAME.
• HXC_MAPPING_DEFINITIONS and related mapping tables — Provide the broader rule context in which mapping components operate.
• Time and Labor alias derivation logic — Application code and concurrent processes that read these components when generating alternate names.