Results for “default_string”

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

Overview

BNE_PARAM_OVERRIDES is a table in the BNE schema (BNE – Web Applications Desktop Integrator) that stores the definition of over-ridden parameter definition values. In Oracle E-Business Suite 12.1.1 and 12.2.2, it allows administrators and users to customize the default behavior of parameters defined at a lower or higher level, thereby overriding the base parameter definition maintained in BNE_PARAM_DEFNS_B. This is essential for tailoring Web ADI integrator behavior, form defaults, and list-of-values behavior without altering the underlying parameter definition.

From a Data Vault modeling perspective, this object leans toward a satellite classification. It does not appear to function as a central hub or a pure link; rather, it captures descriptive, context-specific override values that are dependent on the parent parameter definition, making it a natural satellite candidate.

Key Information Stored

The table contains twenty documented columns. The most important columns are the following:

• APPLICATION_ID – Identifies the Oracle EBS application that owns the parameter definition.
• PARAM_DEFN_CODE – The code of the parameter definition being overridden.
• LVL – Indicates the level at which the override applies, allowing hierarchical or context-sensitive overrides.
• OVERRIDE_ID – Surrogate identifier for a specific override record.
• REQUIRED_FLAG – Indicates whether the parameter is required after the override.
• VISIBLE_FLAG – Controls whether the parameter is visible to the user.
• USER_MODIFYABLE_FLAG – Determines whether the end user may change the parameter value.
• DEFAULT_STRING, DEFAULT_DATE, DEFAULT_NUMBER, DEFAULT_BOOLEAN_FLAG, DEFAULT_FORMULA – Provide the overridden default value in the appropriate data type or as a formula.
• DESC_VALUE – A descriptive value or label associated with the override.
• OBJECT_VERSION_NUMBER – Supports optimistic locking during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY – Standard audit columns recording who created and last modified the row and when.

The primary key is defined by the constraint BNE_PARAM_OVERRIDES_PK on the columns APPLICATION_ID, PARAM_DEFN_CODE, LVL, and OVERRIDE_ID. A unique index, BNE_PARAM_OVERRIDES_UK1, includes the same four columns plus ZD_EDITION_NAME, which is the business-key candidate that also accounts for edition-based redefinition (EBR) in 12.2.2.

Common Use Cases and Queries

Typical use cases include diagnosing why a parameter default differs from the base definition, auditing which overrides are active at a given level, and reporting on parameters that are hidden, required, or non-modifiable.

A common query pattern joins the override table to the base definition table to compare values:

• SELECT o.APPLICATION_ID, o.PARAM_DEFN_CODE, o.LVL, o.OVERRIDE_ID, o.DEFAULT_STRING FROM BNE.BNE_PARAM_OVERRIDES o WHERE o.APPLICATION_ID = :app_id AND o.PARAM_DEFN_CODE = :code;
• SELECT o.PARAM_DEFN_CODE, o.LVL, o.REQUIRED_FLAG, o.VISIBLE_FLAG, o.USER_MODIFYABLE_FLAG FROM BNE.BNE_PARAM_OVERRIDES o WHERE o.VISIBLE_FLAG = 'N';

Reporting use cases include identifying parameters that have been made invisible to users, parameters whose defaults were changed for specific levels, and parameters where the user-modifiable flag has been disabled for compliance or control reasons. Administrators also query this table when troubleshooting Web ADI integrator behavior after a patch or upgrade, since overrides may take precedence over defaults in BNE_PARAM_DEFNS_B.

Related Objects

The most significant object related to BNE_PARAM_OVERRIDES is BNE_PARAM_DEFNS_B, which stores the base parameter definitions. The foreign key relationship maps BNE_PARAM_OVERRIDES.APPLICATION_ID to BNE_PARAM_DEFNS_B.APPLICATION_ID, and the parameter definition code further ties the override to its parent definition. Other relevant objects include the BNE_PARAM_DEFNS_TL table for translated parameter descriptions, BNE_PARAM_DEFNS_VL views that expose the definitions with translations, and API packages such as BNE_PARAM_DEFNS_PKG or related Web ADI setup APIs that may read overrides when resolving parameter behavior. Reporting views or discoverer workbooks that expose Web ADI parameter configuration also depend on this table. When performing impact analysis, DBAs should consider that deleting or updating an override row can change parameter defaults, visibility, and required status for the affected application, code, and level.