Results for “alias_type_id”

50+ results




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

Overview

HXC_ALIAS_TYPES is a reference table in the HXC schema owned by the Time and Labor Engine product within Oracle E-Business Suite. It stores the definitions of alternate name types (aliases) that can be applied to timecard and labor-related entities. Each alias type describes a category of alternate identifier that may be resolved either through a Descriptive Flexfield (DDF) context definition or through an Oracle value set, giving the Time and Labor Engine a flexible mechanism to attach user-defined identifiers to workers, assignments, or other records.

From a modeling perspective, the FK relationship metadata suggests a hub-leaning classification under Data Vault heuristics. This reflects the table's role as a stable, keyed registry of alias-type business entities around which dependent component and definition records are associated.

Key Information Stored

The table contains 10 documented columns. The most significant are described below.

  • ALIAS_TYPE_ID — the surrogate primary key. It is enforced by the HXC_ALIAS_TYPES_PK constraint, which is defined over ALIAS_TYPE_ID together with ZD_EDITION_NAME. This column uniquely identifies each alias type and is the value propagated to child tables.
  • ALIAS_TYPE — the business identifier for the alias type, participating in the unique index HXC_ALIAS_TYPES_UK1 (ALIAS_TYPE, REFERENCE_OBJECT, ZD_EDITION_NAME). This is the natural key by which applications and reports typically look up a type.
  • REFERENCE_OBJECT — the object or entity to which the alias type applies. Together with ALIAS_TYPE it forms the business-key candidate, ensuring an alias type is unique within the scope of a referenced object.
  • ZD_EDITION_NAME — the editioning column that supports the Oracle EBS 12.2 online patching (AD Online Patching) architecture. It appears in both the primary key and the unique index, so every logical lookup must account for the active edition.
  • Object version and audit columns — OBJECT_VERSION_NUMBER supports optimistic locking for concurrent updates, while CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard "WHO" audit tracking consistent with the EBS data model.

Common Use Cases and Queries

Alias types are referenced whenever an application needs to interpret or validate an alternate identifier supplied for a time and labor record. Typical reporting and diagnostic queries resolve a type from its business key or retrieve all types for a reference object.

  • Look up a type by its business key: SELECT alias_type_id, alias_type, reference_object FROM hxc_alias_types WHERE alias_type = :p_type AND reference_object = :p_obj AND zd_edition_name = 'SET1';
  • Enumerate available alias types: SELECT alias_type_id, alias_type, reference_object FROM hxc_alias_types ORDER BY reference_object, alias_type;
  • Join to dependent definitions or components when resolving how a given alias is validated or built.

Because the table is low-volume reference data, it is frequently used as the driving table in lookup joins and in data-conversion or interface mappings that translate external identifiers into Time and Labor Engine identifiers.

Related Objects

HXC_ALIAS_TYPES is referenced by the following key tables, which depend on its primary key:

Together these objects form the alias resolution framework: HXC_ALIAS_TYPES defines the category, HXC_ALIAS_TYPE_COMPONENTS defines how it is constructed from DDF contexts or value sets, and HXC_ALIAS_DEFINITIONS holds the concrete aliases. Application program interfaces that process timecard identifiers ultimately resolve through this trio of tables.