Search Results alias_context_name

Overview

APPS.HXC_ALIAS_DEFINITIONS_V is a supplementary view in the Oracle E-Business Suite APPS schema that exposes alias definition records used by the Time and Labor (HXC) module. In EBS terminology an "alias" is a configurable shortcut or lookup that maps a user-friendly label to an underlying value—commonly a time attribute, approval status, or preference element—so that application logic and setup forms can reference values by name rather than by internal identifier. The view's primary purpose is to simplify coding of Oracle Forms-based setup and maintenance screens, joining the alias definition base tables to their translated (TL) rows and to descriptive flexfield context metadata.

Because it is classified as a view type "supplementary view used to simplify forms coding," Oracle explicitly cautions that the object is not intended as a stable integration or reporting interface: "Warning: Oracle does not recommend you query or alter data using this view. It may change dramatically in subsequent minor or major releases." Nevertheless, the view is widely referenced in ad hoc reporting, data extraction, and troubleshooting of alias configuration, particularly because it surfaces the descriptive flexfield context name and code in a single row.

Underlying Base Objects

According to the ETRM dependency list, HXC_ALIAS_DEFINITIONS_V is defined over the following objects:

• HXC_ALIAS_DEFINITIONS — the primary base table holding one row per alias definition, including business group, legislation, and who-columns.
• HXC_ALIAS_DEFINITIONS_TL — the translation table supplying language-specific ALIAS_DEFINITION_NAME and DESCRIPTION values, joined on the current session language.
• HXC_ALIAS_TYPES — the lookup table classifying each alias by type (for example, time entry rule, preference, or approval), exposing ALIAS_TYPE and ALIAS_TYPE_ID.
• FND_DESCR_FLEX_CONTEXTS_VL — the descriptive flexfield context view that supplies the flexfield context name surfaced as ALIAS_CONTEXT_NAME.
• FND_FLEX_VALUE_SETS — the flexfield value set definition, referenced to resolve the value set associated with the alias context.

The view is not referenced by any other database object, confirming its role as a terminal, read-only convenience layer rather than a building block for further database logic.

Key Columns

• ALIAS_DEFINITION_ID (NUMBER, 15) — primary identifier of the alias definition.
• ALIAS_DEFINITION_NAME (VARCHAR2, 80) — user-facing name of the alias, sourced from the translated table.
• ALIAS_CONTEXT_NAME (VARCHAR2, 80) — the descriptive flexfield context name associated with the alias, often the value users search for when troubleshooting context-sensitive alias behavior.
• ALIAS_CONTEXT_CODE (VARCHAR2, 30) — the internal context code corresponding to the context name.
• BUSINESS_GROUP_ID (NUMBER, 15) — the HR business group (operating unit) that owns the alias; essential for multi-organization filtering.
• LEGISLATION_CODE (VARCHAR2, 30) — the legislation under which the alias applies, supporting country-specific configurations.
• ALIAS_TYPE / ALIAS_TYPE_ID — classification of the alias and its foreign key into HXC_ALIAS_TYPES.
• PROMPT (VARCHAR2, 240) — the display prompt shown on forms for the alias.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) and OBJECT_VERSION_NUMBER for concurrent update control.

Common Use Cases and Queries

Typical scenarios include validating alias setup after a patch, producing setup documentation, and diagnosing why a flexfield context is not appearing on a Time and Labor form.

Listing all aliases for a business group:

SELECT alias_definition_id,
       alias_definition_name,
       alias_context_name,
       alias_type
  FROM apps.hxc_alias_definitions_v
 WHERE business_group_id = :p_bg_id
 ORDER BY alias_definition_name;

Searching by context name (the user's original query term):

SELECT alias_definition_name,
       alias_context_name,
       alias_context_code,
       legislation_code
  FROM apps.hxc_alias_definitions_v
 WHERE alias_context_name LIKE '%TIME%';

Because the metadata warns against relying on the view for integration, developers should prefer the underlying base tables—HXC_ALIAS_DEFINITIONS and HXC_ALIAS_DEFINITIONS_TL—for any persistent or production interface, reserving the view for diagnostic and read-only reporting queries.