Search Results bne_menus_b_uk1

Overview

BNE.BNE_MENUS_B is a core configuration table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the BNE (Oracle Web Applications Desktop Integrator / Application Integration Framework) schema. It stores the definition of a viewer menu, which is the navigation construct used by the EBS application framework to render menu hierarchies for integrated applications and self-service functions. Each row represents one menu entry, identified by the combination of an application and a menu code, and may reference a parent menu to form the hierarchy presented to end users.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, placing it among transactional configuration objects that are read frequently but modified infrequently. From a heuristic Data Vault modeling perspective, this object leans toward a satellite classification, given its descriptive columns and dependency on parent and integrator references rather than serving as a pure hub or link. The physical schema documents 18 columns, and the object is flagged VALID in the ETRM registry for release 12.2.2.

Key Information Stored

The primary key is BNE_MENUS_B_PK, composed of APPLICATION_ID and MENU_CODE. Two unique business-key candidates are documented: BNE_MENUS_B_UK1, which spans APPLICATION_ID and MENU_CODE, and the extended unique index variant that adds ZD_EDITION_NAME for edition-based redefinition support in 12.2.2. The most significant columns include:

• APPLICATION_ID — numeric foreign key to FND_APPLICATIONS.APPLICATION_ID, identifying the owning application.
• MENU_CODE — VARCHAR2(30) unique code identifying the menu for that application.
• PARENT_APP_ID and PARENT_CODE — self-referencing columns that define the parent menu, enabling recursive hierarchy construction.
• SEQUENCE_NUM — controls ordering of menu entries within a parent.
• INTEGRATOR_APP_ID and INTEGRATOR_CODE — foreign key to BNE_INTEGRATORS_B, binding the menu to an integrator definition.
• RESOLVER_CLASS — VARCHAR2(240) naming the Java class that resolves the menu at runtime.
• ACCESS_POINT — VARCHAR2(240) defining the starting access point for the menu.
• PARAM_LIST_APP_ID and PARAM_LIST_CODE — foreign key to BNE_PARAM_LISTS_B, supplying runtime parameters.
• OBJECT_VERSION_NUMBER — optimistic locking support for concurrent edits.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE) and ZD_EDITION_NAME for editioning.

Common Use Cases and Queries

Typical use cases include reporting on configured menu hierarchies, validating parent-child relationships, and auditing which integrators expose which menus. A common pattern reconstructs the tree using the self-join on PARENT_APP_ID and PARENT_CODE:

SELECT m.APPLICATION_ID, m.MENU_CODE, m.PARENT_APP_ID, m.PARENT_CODE, m.SEQUENCE_NUM FROM BNE.BNE_MENUS_B m WHERE m.APPLICATION_ID = :app_id ORDER BY m.PARENT_CODE, m.SEQUENCE_NUM;

Another frequent query joins to BNE_INTEGRATORS_B to list integrator-bound menus, or to BNE_PARAM_LISTS_B to inspect parameterization. Because menus are resolved dynamically via RESOLVER_CLASS and ACCESS_POINT, administrators query this table to troubleshoot missing or misordered menu entries in self-service and OAF pages.

Related Objects

The table participates in several FK relationships that anchor it to the wider BNE framework:

• BNE_MENUS_B (self-reference) via PARENT_APP_ID and PARENT_CODE for hierarchical nesting.
• BNE.BNE_PARAM_LISTS_B via PARAM_LIST_APP_ID for runtime parameter lists.
• BNE.BNE_INTEGRATORS_B via INTEGRATOR_APP_ID for integrator definitions.
• FND_APPLICATIONS via APPLICATION_ID for application metadata.
• FND_USER via CREATED_BY and LAST_UPDATED_BY for WHO audit columns.
• FND_LOGINS via LAST_UPDATE_LOGIN.

These relationships make BNE_MENUS_B a dependent satellite within the BNE integration model, referenced primarily by the runtime menu resolver and by integrator configuration screens.