Search Results bne_contents

Overview

BNE_CONTENTS_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 family, Web Applications Desktop Integrator (Web ADI), which provides spreadsheet-based data entry, upload, and download capabilities against EBS forms and interfaces. The view exposes the content definitions that Web ADI uses to describe integrators, parameter lists, and downloadable content registered in the BNE repository.

In EBS reporting and integration terms, BNE_CONTENTS_VL is the language-aware read layer over the underlying BNE_CONTENTS entity. It presents the descriptive USER_NAME attribute resolved to the session language, while preserving the language-independent key and audit attributes from the base table. Because the view filters the translation table on USERENV('LANG'), it returns exactly one row per content definition, translated into the language of the connected user. It is therefore the correct object to query when building reports, data extracts, or integration lookups that must display content names in the user's own language.

Underlying Base Objects

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

• BNE_CONTENTS_B — the base (language-independent) table holding the primary key, integrator linkage, parameter list linkage, content classification, audit columns, and the once-only download flag.
• BNE_CONTENTS_TL — the translation table holding the language-dependent USER_NAME, keyed by APPLICATION_ID, CONTENT_CODE, and LANGUAGE.

The two are joined on the composite key APPLICATION_ID and CONTENT_CODE, with the translation table restricted to T.LANGUAGE = USERENV('LANG'). This is the canonical Oracle multi-lingual schema pattern (_B base, _TL translation, _VL view), ensuring the view remains in step with whatever language the runtime session has established.

Key Columns

• ROW_ID — the base table ROWID, exposed for row identification and typically not used in application logic.
• APPLICATION_ID — the owning application of the content definition; part of the composite primary key.
• CONTENT_CODE — the unique content identifier within the application; the second component of the primary key.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Web ADI framework to detect concurrent updates.
• INTEGRATOR_APP_ID / INTEGRATOR_CODE — identify the integrator to which the content belongs.
• PARAM_LIST_APP_ID / PARAM_LIST_CODE — identify the parameter list associated with the content definition.
• CONTENT_CLASS — classifies the content type within the BNE framework.
• USER_NAME — the translated, user-facing name of the content, sourced from BNE_CONTENTS_TL.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard EBS audit columns from the base table.
• ONCE_ONLY_DOWNLOAD_FLAG — indicates whether the content may be downloaded only once.

Common Use Cases and Queries

The view is queried when administrators and developers need to report on, audit, or join against registered Web ADI content. Typical scenarios include listing all content defined for a given integrator, verifying parameter list assignments, and producing translated content inventories for documentation. A representative query follows:

SELECT application_id,
       content_code,
       user_name,
       integrator_app_id,
       integrator_code,
       param_list_app_id,
       param_list_code,
       content_class,
       once_only_download_flag
FROM   apps.bne_contents_vl
WHERE  integrator_code = :integrator_code
ORDER BY user_name;

Because the view enforces the translation join and language filter internally, callers avoid writing their own _B/_TL join logic and are guaranteed a single, correctly localized row per content definition. It is the recommended interface for any read-only access to BNE content metadata.