Search Results bne_menus_b




Overview
Explore in AI Chat

Overview

BNE_MENUS_B is the foundational definition table for menus within the BNE (Web Applications Desktop Integrator) product in Oracle EBS 12.1.1 and 12.2.2. It stores the header-level definition of each menu, including parent-child hierarchy relationships, associated integrators, parameter lists, and resolver logic. Menus in BNE drive the navigation and task-launching framework used by Desktop Integrator, Web ADI, and related spreadsheet-based integration features.

The table resides in the BNE schema and is documented as VALID in the ETRM repository. Its primary key is BNE_MENUS_B_PK, defined on the composite of APPLICATION_ID and MENU_CODE. A unique index, BNE_MENUS_B_UK1 (APPLICATION_ID, MENU_CODE, ZD_EDITION_NAME), serves as the business-key candidate and supports the editioning model introduced in 12.2.2. Based on the foreign key topology — where the table references BNE_PARAM_LISTS_B, BNE_INTEGRATORS_B, and recursively references itself — the heuristic Data Vault classification is satellite-leaning. This suggests the object is best modeled as a satellite attached to parent hubs for application, integrator, and menu code, capturing descriptive and hierarchical attributes rather than acting as an independent hub or link.

Key Information Stored

The table contains 18 documented columns. The most significant include:

  • APPLICATION_ID — Part of the composite primary key; identifies the owning application context for the menu.
  • MENU_CODE — The second component of the primary key; the human-readable identifier for the menu.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.
  • PARENT_APP_ID / PARENT_CODE — Recursive foreign keys establishing menu hierarchy; a menu may have a parent menu within the same structure.
  • SEQUENCE_NUM — Controls the ordering of menu entries within a parent.
  • INTEGRATOR_APP_ID / INTEGRATOR_CODE — Foreign key to BNE_INTEGRATORS_B, linking the menu to its associated integrator.
  • RESOLVER_CLASS — Identifies the Java class responsible for resolving menu behavior at runtime.
  • ACCESS_POINT — Defines the access point or endpoint for the menu action.
  • PARAM_LIST_APP_ID / PARAM_LIST_CODE — Foreign key to BNE_PARAM_LISTS_B, associating parameter lists with the menu.
  • ZD_EDITION_NAME — Editioning column supporting Online Patching in 12.2.2.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE provide standard WHO tracking.

The surrogate primary key is the composite APPLICATION_ID and MENU_CODE, while the business-key candidate is the unique index that adds ZD_EDITION_NAME.

Common Use Cases and Queries

Typical usage includes resolving the full menu hierarchy for a given integrator, identifying orphaned menus, and reporting on menu configuration. A common query joins the table to itself to walk the parent-child relationship:

  • SELECT m.MENU_CODE, m.SEQUENCE_NUM, p.MENU_CODE AS PARENT_MENU FROM BNE_MENUS_B m LEFT JOIN BNE_MENUS_B p ON m.PARENT_APP_ID = p.APPLICATION_ID AND m.PARENT_CODE = p.MENU_CODE WHERE m.APPLICATION_ID = :app_id;
  • SELECT m.MENU_CODE, i.INTEGRATOR_CODE FROM BNE_MENUS_B m JOIN BNE_INTEGRATORS_B i ON m.INTEGRATOR_APP_ID = i.APPLICATION_ID AND m.INTEGRATOR_CODE = i.INTEGRATOR_CODE;
  • SELECT m.MENU_CODE, pl.PARAM_LIST_CODE FROM BNE_MENUS_B m JOIN BNE_PARAM_LISTS_B pl ON m.PARAM_LIST_APP_ID = pl.APPLICATION_ID AND m.PARAM_LIST_CODE = pl.PARAM_LIST_CODE;

These patterns support troubleshooting missing menu entries, auditing integrator assignments, and validating parameter list references before deployment.

Related Objects

Significant related objects include:

  • BNE_MENUS_TL — The translation table storing language-specific menu names and descriptions.
  • BNE_PARAM_LISTS_B — Referenced via PARAM_LIST_APP_ID and PARAM_LIST_CODE for parameter list definitions.
  • BNE_INTEGRATORS_B — Referenced via INTEGRATOR_APP_ID and INTEGRATOR_CODE for integrator linkage.
  • BNE_MENUS_B (self-reference) — Via PARENT_APP_ID and PARENT_CODE for hierarchy traversal.
  • BNE_MENUS_B_PK — The primary key constraint enforcing uniqueness on APPLICATION_ID and MENU_CODE.
  • BNE_MENUS_B_UK1 — The unique index supporting business-key and editioning validation.

Together these objects form the menu definition subsystem within BNE, enabling hierarchical navigation for Desktop Integrator functionality.