Search Results reporting_interface_code




Overview
Explore in AI Chat

Overview

BNE_MAPPINGS_VL is a standard translation (MLS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a member of the BNE product family — Web Applications Desktop Integrator — which governs the integration, mapping, and reporting definitions used by desktop and spreadsheet-based interfaces such as Web ADI and Oracle's reporting tools. The view presents the mapping definitions stored in the BNE_MAPPINGS entity together with the language-specific display name held in the translation layer.

Its principal role is to expose a single, language-aware rowset for each mapping definition, so that reports, concurrent programs, and lookup-based user interfaces can retrieve the mapping code together with its translated USER_NAME without joining the base and translation tables explicitly. The view resolves the current session language through USERENV('LANG'), returning only the translation row that matches the caller's environment. This makes it suitable for reporting and inquiry screens where a human-readable name is required. Users searching for reporting_interface_code will find that column exposed directly by this view, which is the reporting-oriented mapping attribute maintained by Web ADI.

Underlying Base Objects

The view is defined over two base objects, both exposed to APPS as synonyms: BNE_MAPPINGS_B, which holds the language-independent mapping definition, and BNE_MAPPINGS_TL, which holds the translated user-facing name. The join is driven by the composite key APPLICATION_ID plus MAPPING_CODE, with the translation restricted to the session language:

The documented view text confirms that ROW_ID is derived from M.ROWID, and that all descriptive mapping attributes originate from the base table while only the name is language sensitive. The view is reported as VALID in both 12.1.1 and 12.2.2, and the underlying tables may be partitioned, so queries should be filtered on the leading key columns to obtain the best execution plan.

Key Columns

  • ROW_ID — the row identifier of the base mapping record, derived from the base table ROWID.
  • APPLICATION_ID — the application that owns the mapping definition; part of the primary key.
  • MAPPING_CODE — the internal code identifying the mapping; part of the primary key.
  • USER_NAME — the translated, user-facing name of the mapping, resolved for the session language.
  • INTEGRATOR_APP_ID and INTEGRATOR_CODE — identify the integrator associated with the mapping.
  • REPORTING_FLAG — indicates whether the mapping is enabled for reporting purposes.
  • REPORTING_INTERFACE_APP_ID and REPORTING_INTERFACE_CODE — identify the reporting interface to which the mapping is bound; these are the columns users typically retrieve when searching on reporting_interface_code.
  • OBJECT_VERSION_NUMBER — the optimistic locking version used by the underlying OAF/BC4J entities.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes validating mapping and reporting-interface configuration, extracting mapping definitions for integration documentation, and joining the view to lookup or application tables to resolve reporting interfaces. The following query lists all mappings linked to a reporting interface:

  • SELECT m.application_id, m.mapping_code, m.user_name, m.reporting_flag, m.reporting_interface_app_id, m.reporting_interface_code FROM apps.bne_mappings_vl m WHERE m.reporting_interface_code = :p_reporting_interface_code ORDER BY m.application_id, m.mapping_code;

To list every mapping where reporting is enabled:

  • SELECT m.application_id, m.mapping_code, m.user_name, m.reporting_interface_app_id, m.reporting_interface_code FROM apps.bne_mappings_vl m WHERE m.reporting_flag = 'Y' ORDER BY m.application_id, m.mapping_code;

Because USER_NAME is filtered to the session language, callers requiring a specific language should set the corresponding NLS session parameter, or query BNE_MAPPINGS_TL directly with an explicit LANGUAGE predicate. For bulk extraction or audit purposes, the view may be joined to FND_APPLICATION_VL on the application identifiers to resolve application and integrator names.