Search Results bne_components_b




Overview
Explore in AI Chat

Overview

BNE_COMPONENTS_B is a foundational configuration table in the BNE (Web Applications Desktop Integrator) product, also marketed as Oracle Web Applications Desktop Integrator / Enterprise Resource Planning Integrator. It resides in the BNE schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The table stores the "Definition of LOV and XML objects" — that is, the master definitions of reusable list-of-values (LOV) components and XML-based components that Desktop Integrator uses when constructing and rendering spreadsheet-based Web ADI layouts. Each row describes a single component, identified by the combination of COMPONENT_CODE and APPLICATION_ID, and points to the parameter list that drives the component's runtime behavior.

From a modeling perspective, the mined Data Vault classification for this object is satellite-leaning. This reflects the presence of descriptive and behavioral attributes (the Java class, parameter list references, and audit columns) attached to a component business key, rather than a transaction join table. The heuristic should be treated as a suggestion for enterprise data warehouse design, not as a property of the operational table itself.

Key Information Stored

The table contains twelve documented columns. The most significant are:

  • COMPONENT_CODE — the business identifier of the LOV or XML component. Combined with APPLICATION_ID it forms the primary key, BNE_COMPONENTS_B_PK.
  • APPLICATION_ID — the Oracle EBS application (product) that owns the component, enabling the same code to be reused across applications.
  • COMPONENT_JAVA_CLASS — the Java implementation class that renders or resolves the component at runtime.
  • PARAM_LIST_APP_ID and PARAM_LIST_CODE — a foreign reference to the parameter list that configures the component.
  • OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking column used to detect concurrent modifications.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard "WHO" audit columns that record row provenance and change history.
  • ZD_EDITION_NAME — the editioning column used by EBS 12.2 Online Patching (ADOP), present in the 12.2.2 schema.

The primary key is the composite surrogate/business key BNE_COMPONENTS_B_PK (COMPONENT_CODE, APPLICATION_ID). A unique index, BNE_COMPONENTS_B_UK1, spans APPLICATION_ID, COMPONENT_CODE, and ZD_EDITION_NAME, reinforcing the business key and supporting edition-aware uniqueness in 12.2.2. Note that there is no separate single-column surrogate; the business attributes themselves serve as the key.

Common Use Cases and Queries

Typical use cases involve inspecting which LOV or XML components are registered for a given application, tracing a component to its parameter list, or auditing component definitions across editions. A representative query joining to the foreign-key table is:

SELECT c.COMPONENT_CODE, c.APPLICATION_ID, c.COMPONENT_JAVA_CLASS,
       c.PARAM_LIST_APP_ID, c.PARAM_LIST_CODE
FROM   BNE.BNE_COMPONENTS_B c
WHERE  c.APPLICATION_ID = :app_id
AND    c.COMPONENT_CODE = :code;

Reporting scenarios include listing all components referenced by interface columns (via BNE_INTERFACE_COLS_B), or identifying components whose parameter lists have changed. Because ZD_EDITION_NAME participates in the unique index, queries intended for a specific runtime edition should filter on it when running under 12.2.2.

Related Objects

  • BNE_INTERFACE_COLS_B — references BNE_COMPONENTS_B through the column pair VAL_COMPONENT_APP_ID / VAL_COMPONENT_CODE, linking each interface column to its validation component.
  • BNE_COMPONENTS_TL — the translation table providing language-specific descriptions for component codes.
  • BNE_PARAM_LISTS — the parent of the parameter-list reference held in PARAM_LIST_APP_ID / PARAM_LIST_CODE.
  • BNE_INTERFACE_COLS_TL — translations for the interface columns that consume components.
  • FND_APPLICATION — resolves APPLICATION_ID and PARAM_LIST_APP_ID to application names.
  • FND_LOV_COLUMNS / FND_LOOKUPS — related LOV metadata that complements component definitions.

Together these objects form the metadata layer that Web Applications Desktop Integrator uses to generate, validate, and render desktop-integrated spreadsheet content within Oracle EBS.