Search Results bne_dup_interface_profiles




Overview
Explore in AI Chat

Overview

The BNE_DUP_INTERFACE_PROFILES table resides in the BNE schema and belongs to the Web Applications Desktop Integrator (Web ADI) product family. It stores the definition of a duplicate upload profile associated with a specific interface. In Oracle EBS, Web ADI enables users to upload spreadsheet-based data into application interfaces, and duplicate handling is a critical control point during those uploads. This table serves as the association layer that binds a given interface to the duplicate profile governing how duplicate records are detected and resolved during the upload cycle.

From a dimensional modeling perspective, the mined Data Vault classification for this object is a link. This classification reflects the table's structure: it carries no independent descriptive identity of its own but instead resolves the many-to-many relationship between an interface definition and a duplicate profile definition. The four-column primary key (INTERFACE_APP_ID, INTERFACE_CODE, DUP_PROFILE_APP_ID, DUP_PROFILE_CODE) reinforces this linking function, since both composite foreign keys participate directly in the primary key.

Key Information Stored

The table contains 13 documented columns. The most significant are described below.

The surrogate primary key is BNE_DUP_INTERFACE_PROFILES_PK over the four linking columns. The unique index BNE_DUP_INTERFACE_PROFILES_UK1 (INTERFACE_APP_ID, INTERFACE_CODE, DUP_PROFILE_APP_ID, DUP_PROFILE_CODE, ZD_EDITION_NAME) functions as the business-key candidate, enforcing that a given interface-profile pairing is unique within an edition.

Common Use Cases and Queries

Typical use cases involve verifying which duplicate profile governs a given interface, auditing duplicate handling configuration, and generating reports on interface-to-profile mappings. A representative query joining the parent tables follows:

  • SELECT dip.interface_code, dip.dup_profile_code, dip.dup_handling_code, dip.default_resolver_classname FROM bne.bne_dup_interface_profiles dip WHERE dip.interface_app_id = :app_id AND dip.interface_code = :code;
  • Joining to BNE_DUPLICATE_PROFILES_B to retrieve the profile name and description for reporting purposes.
  • Filtering by ZD_EDITION_NAME to isolate records belonging to the active edition during online patching windows.
  • Auditing records modified within a date range using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The following objects are most significant in relation to this table:

  • BNE_DUPLICATE_PROFILES_B — referenced via DUP_PROFILE_APP_ID and DUP_PROFILE_CODE; holds the duplicate profile definitions.
  • BNE_INTERFACES_B — referenced via INTERFACE_APP_ID and INTERFACE_CODE; holds the interface definitions.
  • BNE_DUPLICATE_PROFILES_TL — typically provides translated profile names for reporting.
  • BNE_INTERFACES_TL — typically provides translated interface names.
  • BNE_DUP_INTERFACE_PROFILES_UK1 — the unique index enforcing business-key uniqueness.

These relationships make BNE_DUP_INTERFACE_PROFILES a central configuration link for Web ADI upload duplicate-handling behavior across EBS releases 12.1.1 and 12.2.2, with the ZD_EDITION_NAME column present specifically to support the 12.2.x online patching architecture.