Search Results bne_param_lists_b_n1

Overview

BNE.BNE_PARAM_LISTS_B is the definition table for parameter lists within the Oracle E-Business Suite "BNE" (Business Intelligence/Personalization) schema. A parameter list is an ordered collection of parameters used to store the required values needed to run some code. Content components, for example, require a parameter list (referenced via BNE_CONTENTS.PARAM_LIST_APP_ID and BNE_CONTENTS.PARAM_LIST_CODE) to define the parameters they need at runtime. Parameter lists are also consumed by components (BNE_COMPONENTS_B), viewers (BNE_VIEWERS_B), and the upload and import processes. Each parameter list may additionally reference attributes stored in BNE_ATTRIBUTES_B for generic data storage.

The table is classified heuristically as hub-leaning under a Data Vault modeling interpretation. This is a suggestion only: BNE_PARAM_LISTS_B behaves as a central reference entity identified by a stable two-part business key, with dependent detail and referencing tables radiating from it. Its physical storage resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its indexes reside in APPS_TS_TX_IDX. The object carries a status of VALID in the ETRM 12.2.2 documented schema, which reports 14 columns.

Key Information Stored

The primary key is BNE_PARAM_LISTS_B_PK, defined on (APPLICATION_ID, PARAM_LIST_CODE). This composite key functions as the surrogate identifier for the entity and is also the natural business key: APPLICATION_ID is the application identifier (foreign key to FND_APPLICATIONS.APPLICATION_ID), and PARAM_LIST_CODE is a unique code identifying the entity within that application. Because the primary key columns are themselves the business identifiers, no separate surrogate column exists.

The documented unique index BNE_PARAM_LISTS_B_UK1 covers (APPLICATION_ID, PARAM_LIST_CODE, ZD_EDITION_NAME). The inclusion of ZD_EDITION_NAME indicates the table participates in Oracle's edition-based redefinition (EBR) model, allowing multiple edition-specific versions of the same logical parameter list to coexist. A non-unique index, BNE_PARAM_LISTS_B_N1, covers (ATTRIBUTE_APP_ID, ATTRIBUTE_CODE) to support attribute lookups.

The most significant columns include:

• APPLICATION_ID and PARAM_LIST_CODE — the composite primary and business key.
• OBJECT_VERSION_NUMBER — optimistic locking / row versioning column.
• PERSISTENT_FLAG — indicates whether the parameter list is persistent (Y/N). Persistent lists should not be deleted; non-persistent lists may be deleted after being passed from client to server to ensure cleanup.
• COMMENTS — developer-defined descriptive comments about the parameter list.
• ATTRIBUTE_APP_ID and ATTRIBUTE_CODE — reference to an attribute definition used for generic data storage.
• LIST_RESOLVER — fully qualified Java class name used to perform parameter list pre-processing and validation.
• ZD_EDITION_NAME — edition identifier supporting EBR.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard "WHO" audit columns.

Common Use Cases and Queries

Typical reporting and diagnostics center on resolving which components, viewers, or import programs depend on a given parameter list, and on auditing persistent versus non-persistent lists.

Listing all parameter lists for an application:

• SELECT param_list_code, persistent_flag, list_resolver, comments FROM bne.bne_param_lists_b WHERE application_id = :app_id ORDER BY param_list_code;

Joining to the attribute definition referenced by a list:

• SELECT p.param_list_code, a.attribute_code FROM bne.bne_param_lists_b p, bne.bne_attributes_b a WHERE p.attribute_app_id = a.application_id AND p.attribute_code = a.attribute_code;

Finding viewers bound to a parameter list (via BNE_VIEWERS_B.PARAM_LIST_APP_ID or CREATE_DOC_LIST_APP_ID), or import programs bound through BNE_IMPORT_PROGRAMS.IMPORT_PARAM_LIST_APP_ID, is a common impact-analysis pattern before modifying a list. Because of EBR, queries should typically filter on the current edition name or use the editioning views.

Related Objects

BNE_PARAM_LISTS_B sits at the center of several relationships:

• BNE_ATTRIBUTES_B — referenced by BNE_PARAM_LISTS_B.ATTRIBUTE_CODE (with ATTRIBUTE_APP_ID) for generic attribute storage.
• BNE_IMPORT_PROGRAMS — references this table via IMPORT_PARAM_LIST_APP_ID.
• BNE_PARAM_GROUPS_B — references this table via APPLICATION_ID.
• BNE_VIEWERS_B — references this table through both PARAM_LIST_APP_ID and CREATE_DOC_LIST_APP_ID.
• BNE_COMPONENTS_B — consumes parameter lists for component execution.
• BNE_CONTENTS — content components reference parameter lists via PARAM_LIST_APP_ID and PARAM_LIST_CODE.

The combined FK topology confirms BNE_PARAM_LISTS_B as a hub-leaning reference entity whose business key (APPLICATION_ID, PARAM_LIST_CODE) is reused across viewers, import programs, and parameter groups.