Search Results hxc_alias_values




Overview
Explore in AI Chat

Overview

The HXC_ALIAS_VALUES table resides in the HXC schema, which supports the Oracle Time and Labor Engine (HXC) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores alternate name components — discrete, configurable values that represent the individual segments or elements used to construct a person's full or alternate name. Each row corresponds to a single alias value, such as a title, suffix, salutation component, or other naming element, that is governed by a parent alias definition.

Functionally, HXC_ALIAS_VALUES acts as a reference and configuration table. It is queried by Time and Labor name-generation logic, by application forms that present users with lists of permitted name components, and by integrations that need to resolve an alias value identifier into a human-readable string. Because the table carries effective date logic and an enabled flag, it supports time-bounded, selectively active reference data rather than a static code list.

The provided metadata classifies this object heuristically as satellite-leaning under a Data Vault modeling interpretation. This suggests HXC_ALIAS_VALUES is best understood as descriptive attribute data attached to a parent concept — the alias definition — rather than as an independent hub of business keys or a link resolving a many-to-many relationship. The single foreign key to HXC_ALIAS_DEFINITIONS reinforces this satellite reading.

Key Information Stored

Although the documented physical schema contains forty-four columns, the substantive business content is concentrated in a small number of them.

  • ALIAS_VALUE_ID — the surrogate primary key, defined through the HXC_ALIAS_VALUES_PK unique index. This is an internally generated system identifier and carries no business meaning.
  • ALIAS_DEFINITION_ID — the foreign key to HXC_ALIAS_DEFINITIONS, establishing which alias definition (for example, a particular naming component category) the value belongs to.
  • ALIAS_VALUE_NAME — the descriptive, user-facing text of the alias value, such as the literal string presented in a name component list.
  • ENABLED_FLAG — controls whether the value is selectable and active. Disabled rows remain in the table for historical reference but are excluded from current pick lists and generation logic.
  • DATE_FROM and DATE_TO — the effective dating range that bounds when the alias value is valid for use.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS who-columns supporting audit and concurrency tracing.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework to detect stale updates.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard descriptive flexfield (DFF) storage block, allowing customers to extend alias value records with site-specific data.

The documented unique index includes both ALIAS_VALUE_ID and ZD_EDITION_NAME, reflecting the editioning infrastructure present in 12.2.x. From a business-key standpoint, the meaningful combination is ALIAS_DEFINITION_ID together with the alias value name and effective dates, since a value is only unique within its owning definition.

Common Use Cases and Queries

The most frequent reporting requirement is retrieving active alias values for a given definition, typically for validation or list-of-values replication.

  • Listing enabled values within an effective date window: select ALIAS_VALUE_NAME from HXC_ALIAS_VALUES where ALIAS_DEFINITION_ID = :p_def_id and ENABLED_FLAG = 'Y' and trunc(sysdate) between DATE_FROM and nvl(DATE_TO, sysdate + 1).
  • Joining to the parent definition to resolve the human-readable context: select v.ALIAS_VALUE_NAME, d.ALIAS_DEFINITION_NAME from HXC_ALIAS_VALUES v, HXC_ALIAS_DEFINITIONS d where v.ALIAS_DEFINITION_ID = d.ALIAS_DEFINITION_ID.
  • Auditing recently changed reference data using LAST_UPDATE_DATE to identify values modified after a given timestamp.
  • Reporting on flexfield usage by inspecting ATTRIBUTE_CATEGORY and the ATTRIBUTE1–ATTRIBUTE30 columns when a customer has configured descriptive flexfields against alias values.
  • Data migration and conversion validation, confirming that each source alias value maps to a single definition and an active date range.

Because the table is small and reference-oriented, queries against it are inexpensive; however, joins should always respect the ALIAS_DEFINITION_ID relationship to avoid cross-definition duplication.

Related Objects

  • HXC_ALIAS_DEFINITIONS — the direct parent of this table, joined on HXC_ALIAS_VALUES.ALIAS_DEFINITION_ID = HXC_ALIAS_DEFINITIONS.ALIAS_DEFINITION_ID. This is the only documented foreign key relationship.
  • HXC_ALIAS_ASSIGNMENTS — typically references alias values when a component is assigned to a person or organization name record.
  • PER_ALL_PEOPLE_F — the HR foundation table whose name construction may draw on alias values through Time and Labor name-generation logic.
  • HXC_TIME_ATTRIBUTES / HXC_TIME_BUILDING_BLOCKS — related HXC configuration objects that share the Time and Labor Engine's reference-data patterns.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — the standard flexfield value infrastructure, relevant where customers model alias values as flexfield-driven rather than table-driven reference data.
  • HXC_ALIAS_VALUES_PK — the unique index enforcing the primary key on ALIAS_VALUE_ID (with ZD_EDITION_NAME in 12.2.x), which governs how the table is accessed and maintained.