Search Results qualifier_attribute1

Overview

HXC_LAYOUT_COMPONENTS_V is an APPS-owned view within the HXC – Time and Labor Engine product of Oracle E-Business Suite, valid in both the 12.1.1 and 12.2.2 releases. It presents a denormalized, human-readable projection of the configuration metadata that drives Time and Labor self-service layouts. Each row describes a single layout component — a field, region item, or display element — together with its definition, its rendering characteristics, and any associated qualifier attributes.

The view exists primarily to serve the OTL (Oracle Time and Labor) layout engine and form/region rendering framework. Because it resolves the foreign keys between component instances, component definitions, region items, and qualifiers in a single query, it is heavily used by both application code and by report and integration developers who need to introspect layout configuration without joining five base tables manually. The presence of the /*+ INDEX (LAYQUAL HXC_LAYOUT_COMP_QUALIFIERS_FK1) */ hint confirms that the view was tuned for the qualifier lookup, which is the most selective and most frequently repeated predicate in practice.

Underlying Base Objects

The view is defined over five APPS synonyms, each mapping to a base table:

• HXC_LAYOUT_COMPONENTS – the driving table (alias COMP); stores each configured layout component instance.
• HXC_LAYOUT_COMP_DEFINITIONS – joined on LAYOUT_COMP_DEFINITION_ID; supplies component type, class, and render type.
• HXC_LAYOUT_COMP_QUALIFIERS – outer-joined on LAYOUT_COMPONENT_ID; supplies qualifier name and up to thirty generic qualifier attributes.
• AK_REGION_ITEMS – outer-joined on REGION_CODE; supplies the CSS label class.
• AK_REGION_ITEMS_TL – outer-joined for the translated label and description of the region item.

The outer joins mean a layout component is still returned even when no qualifier, region item, or translated label exists, so the view is safe to use as a complete component inventory.

Key Columns

• LAYOUT_COMPONENT_ID / LAYOUT_ID / PARENT_COMPONENT_ID – identify the component, the layout it belongs to, and its parent for hierarchical rendering.
• COMPONENT_NAME / COMPONENT_VALUE – the component identifier and its assigned literal value; COMPONENT_VALUE is the column most commonly searched by implementers investigating how a field is populated.
• COMPONENT_TYPE / COMPONENT_CLASS / RENDER_TYPE – derived from the definition table; determine how the element behaves and renders.
• LABEL / DESCRIPTION / CSS_CLASS – presentation metadata sourced from the AK region items.
• COMPONENT_ALIAS / PARENT_BEAN / NAME_VALUE_STRING / SEQUENCE – binding and ordering metadata used by the layout engine.
• QUALIFIER_NAME and QUALIFIER_ATTRIBUTE1–30 – flexible qualifier context that conditions when the component applies.
• ATTRIBUTE1–5 – descriptive flexfield attributes on the component itself.

Common Use Cases and Queries

Typical scenarios include auditing which value a specific layout field carries, tracing a layout's component hierarchy, and exporting layout configuration for migration or documentation. A search on component_value is usually an attempt to locate where a literal or token is stored.

• Find components carrying a specific value:

  SELECT layout_id, component_name, component_value, component_type
FROM apps.hxc_layout_components_v
WHERE component_value = :p_value;

• List all components for one layout, in render order:

  SELECT component_name, component_value, render_type, sequence
FROM apps.hxc_layout_components_v
WHERE layout_id = :p_layout_id
ORDER BY sequence;

• Inspect qualifier context for a component:

  SELECT component_name, qualifier_name, qualifier_attribute1
FROM apps.hxc_layout_components_v
WHERE layout_component_id = :p_id;

Because the view joins five objects, queries should always filter on LAYOUT_ID or LAYOUT_COMPONENT_ID to avoid full scans of the component population.