Search Results alias_value_name

Overview

The view APPS.HXC_TIME_CATEGORY_COMPS_V is a denormalized reporting and integration layer within the Oracle E-Business Suite Time and Labor Engine (HXC) module. It exposes the components that make up a time category definition, joining the raw component rows in HXC_TIME_CATEGORY_COMPS against descriptive metadata so that components can be presented in human-readable form. The view is central to any activity that builds, inspects, or migrates time category rules across EBS 12.1.1 and 12.2.2, because it resolves opaque identifiers such as mapping component IDs, flex value IDs, lookup codes, and formula references into meaningful names.

Because the underlying table stores polymorphic component definitions, the view uses a UNION to present the different component families through a single consistent projection, with several columns populated conditionally depending on the component type.

Underlying Base Objects

The view is defined primarily over HXC_TIME_CATEGORY_COMPS, aliased TCC, joined to HXC_MAPPING_COMPONENTS_V (MPC) and the HR_LOOKUPS view (LK). The documented referenced base objects also include FND_FLEX_VALUE_SETS, FF_FORMULAS_F, HXC_TIME_CATEGORIES, and the package HXC_TIME_CATEGORY_UTILS_PKG, which supplies the GET_FLEX_VALUE function used to decode value IDs. Additional documented dependencies include FND_LOOKUP_VALUES, FND_SESSIONS, the HR_API package, and the alias family of objects (HXC_ALIAS_DEFINITIONS, HXC_ALIAS_TYPES, HXC_ALIAS_TYPE_COMPONENTS, HXC_ALIAS_VALUES), together with HXC_BLD_BLK_INFO_TYPES and HXC_MAPPING_COMPONENTS. The lookup join resolves the IS_NULL flag against lookup type HXC_TIME_CATEGORY_IS_NULL, and the mapping component view provides building-block context, segment, and end-user column names.

Key Columns

• TIME_CATEGORY_COMP_ID — primary identifier of the component row.
• TIME_CATEGORY_ID and REF_TIME_CATEGORY_ID — the owning time category and any referenced category.
• TYPE — discriminates the component family; the first UNION branch restricts to 'MC' mapping components.
• COMPONENT_TYPE_ID — identifier of the specific component definition.
• FLEX_VALUE_SET_ID and VALUE_ID — drive the decoded VALUE column via HXC_TIME_CATEGORY_UTILS_PKG.GET_FLEX_VALUE.
• EQUAL_TO — the comparison operator/constant used when matching the component; central to the search term "equal_to".
• IS_NULL and IS_NULL_MEANING — whether the component tests for a null condition, with the lookup meaning.
• SEGMENT, CONTEXT, CATEGORY, MAPPING_COMPONENT_NAME, END_USER_COLUMN_NAME — mapping metadata describing where the component applies.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing time category rule configuration, diagnosing why a mapping did or did not fire, and extracting rule definitions for migration or documentation. Filtering on EQUAL_TO is common when locating components that match a specific comparison value.

The following query lists components for a given time category, showing the comparison value and decoded flex value:

SELECT time_category_id, type, component_type_id,
       equal_to, is_null_meaning, value, segment, context
  FROM apps.hxc_time_category_comps_v
 WHERE time_category_id = :p_time_category_id
 ORDER BY time_category_comp_id;

To isolate components using a specific comparison value:

SELECT time_category_id, component_type_id, equal_to, value
  FROM apps.hxc_time_category_comps_v
 WHERE equal_to = :p_value;

Because several columns are populated only in certain UNION branches (for example, VALUE versus VALUE_SET_NAME), reports should filter by TYPE or coalesce the descriptive columns to avoid null-valued output. Restrict queries on TYPE = 'MC' when only mapping components are required.