Search Results bne_duplicate_profiles

Overview

BNE_DUPLICATE_PROFILES_VL is a standard translation (VL) view owned by the APPS schema within the BNE – Web Applications Desktop Integrator product family. It exposes the duplicate profile definitions maintained by the Web Applications Desktop Integrator (Web ADI), the framework that allows Oracle E-Business Suite users to upload and download data between desktop applications and EBS forms. The view resolves the language-dependent attributes of a duplicate profile into the session language, presenting a single, query-ready row per profile for the currently connected user. Status is documented as VALID in ETRM for both 12.1.1 and 12.2.2.

Because it is a _VL view rather than a base table, it is the object that should be referenced in custom reports, BI Publisher data models, OA Framework pages, and integration extracts. Querying the _VL view automatically applies the language filter and blends the descriptive translation rows, removing the need for report developers to join the _B and _TL tables manually. This makes it the conventional entry point for any reporting requirement that must resolve a duplicate profile code into a user-facing name.

Underlying Base Objects

The view is defined over two documented synonyms: BNE_DUPLICATE_PROFILES_B, the base (language-independent) table, and BNE_DUPLICATE_PROFILES_TL, the translation table. The join is performed on the composite key of APPLICATION_ID and DUP_PROFILE_CODE, with the translation side additionally restricted to LANGUAGE = USERENV('LANG') so that only the row matching the current session language is returned. A ROWID from the base table is aliased as ROW_ID, and the translation column USER_NAME supplies the display name associated with the profile code. The view therefore behaves as a denormalized, language-resolved projection of the two physical tables.

Key Columns

• ROW_ID – the ROWID of the underlying BNE_DUPLICATE_PROFILES_B row, useful for row-level identification.
• APPLICATION_ID – the application owning the duplicate profile; part of the composite primary key.
• DUP_PROFILE_CODE – the internal code identifying the duplicate profile; the second component of the composite key.
• OBJECT_VERSION_NUMBER – optimistic locking column used by the Web ADI framework during DML.
• INTEGRATOR_APP_ID, INTEGRATOR_CODE – identify the integrator to which the duplicate profile is attached.
• USER_NAME – the translated, user-facing name of the duplicate profile, sourced from the TL table.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include auditing which duplicate profiles are defined for an integrator, validating profile configuration before a Web ADI upload, and joining duplicate profile codes to human-readable names in extracts. Because the view is language-aware, it is also suitable for multilingual environments where USER_NAME must follow the user's session language.

A representative query listing profiles for a given integrator:

• SELECT application_id, dup_profile_code, user_name, integrator_code FROM apps.bne_duplicate_profiles_vl WHERE integrator_code = :integrator_code;

A second pattern joins the view back to the base table to reconcile all language rows for administrative review:

• SELECT v.dup_profile_code, v.user_name, t.language FROM apps.bne_duplicate_profiles_vl v, apps.bne_duplicate_profiles_tl t WHERE v.application_id = t.application_id AND v.dup_profile_code = t.dup_profile_code;

Access should be granted through the standard APPS synonyms; direct queries against the _B and _TL tables are unnecessary when the _VL view satisfies the requirement.