Search Results bne_mappings_b




Overview
Explore in AI Chat

Overview

BNE_MAPPINGS_B is a core configuration table in the BNE (Web Applications Desktop Integrator) product of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. It stores the definition of mappings between spreadsheet contents and interface columns, forming the metadata backbone that Web ADI uses to translate user-entered or uploaded spreadsheet values into the columns of an Oracle EBS interface table. Each row associates a mapping definition with a specific integrator and, where relevant, a reporting interface, enabling Web ADI to construct the layout, validations, and column-to-attribute relationships presented to end users.

From a Data Vault modeling perspective, the mined FK structure classifies BNE_MAPPINGS_B as satellite-leaning. This is a modeling suggestion rather than a physical implementation: the table behaves largely as descriptive metadata hanging off the integrator and reporting-interface hubs, with its child detail rows in BNE_MAPPING_LINES representing the finer-grained link and descriptive content. The table is owned by the BNE schema and carries a single-table primary key constraint, BNE_MAPPINGS_B_PK, defined on the composite of MAPPING_CODE and APPLICATION_ID.

Key Information Stored

The documented physical schema for 12.2.2 contains 14 columns. The most operationally significant are:

Note that the composite primary key differs from the business-key candidate surfaced by the unique index: BNE_MAPPINGS_B_UK1 adds ZD_EDITION_NAME, reflecting the 12.2 editioning model.

Common Use Cases and Queries

Typical scenarios include auditing which mappings exist for a given integrator, tracing a mapping to its interface, and diagnosing Web ADI layout or upload failures. A representative query joining the parent integrator and interface follows:

  • SELECT m.mapping_code, m.integrator_code, m.reporting_interface_code, m.reporting_flag, m.last_update_date FROM bne_mappings_b m WHERE m.integrator_app_id = :app_id AND m.integrator_code = :integrator_code;
  • SELECT m.mapping_code, l.* FROM bne_mappings_b m JOIN bne_mapping_lines l ON l.application_id = m.application_id AND l.mapping_code = m.mapping_code WHERE m.mapping_code = :mapping_code;
  • SELECT m.* FROM bne_mappings_b m WHERE m.reporting_flag = 'Y' AND m.application_id = :app_id;

Reporting use cases center on inventorying mapping definitions per integrator, verifying edition-scoped rows in 12.2 (ZD_EDITION_NAME), and supporting migration or comparison of Web ADI configurations across environments.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

  • BNE_MAPPING_LINES — child detail table; joins on APPLICATION_ID and MAPPING_CODE.
  • BNE_INTERFACES_B — parent interface definition; referenced via REPORTING_INTERFACE_APP_ID and REPORTING_INTERFACE_CODE.
  • BNE_INTEGRATORS_B — parent integrator definition; referenced via INTEGRATOR_APP_ID and INTEGRATOR_CODE.
  • BNE_MAPPINGS_TL — translation table for mapping names/descriptions (by convention in BNE).
  • BNE_MAPPINGS_VL — the multilingual view commonly used for reporting and lookups.

Collectively these objects define the Web ADI mapping metadata model, with BNE_MAPPINGS_B serving as the parent anchor for mapping lines and the join point to interfaces and integrators.