Search Results bne_viewers_vl




Overview
Explore in AI Chat

Overview

BNE_VIEWERS_VL is a standard Oracle E-Business Suite translation (MLS) view owned by the APPS schema and delivered as part of the BNE – Web Applications Desktop Integrator product. Its functional purpose is to expose the viewer definitions registered with the Desktop Integrator framework, presenting both the language-independent attributes from the base entity and the current-session translated display name. The "_VL" suffix denotes a view that joins the "_B" (base) and "_TL" (translation) tables and restricts the translation rows to the language of the connected user session or responsibility, as determined by USERENV('LANG').

In reporting and integration terms, this view is the supported presentation layer for viewer configuration data. Rather than querying the underlying base tables directly, concurrent programs, forms, OAF pages, and custom reports reference the _VL view so that the correct translated viewer name is returned without the developer having to code the language join manually. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and retains the same definition across those releases.

Underlying Base Objects

The view is defined over two synonym-referenced base objects within the APPS schema:

  • BNE_VIEWERS_B – the base table holding language-independent viewer attributes.
  • BNE_VIEWERS_TL – the translation table holding the language-specific user_name value.

The join is performed on the composite key APPLICATION_ID plus VIEWER_CODE, with an additional filter on BNE_VIEWERS_TL.LANGUAGE = USERENV('LANG'). The view text also exposes the base table ROWID aliased as ROW_ID, and carries the standard WHO audit columns and OBJECT_VERSION_NUMBER for optimistic locking.

Key Columns

  • ROW_ID – the base table ROWID, used for row identification in the Desktop Integrator framework.
  • APPLICATION_ID – the application owning the viewer definition.
  • VIEWER_CODE – the unique code identifying the viewer within the application.
  • USER_NAME – the translated, user-facing viewer name sourced from BNE_VIEWERS_TL.
  • VIEWER_JAVA_CLASS – the Java class implementing the viewer.
  • PARAM_LIST_APP_ID / PARAM_LIST_CODE – identify the parameter list associated with the viewer.
  • CREATE_DOC_LIST_APP_ID / CREATE_DOC_LIST_CODE – the document list used when the viewer creates output; this is the column referenced by searches for "create_doc_list_code".
  • ENABLED_FLAG – indicates whether the viewer definition is active.
  • OBJECT_VERSION_NUMBER – optimistic locking / concurrency control attribute.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – standard WHO audit columns.

Common Use Cases and Queries

Typical uses include validating viewer registration, auditing which document list drives viewer output creation, and populating LOVs in Desktop Integrator components. A query listing enabled viewers for the current session language is:

SELECT application_id, viewer_code, user_name, viewer_java_class,
create_doc_list_app_id, create_doc_list_code, enabled_flag
FROM apps.bne_viewers_vl
WHERE enabled_flag = 'Y'
ORDER BY application_id, viewer_code;

To locate viewers associated with a specific document list code, as suggested by the "create_doc_list_code" search term:

SELECT application_id, viewer_code, user_name, create_doc_list_app_id, create_doc_list_code
FROM apps.bne_viewers_vl
WHERE create_doc_list_code = :p_doc_list_code;

Because the view already restricts translation rows by USERENV('LANG'), callers must ensure the concurrent program or session language is set correctly to obtain the intended translated USER_NAME; otherwise a fallback language row will not be returned and the viewer may appear absent from the result set.