Search Results bne_param_defns_b




Overview
Explore in AI Chat

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

Overview

BNE_PARAM_DEFNS_B is a core configuration table in the BNE (Web Applications Desktop Integrator) product of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. It stores the definition of parameter UI metadata, meaning it holds the declarative specification of how individual parameters are rendered, validated, defaulted and resolved within BNE-based functionality such as Web ADI integrators, desktop integration layouts and parameter-driven concurrent or web processes. The table is owned by the BNE schema and is composed of 35 documented columns in the 12.2.2 physical schema.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is satellite-leaning. This suggests the table is best understood as descriptive attribute context attached to one or more parent business keys, rather than as an independent hub or an associative link. The presence of OBJECT_VERSION_NUMBER and audit columns reinforces its role as a versioned, maintainable definition store rather than a transactional fact table.

Key Information Stored

The surrogate primary key is BNE_PARAM_DEFNS_B_PK, defined on (APPLICATION_ID, PARAM_DEFN_CODE). A separate unique index, BNE_PARAM_DEFNS_B_UK1, is defined on (APPLICATION_ID, PARAM_DEFN_CODE, ZD_EDITION_NAME), making it the documented business-key candidate; the ZD_EDITION_NAME column participates in edition-based redefinition semantics in 12.2.x. The most significant columns are:

Common Use Cases and Queries

Typical use cases include auditing parameter definitions, tracing UI behavior, diagnosing default-value issues, and documenting integrator configuration. A common query joins parameters to their attribute definitions:

  • Retrieving parameter metadata: SELECT application_id, param_defn_code, param_name, datatype, display_type FROM bne.bne_param_defns_b WHERE application_id = :app_id;
  • Locating editable, visible parameters: SELECT param_defn_code FROM bne.bne_param_defns_b WHERE default_visible_flag = 'Y' AND default_user_modifyable_flag = 'Y';
  • Joining to attributes: SELECT p.param_defn_code, p.param_name, a.attribute_code FROM bne.bne_param_defns_b p, bne.bne_attributes a WHERE p.attribute_app_id = a.application_id AND p.attribute_code = a.attribute_code;
  • Identifying overrides applied to a definition via BNE_PARAM_OVERRIDES using the shared (APPLICATION_ID, PARAM_DEFN_CODE) keys.
  • Edition-scoped reporting restricted by ZD_EDITION_NAME in 12.2.2 environments.

Related Objects

The documented relationships anchor this table within the BNE metadata family:

  • BNE_ATTRIBUTES — referenced by BNE_PARAM_DEFNS_B via (ATTRIBUTE_APP_ID, ATTRIBUTE_CODE).
  • BNE_PARAM_OVERRIDES — references BNE_PARAM_DEFNS_B via (APPLICATION_ID, PARAM_DEFN_CODE), supplying context-specific overrides.
  • BNE_PARAM_LIST_ITEMS — related through PARAM_DEFN_APP_ID and PARAM_DEFN_CODE, holding list-of-values entries for parameters.
  • BNE_PARAM_DEFNS_B_PK and BNE_PARAM_DEFNS_B_UK1 — the primary and unique indexes enforcing identity and edition uniqueness.

Collectively these objects form the metadata backbone that drives parameter rendering, validation and persistence across Web ADI integrators in Oracle EBS.