Search Results bne_duplicate_profiles_b_pk

Overview

BNE_DUPLICATE_PROFILES_B is a core definition table within the BNE (Web Applications Desktop Integrator) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the definition of a duplicate upload profile. In the context of ETRM and Desktop Integrator, a duplicate profile governs how uploaded spreadsheet or interface data is matched against existing records to detect and handle duplicates during Web ADI uploads and integrations. The table resides in the BNE schema and is referenced by integration and interface profile configuration, making it a configuration-level entity rather than a transactional one.

Under the heuristic Data Vault classification mined from its foreign key structure, this object is satellite-leaning. This is a modeling suggestion: the table's business identity depends on external keys (integrator context) and its descriptive attributes hang off that identity, so a Data Vault implementation would typically represent it as a satellite keyed to a hub or link rather than as an independent hub.

Key Information Stored

The table contains 11 documented columns. Its surrogate primary key is defined by the constraint BNE_DUPLICATE_PROFILES_B_PK over (APPLICATION_ID, DUP_PROFILE_CODE). A separate unique index, BNE_DUPLICATE_PROFILES_B_UK1, covers (APPLICATION_ID, DUP_PROFILE_CODE, ZD_EDITION_NAME) and serves as the business-key candidate, adding edition scoping to the identity.

• APPLICATION_ID — identifies the owning application; part of the primary key.
• DUP_PROFILE_CODE — the profile code naming the duplicate upload profile; part of the primary key.
• INTEGRATOR_APP_ID — foreign key to BNE_INTEGRATORS_B, associating the profile with an integrator.
• INTEGRATOR_CODE — the integrator code used together with INTEGRATOR_APP_ID for the integrator relationship.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column used by the framework.
• ZD_EDITION_NAME — editioning column supporting the EBS editioning model; participates in the UK1 business key.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording creation metadata.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording last modification metadata.

The primary key provides the technical unique identity, while the unique index over APPLICATION_ID, DUP_PROFILE_CODE, and ZD_EDITION_NAME represents the candidate business key, since the same profile code may legitimately exist across editions.

Common Use Cases and Queries

Typical uses center on configuration reporting and tracing how duplicate-handling behavior is defined for a given integrator. Administrators and support analysts query this table to confirm which duplicate profiles exist, which integrator they belong to, and to trace relationships with interface profiles.

A representative query joins the integrator lookup:

• SELECT dpb.APPLICATION_ID, dpb.DUP_PROFILE_CODE, dpb.INTEGRATOR_APP_ID, dpb.INTEGRATOR_CODE FROM BNE.BNE_DUPLICATE_PROFILES_B dpb WHERE dpb.APPLICATION_ID = :app_id;

To identify profiles by integrator, filter on INTEGRATOR_CODE or join to BNE_INTEGRATORS_B. To trace dependent interface profiles, join forward to BNE_DUP_INTERFACE_PROFILES on DUP_PROFILE_APP_ID and DUP_PROFILE_CODE. Reporting extracts frequently include creation and update audit columns to support change tracking, while ZD_EDITION_NAME is used to scope queries to the active edition during patching and edition-based redefinition analysis.

Related Objects

• BNE_INTEGRATORS_B — referenced by this table; join on BNE_DUPLICATE_PROFILES_B.INTEGRATOR_APP_ID = BNE_INTEGRATORS_B.INTEGRATOR_APP_ID and INTEGRATOR_CODE.
• BNE_DUP_INTERFACE_PROFILES — references this table; join on DUP_PROFILE_APP_ID = APPLICATION_ID and DUP_PROFILE_CODE.
• BNE_DUPLICATE_PROFILES_TL — the translated/child table that typically accompanies the "_B" base table, holding language-specific descriptions.
• BNE_DUPLICATE_PROFILE_COLS — likely related child table defining the columns used by a duplicate profile.
• BNE_INTEGRATORS_TL — the translation table for integrator names, joined indirectly through BNE_INTEGRATORS_B.

The "_B" suffix indicates a base table in the BNE translation pattern, so corresponding "_TL" tables should be consulted when descriptive text is required. Together these objects form the duplicate-detection configuration layer consumed by Desktop Integrator uploads and interface processing.