Results for “menu_id”

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

Overview

ICX_FORM_FUNCTIONS_VL is a view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, classified under the ICX product family (Oracle iProcurement). The view is documented in ETRM as VALID and carries the description "Retrofitted," indicating it was reconstructed by Oracle during an upgrade or patch cycle to preserve compatibility for dependent iProcurement components that reference form functions through a menu-oriented representation. Functionally, the view surfaces menu entries that are tied specifically to Oracle Forms-based functions of type WWW or WWK, joining menu structure metadata to the underlying function definitions. Because the view resolves menu-to-function relationships into a flattened, readable form, it is used internally by iProcurement and related self-service modules to render navigation entries, function lists, and menu labels. In reporting and integration contexts, it provides a convenient projection of FND menu entries without requiring consumers to reproduce the join logic against the Oracle Forms function tables directly.

Underlying Base Objects

Per the documented ETRM metadata, ICX_FORM_FUNCTIONS_VL is defined over two referenced base objects, both of which are themselves views:

• FND_MENU_ENTRIES_VL — supplies the menu definition rows, including MENU_ID, ENTRY_SEQUENCE, FUNCTION_ID, PROMPT, and DESCRIPTION.
• FND_FORM_FUNCTIONS_VL — supplies the form function attributes, notably FUNCTION_ID and TYPE, and is filtered so that only Form functions of type WWW or WWK qualify.

The relationship between the two is established through FUNCTION_ID, which acts as the join key in the view's defining SQL. The view effectively restricts the menu entry population to those entries whose associated function is a Forms-based function of the documented types, excluding non-Forms function types such as JSP, SSWA, or purely external URL functions. This filtering is significant because it distinguishes Forms-launched iProcurement navigation from other function classes present in the same menu hierarchy.

Key Columns

The view exposes three documented columns:

• MENU_ID — the identifier of the menu to which the entry belongs. This links the row to a specific menu definition in the FND menu hierarchy and is the primary grouping attribute for consumers enumerating entries within a menu.
• ENTRY_SEQUENCE — the ordinal position of the menu entry within its parent menu. It governs the order in which entries are displayed, allowing consumers to reproduce the presentation order of a menu deterministically.
• TEXT — a concatenated display label formed by combining PROMPT and DESCRIPTION from the menu entry, separated by a space. This column provides the human-readable text associated with the function as presented within the menu structure.

Notably, the view does not expose FUNCTION_ID, FUNCTION_NAME, or the function TYPE directly; those attributes remain available only in the underlying base views for consumers that need them.

Common Use Cases and Queries

Typical scenarios include enumerating the Forms-based functions within a given menu for diagnostic or auditing purposes, validating that expected iProcurement menu entries are present after patching, and driving custom navigation reports that mirror the standard menu presentation.

To list all entries for a specific menu, ordered as displayed:

SELECT menu_id, entry_sequence, text
FROM   apps.icx_form_functions_vl
WHERE  menu_id = :p_menu_id
ORDER  BY entry_sequence;

To search for entries whose displayed label matches a keyword:

SELECT menu_id, entry_sequence, text
FROM   apps.icx_form_functions_vl
WHERE  UPPER(text) LIKE '%'||UPPER(:p_keyword)||'%'
ORDER  BY menu_id, entry_sequence;

To compare the view's population against the full menu entry set (to identify entries excluded by the WWW/WWK filter), a query can outer-join the view to FND_MENU_ENTRIES_VL and flag rows where the ICX view returns no match. This is useful when reconciling menu entries after an upgrade, since the "Retrofitted" status suggests the view must remain aligned with the current FND menu and function definitions in both 12.1.1 and 12.2.2 environments.