Search Results css_class




Overview
Explore in AI Chat

Overview

HXC_LAYOUT_COMP_PROMPTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HXC – Time and Labor Engine product. It exposes the prompt definitions configured against layout components used by Time and Labor and related self-service time entry pages. In Oracle EBS 12.1.1 and 12.2.2, layout components drive how time card fields, prompts, and attribute labels are rendered to end users; this view consolidates the internal component-to-prompt mapping with the descriptive, translated metadata maintained in the Oracle Application Framework (OA Framework / AK) repository.

The view is defined as a join between the base prompt table and AK_REGION_ITEMS_VL. It therefore performs two functions simultaneously: it supplies the technical identifiers required to resolve a prompt back to its owning layout component, and it supplies the user-facing label, description, and Cascading Style Sheet class associated with the underlying region item. This makes the view a convenient single source for administrators, developers, and reporting queries that need to reconcile HXC configuration with the AK presentation layer, without writing the join manually each time.

Underlying Base Objects

The documented base objects referenced by the view are:

  • HXC_LAYOUT_COMP_PROMPTS (documented as a SYNONYM in the ETRM metadata), which stores the layout component prompt records, including the prompt alias, region and attribute identifiers, prompt type, and the LAYOUT_COMP_PROMPT_ID primary key.
  • AK_REGION_ITEMS_VL (VIEW), the OA Framework region item view that carries the translatable attribute label, description, and CSS label class name for region items.

The view text joins these two sources on four matching keys — REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID — and additionally restricts the result set with the predicate BASE.PROMPT_TYPE = 'AK_PROMPT'. This filter ensures that only prompts derived from AK region items are returned; other prompt types stored in the base table are excluded. The join is effectively an equi-join on region and attribute identity across the HXC and AK schemas, so referential integrity between the two objects is a prerequisite for rows to appear.

Key Columns

  • LAYOUT_COMP_PROMPT_ID — Primary key of the underlying prompt record; uniquely identifies a prompt within the component configuration.
  • LAYOUT_COMPONENT_ID — Foreign key to the layout component to which the prompt belongs, enabling grouping of prompts by component.
  • PROMPT_ALIAS — The internal alias used to reference the prompt within the layout definition.
  • LABEL — The prompt text displayed to the user, sourced from AK.ATTRIBUTE_LABEL_LONG. Because it originates from AK_REGION_ITEMS_VL, it reflects the translated label for the session language.
  • DESCRIPTION — The description of the region item from the AK repository, providing additional context about the attribute.
  • CSS_CLASS — The CSS label class name (AK.CSS_LABEL_CLASS_NAME) applied to the prompt, controlling its visual presentation.

Common Use Cases and Queries

Typical uses include auditing which prompts are attached to a given layout component, exporting prompt labels and CSS classes for documentation or regression comparison, and troubleshooting missing or mislabelled fields on time entry pages. The following query lists all AK-derived prompts for a specific component:

SELECT layout_comp_prompt_id,
       layout_component_id,
       prompt_alias,
       label,
       description,
       css_class
FROM   apps.hxc_layout_comp_prompts_v
WHERE  layout_component_id = :p_component_id
ORDER  BY prompt_alias;

A second common pattern searches for prompts by their displayed label, useful when only the on-screen text is known:

SELECT layout_component_id, prompt_alias, label
FROM   apps.hxc_layout_comp_prompts_v
WHERE  UPPER(label) LIKE UPPER('%' || :p_search_text || '%');

Because the view depends on AK_REGION_ITEMS_VL, queries benefit from the same language and translation handling as OA Framework pages, making it suitable for both diagnostic and lightweight integration reporting in 12.1.1 and 12.2.2.