Search Results bne_menus_vl

Overview

BNE_MENUS_VL is a translation-enabled (VL, "view with language") view owned by the APPS schema in Oracle E-Business Suite. It is part of the BNE product family — Web Applications Desktop Integrator (Web ADI) — which provides the framework for integrating desktop tools such as Microsoft Excel and Word with EBS forms, concurrent programs, and web pages. The view exposes the definition of BNE menus, the hierarchical structures that group Web ADI integrators into named, navigable access points.

In Oracle EBS 12.1.1 and 12.2.2, Web ADI menus are the mechanism by which administrators control which integrators appear for a given responsibility or user. Rather than reading the underlying tables directly, developers and support analysts query BNE_MENUS_VL to obtain the menu metadata already joined with its language-specific translated display name. Because it resolves USERENV('LANG') at runtime, the view returns the menu description in the session's current language, making it suitable for both reporting and application-layer consumption without additional language joins.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• BNE_MENUS_B — the base ("B") table holding language-independent menu attributes, including the application identifier, menu code, parent relationship, sequence, integrator binding, resolver class, and audit columns.
• BNE_MENUS_TL — the translation ("TL") table holding the language-specific menu user name.

The join is performed on APPLICATION_ID and MENU_CODE, with the additional predicate T.LANGUAGE = USERENV('LANG') restricting the result to a single translation row per menu. A M.ROWID is projected as ROW_ID to provide a unique row identifier for the view result. Because it is a VL view, it is read-only with respect to the translated column and does not itself support DML on the translation; maintenance is performed against the B and TL tables (typically through the Web ADI administrative UI or the corresponding APIs).

Key Columns

• ROW_ID — the ROWID of the BNE_MENUS_B row, usable as a unique key for the menu base record.
• APPLICATION_ID / MENU_CODE — the composite primary key identifying the menu within its owning application.
• USER_NAME — the translated display name of the menu, sourced from BNE_MENUS_TL for the session language.
• PARENT_APP_ID / PARENT_CODE — reference to the parent menu, enabling reconstruction of the menu hierarchy.
• SEQUENCE_NUM — the ordering of the menu within its parent.
• INTEGRATOR_APP_ID / INTEGRATOR_CODE — the integrator associated with the menu entry, where applicable.
• RESOLVER_CLASS — the Java class responsible for resolving the access point at runtime.
• ACCESS_POINT — the target function, page, or destination invoked when the menu entry is selected.
• PARAM_LIST_APP_ID / PARAM_LIST_CODE — the parameter list passed to the resolved access point.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Web ADI framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include auditing which Web ADI menus exist for an application, reviewing the hierarchy of menus and their integrators, and troubleshooting why a given integrator is not visible to users. A basic listing of menus in the current language:

SELECT application_id, menu_code, user_name, parent_code, sequence_num
FROM   apps.bne_menus_vl
ORDER  BY application_id, parent_code, sequence_num;

To inspect the integrator binding and access point for a specific menu:

SELECT menu_code, integrator_code, resolver_class, access_point
FROM   apps.bne_menus_vl
WHERE  application_id = :app_id
AND    menu_code      = :menu_code;

To reconstruct the hierarchy from parent to child entries:

SELECT child.user_name AS child_menu, parent.user_name AS parent_menu
FROM   apps.bne_menus_vl child,
       apps.bne_menus_vl parent
WHERE  child.parent_app_id = parent.application_id (+)
AND    child.parent_code   = parent.menu_code (+);

Because the view resolves the session language automatically, reports executed under different language settings yield the appropriately translated USER_NAME without modification. It should be noted that the view is a reporting convenience; DML against menu definitions must be performed on BNE_MENUS_B and BNE_MENUS_TL or through supported Web ADI administration functionality.