Search Results bne_interface_cols_vl




Overview
Explore in AI Chat

Overview

BNE_INTERFACE_COLS_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 part of the BNE product, Web Applications Desktop Integrator (Web ADI), which drives the desktop integration and spreadsheet upload/download framework across EBS. The view exposes the column-level definition of Web ADI interfaces — that is, the metadata that determines how each column of a BNE interface is rendered, validated, mapped, and uploaded.

As a "_VL" view, it joins the base entity table to its translation table and filters on the session language via USERENV('LANG'), returning a single row per interface column for the current language. This makes it the canonical, language-resolved source for interface column metadata, and it is the object that consumers should query rather than the underlying _B table when translated prompt text or help text is required. In the context of the user's search for val_component_app_id, the view is the published access point for that attribute along with the broader set of value-list and validation descriptors.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

  • BNE_INTERFACE_COLS_B — the base (non-translated) table holding the operational column definitions, including application, interface code, sequence, data type, validation, and mapping attributes. Aliased as B in the view text.
  • BNE_INTERFACE_COLS_TL — the translation table holding language-specific text such as prompts and user help. Aliased as T.

The join predicates are B.APPLICATION_ID = T.APPLICATION_ID AND B.INTERFACE_CODE = T.INTERFACE_CODE AND B.SEQUENCE_NUM = T.SEQUENCE_NUM, with the additional filter T.LANGUAGE = USERENV('LANG'). Because the _B and _TL tables are synonymous with APPS, the view resolves entirely within the APPS schema and follows the standard EBS MLS view pattern.

Key Columns

The view exposes the full column set of the base entity. Notable columns include:

Common Use Cases and Queries

Typical uses include diagnosing why a Web ADI column validates or uploads incorrectly, auditing value-list configuration, and reporting on interface column layout. A common starting point is to list columns for a given interface:

  • SELECT interface_col_name, data_type, val_type, val_component_app_id, val_component_code FROM bne_interface_cols_vl WHERE application_id = :app_id AND interface_code = :iface ORDER BY sequence_num;
  • SELECT interface_code, sequence_num, val_component_app_id, val_component_code FROM bne_interface_cols_vl WHERE val_component_app_id IS NOT NULL;
  • SELECT interface_col_name, prompt_left, user_help_text FROM bne_interface_cols_vl WHERE application_id = :app_id AND interface_code = :iface;

Because the view applies the language filter automatically, it is preferred over querying BNE_INTERFACE_COLS_B directly when translated prompts or help text are required.