Results for “hxc_layout_comp_messages_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The HXC_LAYOUT_COMP_MESSAGES_V view is a reporting and integration object within the Oracle E-Business Suite Time and Labor Engine (HXC) product. It belongs to the APPS schema and is documented with a VALID status in ETRM for both the 12.1.1 and 12.2.2 releases. The view serves as a resolution layer that links layout component prompt definitions used in Time and Labor timecard layouts to the actual translated message text stored in the Oracle Application Object Library message repository (FND_NEW_MESSAGES).

In the Time and Labor configuration model, layout components define the fields and prompts that appear on a timecard or time entry page. Some of these prompts are not static labels; instead they are driven by Oracle message names so that the displayed text can be translated and maintained centrally. This view exposes the resolved prompt text for those message-based prompts, giving report writers, integrators, and technical consultants a convenient way to retrieve the effective, language-specific message text associated with a given layout component.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through synonyms in APPS:

• HXC_LAYOUT_COMP_PROMPTS — the driving table (aliased BASE) that stores layout component prompt records, including the prompt alias, the prompt type, and the attribute code and application that identify the associated message.
• FND_NEW_MESSAGES — the Applications message repository (aliased MSG) that stores message names, application identifiers, language codes, and the corresponding message text.

The join is established on three predicates: ATTRIBUTE_CODE equals MESSAGE_NAME, ATTRIBUTE_APPLICATION_ID equals APPLICATION_ID, and the prompt is restricted to PROMPT_TYPE = 'FND_MESSAGE'. In addition, the language is filtered by MSG.LANGUAGE_CODE equal to USERENV('LANG'), so the view returns only the message text in the session's current language. The relationship is therefore one of definition to content: the prompts table supplies the context and the messages table supplies the resolved text.

Key Columns

• LAYOUT_COMP_PROMPT_ID — the unique identifier of the layout component prompt record from the base prompts table.
• LAYOUT_COMPONENT_ID — identifies the layout component to which the prompt belongs, enabling linkage back to the owning timecard layout structure.
• PROMPT_ALIAS — the alias assigned to the prompt in the layout definition, used to reference the prompt position or purpose.
• MESSAGE_NAME — the Oracle message name resolved from the prompt's attribute code, matching FND_NEW_MESSAGES.MESSAGE_NAME.
• MESSAGE_TEXT — the translated message text retrieved from FND_NEW_MESSAGES for the current session language.

Common Use Cases and Queries

Typical uses include auditing which message-based prompts appear on a layout, producing translation or label reports, and resolving prompt aliases to their displayed text for downstream extracts or integrations. A representative query returning resolved prompt text for a specific layout component is shown below.

• Resolve prompts for a layout component: SELECT layout_comp_prompt_id, layout_component_id, prompt_alias, message_name, message_text FROM hxc_layout_comp_messages_v WHERE layout_component_id = :p_component_id;
• Search by message name: SELECT layout_component_id, prompt_alias, message_text FROM hxc_layout_comp_messages_v WHERE message_name = 'HXC_SOME_PROMPT';
• List all message-based prompts: SELECT layout_component_id, prompt_alias, message_name, message_text FROM hxc_layout_comp_messages_v ORDER BY layout_component_id, prompt_alias;

Because the view filters on USERENV('LANG'), results reflect the language of the querying session; reports requiring multiple languages must account for this filter.