Search Results d_reference_object_name

Overview

HXC_ALIAS_TYPES_V is an Oracle Application Object Library (APPS) view owned by the APPS schema and exposed through the HXC – Time and Labor Engine product module. It functions as a reporting and integration surface over the HXC_ALIAS_TYPES configuration table, resolving raw reference object identifiers into human-readable names. In Oracle EBS 12.1.1 and 12.2.2, the view delivers a denormalized, presentation-ready projection of alias type definitions used by the Time and Labor Engine for alternate name resolution, value set references, and descriptive flexfield context lookups. Because the view performs the translation from internal identifiers to descriptive names, it is a common target for concurrent programs, BI Publisher reports, Oracle Applications Framework (OAF) pages, and inbound/outbound integration extracts that need to display or validate alias type configuration without implementing their own join logic.

Underlying Base Objects

The view is defined as a UNION of two SELECT branches, both anchored on the HXC_ALIAS_TYPES table (exposed to APPS as a synonym). The first branch restricts to ALIAS_TYPE values of VALUE_SET_NONE, VALUE_SET_TABLE, and VALUE_SET_INDEPENDENT, joining HXC_ALIAS_TYPES.REFERENCE_OBJECT to FND_FLEX_VALUE_SETS (synonym) via FLEX_VALUE_SET_ID to derive the descriptive name D_REFERENCE_OBJECT_NAME. The second branch handles ALIAS_TYPE = 'OTL_ALT_DDF', joining REFERENCE_OBJECT to FND_DESCR_FLEX_CONTEXTS_VL through DESCRIPTIVE_FLEX_CONTEXT_CODE. Both branches additionally invoke the HR_BIS package function BIS_DECODE_LOOKUP('HXC_ALT_NAME_TYPE', ALIAS_TYPE) to translate the alias type code into its decoded lookup meaning. The documented referenced base objects are therefore FND_DESCR_FLEX_CONTEXTS_VL (VIEW), FND_FLEX_VALUE_SETS (SYNONYM), HR_BIS (PACKAGE), and HXC_ALIAS_TYPES (SYNONYM).

Key Columns

• ALIAS_TYPE_ID – Primary identifier of the alias type row; surrogate key from HXC_ALIAS_TYPES.
• ALIAS_TYPE – The functional classification (for example VALUE_SET_NONE, VALUE_SET_TABLE, VALUE_SET_INDEPENDENT, OTL_ALT_DDF) driving which union branch the row originates from.
• REFERENCE_OBJECT – The underlying identifier, interpreted variably as a flex value set ID or a descriptive flexfield context code depending on ALIAS_TYPE.
• D_REFERENCE_OBJECT_NAME – Derived descriptive name: FLEX_VALUE_SET_NAME for value set branches, DESCRIPTIVE_FLEX_CONTEXT_NAME for the OTL_ALT_DDF branch.
• MEANING – Decoded display text produced by HR_BIS.BIS_DECODE_LOOKUP against the HXC_ALT_NAME_TYPE lookup, providing a user-facing label for the alias type.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE – Standard Who columns for audit trail and incremental extract filtering.
• OBJECT_VERSION_NUMBER – Optimistic locking and row versioning attribute, useful in integration payloads.

Common Use Cases and Queries

Typical uses include validating alias type configuration before loading timecard data, populating LOVs in custom OAF or Forms pages, and building extracts that reconcile flex value sets and descriptive flexfield contexts against Time and Labor alias definitions. A representative query returns decoded alias types with their descriptive references:

SELECT alias_type_id, alias_type, reference_object, d_reference_object_name, meaning FROM apps.hxc_alias_types_v WHERE alias_type = :p_alias_type ORDER BY d_reference_object_name;

To audit recently changed configuration, filter on the Who columns:

SELECT alias_type, reference_object, d_reference_object_name, last_updated_by, last_update_date FROM apps.hxc_alias_types_v WHERE last_update_date >= :p_since;

For integrations that must distinguish value-set-backed alias types from flexfield-backed ones, use ALIAS_TYPE as the discriminator and treat REFERENCE_OBJECT accordingly. Because the view is a UNION with no aggregations, it is safely consumed in read-only reporting and can be indexed downstream via materialized views when high-volume extraction is required.