Results for “param_list_code”

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

Overview

BNE_COMPONENTS_VL is a standard Oracle Application Object Library (AOL) translation (MLS) view owned by the APPS schema in Oracle E-Business Suite. It is part of the BNE product family — Web Applications Desktop Integrator (WebADI) — and presents a language-specific, user-facing projection of the BNE_COMPONENTS application component registry. The underlying entity, BNE_COMPONENTS, stores metadata describing the Java-based components that WebADI uses when rendering, mapping, and uploading integrator content. Because this is a "_VL" view, it joins the non-translated base table with its translation table and filters rows to the session language, so each query returns one translatable value (USER_NAME) appropriate to the current user's environment.

For reporting and integration purposes, BNE_COMPONENTS_VL is the object that EBS developers and support analysts query to resolve how a given component is wired into the WebADI runtime — for example, which Java implementation class handles a component and which parameter list supplies its runtime parameters. The component_java_class column is frequently the focus of troubleshooting, since it identifies the concrete implementation invoked by WebADI.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over two referenced synonyms in APPS:

• BNE_COMPONENTS_B — the base ("_B") table holding non-translatable attributes such as APPLICATION_ID, COMPONENT_CODE, OBJECT_VERSION_NUMBER, COMPONENT_JAVA_CLASS, PARAM_LIST_APP_ID, PARAM_LIST_CODE, and standard WHO audit columns.
• BNE_COMPONENTS_TL — the translation ("_TL") table holding the language-specific USER_NAME, keyed by LANGUAGE plus the primary key columns.

The view joins the two on APPLICATION_ID and COMPONENT_CODE and restricts the result with T.LANGUAGE = USERENV('LANG'), returning the translation matching the session language. The view text exposes ROW_ID via ROWID from the base table, producing a stable row identifier for the joined record.

Key Columns

• ROW_ID — the base-table ROWID of the component record.
• APPLICATION_ID — the application owner (FND_APPLICATION) associated with the component.
• COMPONENT_CODE — the unique code identifying the component; part of the composite key.
• COMPONENT_JAVA_CLASS — the Java class implementing the component; central to diagnosing WebADI runtime behavior.
• OBJECT_VERSION_NUMBER — optimistic locking / OAF concurrency control value.
• PARAM_LIST_APP_ID and PARAM_LIST_CODE — identify the parameter list supplying the component's parameters.
• USER_NAME — the user-facing, translated display name from BNE_COMPONENTS_TL.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

The view is typically queried to audit component-to-class mappings, verify parameter-list wiring, or resolve component names in the user's language during WebADI troubleshooting.

List all components and their Java classes for an application:

• SELECT component_code, component_java_class, user_name FROM bne_components_vl WHERE application_id = :app_id ORDER BY component_code;

Locate the component(s) backed by a specific implementation class:

• SELECT component_code, user_name, application_id FROM bne_components_vl WHERE component_java_class LIKE '%MyIntegrator%' ORDER BY component_code;

Inspect parameter-list associations for auditing:

• SELECT component_code, param_list_app_id, param_list_code FROM bne_components_vl WHERE param_list_code IS NOT NULL;

Because the view filters on USERENV('LANG'), results reflect the connecting user's language; queries run in a different session language may return alternate USER_NAME values while the base attributes remain identical.