Search Results bne_duplicate_profiles_tl_uk1

Overview

BNE.BNE_DUPLICATE_PROFILES_TL is a translation (TL) table in the Oracle E-Business Suite BNE schema. It stores the language-dependent, translatable text associated with duplicate upload profiles used by the Oracle iSupplier / Supplier Network (BNE) module for managing bulk supplier and user data uploads. Each row represents the translated definition of a duplicate upload profile — the configuration that determines how the system detects and handles duplicate records during a bulk upload operation.

In Oracle EBS 12.1.1 and 12.2.2, the BNE schema underpins supplier registration, supplier onboarding, and bulk data loading processes. The TL suffix indicates this table follows the standard EBS multi-language translations pattern, pairing with a base table (typically BNE_DUPLICATE_PROFILES_B) through the composite key of APPLICATION_ID, DUP_PROFILE_CODE, and LANGUAGE. A SOURCE_LANG column enables the standard EBS translation synchronization behavior, where changes to the source language row propagate to untranslated rows. As a language-dependent child of a configuration entity, the object functions, from a Data Vault modeling perspective, as a satellite table — it carries descriptive, descriptive-context attributes keyed to the parent profile and language, rather than acting as an independent hub or a relationship link.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• APPLICATION_ID — Numeric identifier of the owning application; a foreign key to FND_APPLICATIONS.APPLICATION_ID. It scopes the profile to a specific EBS application context.
• DUP_PROFILE_CODE — A VARCHAR2(30) unique code identifying the duplicate profile entity for the given APPLICATION_ID.
• LANGUAGE — The language of the translated row, forming part of the composite primary key.
• SOURCE_LANG — The language the text mirrors; changes made to the source language row are reflected in this row until a translation is explicitly provided.
• USER_NAME — A VARCHAR2(240) column holding the profile's display name or descriptive text. Despite the column name, the documented comment describes it as SQL query text that may contain tokens, and it is the primary translatable content.
• ZD_EDITION_NAME — The editioning column supporting Oracle EBS 12.2 online patching (Edition-Based Redefinition), allowing multiple editions of the row to coexist during patching cycles.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard EBS "Who" audit columns recording creation and last-update metadata, with CREATED_BY and LAST_UPDATED_BY referencing FND_USER.USER_ID and LAST_UPDATE_LOGIN referencing FND_LOGINS.LOGIN_ID.

The documented surrogate primary key is BNE_DUPLICATE_PROFILES_TL_PK (APPLICATION_ID, DUP_PROFILE_CODE, LANGUAGE). The unique index the user searched for, BNE_DUPLICATE_PROFILES_TL_UK1, is defined on (APPLICATION_ID, DUP_PROFILE_CODE, LANGUAGE, ZD_EDITION_NAME) in the APPS_TS_TX_IDX tablespace — a business-key candidate that extends the PK with the editioning column to enforce uniqueness within an edition.

Common Use Cases and Queries

Functional consultants and developers query this table to inspect or troubleshoot duplicate-handling configuration during supplier bulk uploads, and to report on profile descriptions in specific languages. A typical lookup retrieves the translated profile text for a given application and language:

• SELECT dup_profile_code, user_name, source_lang FROM bne.bne_duplicate_profiles_tl WHERE application_id = :app_id AND language = USERENV('LANG');
• Joining to the base profile table to list all profiles with their translations, filtering on the edition: WHERE zd_edition_name = 'SET1'.
• Auditing translation currency by comparing rows where source_lang <> language.

Reporting scenarios include validating that every DUP_PROFILE_CODE has a row for each installed language, and confirming the Who columns for change-tracking during support investigations.

Related Objects

The object is classified as standalone in the mined relationship data, meaning it does not itself reference other tables via enforced foreign keys within the mined set, though it is referenced logically by the following:

• BNE.BNE_DUPLICATE_PROFILES_B — the base (non-translated) table, joined on APPLICATION_ID, DUP_PROFILE_CODE, and LANGUAGE/ZD_EDITION_NAME.
• FND_APPLICATIONS — referenced via APPLICATION_ID.
• FND_USER — referenced via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced via LAST_UPDATE_LOGIN.
• BNE_DUPLICATE_PROFILES_TL_PK and BNE_DUPLICATE_PROFILES_TL_UK1 — the primary and unique indexes enforcing row and business-key uniqueness.

These objects should be considered together when tracing duplicate-profile configuration and its translated presentation in the Oracle EBS data model.