Search Results bne_stylesheets_vl




Overview

BNE_STYLESHEETS_VL is a standard translation (VL) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the BNE product family — Web Applications Desktop Integrator (Web ADI) — which provides the spreadsheet-based interface used to upload and download EBS data. The view presents a language-resolved, user-facing representation of the stylesheet definitions stored in the Web ADI repository, pairing each stylesheet's language-independent attributes with the translated user name and description appropriate to the session.

The "_VL" suffix denotes a view that joins a base ("_B") table with its translation ("_TL") table, filtering the translation row by the runtime language of the session. This pattern is pervasive throughout EBS and allows reporting tools, concurrent programs, and OAF/Forms pages to retrieve a single denormalized row per entity without manually joining the translation table or resolving language precedence. For BNE_STYLESHEETS_VL, the effect is that every query returns the stylesheet code, its behavioral flags, and the human-readable name and description in the user's current language.

The view is read-only by design. DML against a _VL view is not supported; inserts and updates must target BNE_STYLESHEETS_B and BNE_STYLESHEETS_TL directly. This makes the view a reporting and lookup construct rather than a maintenance interface.

Underlying Base Objects

BNE_STYLESHEETS_VL is defined over two synonyms that resolve to the underlying BNE tables:

  • BNE_STYLESHEETS_B — the base table holding language-independent attributes of each stylesheet, including APPLICATION_ID, STYLESHEET_CODE, the default and read-only flags, the image file name, and standard WHO audit columns.
  • BNE_STYLESHEETS_TL — the translation table holding USER_NAME and DESCRIPTION per language.

The join condition is a composite key on APPLICATION_ID and STYLESHEET_CODE, combined with the language filter T.LANGUAGE = USERENV('LANG'). Because the translation side is restricted to the session language, only one TL row per stylesheet is returned; if no translation exists for the current language, the row is omitted entirely (an inner join, not an outer join). The view also exposes S.ROWID AS ROW_ID, a convenience column often used by EBS framework code to uniquely identify the underlying base row.

Key Columns

  • ROW_ID — the ROWID of the BNE_STYLESHEETS_B row, useful as a surrogate row identifier.
  • APPLICATION_ID — the owning application; combined with STYLESHEET_CODE it forms the primary key.
  • STYLESHEET_CODE — the developer-facing unique code for the Web ADI stylesheet.
  • OBJECT_VERSION_NUMBER — optimistic locking version, incremented on each update.
  • USER_NAME — the translated display name of the stylesheet.
  • DESCRIPTION — the translated description of the stylesheet's purpose.
  • DEFAULT_FLAG — "Y"/"N", defaulted to "N" via NVL; indicates whether the stylesheet is the default for its context.
  • READ_ONLY_FLAG — "Y"/"N", defaulted to "N"; indicates whether the stylesheet is protected from modification.
  • IMAGE_FILE_NAME — the file name of the image associated with the stylesheet (the column the user searched for). This value typically points to an icon or graphic stored in the Web ADI image repository and rendered in the desktop integrator UI.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO audit columns.

Common Use Cases and Queries

The view is most often queried for metadata extraction, personalization diagnostics, and integration checks. A typical check for a specific image file is:

SELECT application_id, stylesheet_code, user_name, image_file_name
FROM apps.bne_stylesheets_vl
WHERE image_file_name = 'MYICON.gif';

To list all active stylesheets with their flags:

SELECT stylesheet_code, user_name, default_flag, read_only_flag
FROM apps.bne_stylesheets_vl
WHERE read_only_flag = 'N'
ORDER BY user_name;

To reconcile translations — for example, confirming which stylesheets lack a row in the session language — query BNE_STYLESHEETS_B and left-join BNE_STYLESHEETS_TL directly rather than the VL view, because the VL view suppresses untranslated rows. Finally, because the view resolves USERENV('LANG'), running the same SELECT in a different language session demonstrates translation coverage and is a common sanity check when validating multilingual Web ADI deployments.