Search Results dup_profile_code




Overview
Explore in AI Chat

Overview

BNE_DUP_INTERFACE_COLS is a table in the BNE schema (Web Applications Desktop Integrator) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of duplicate upload profiles for interface columns, acting as a mapping layer between a Web ADI interface definition and the duplicate-handling profile that governs how repeated rows are processed during upload. Each record binds a specific interface column — identified by application, interface code, and sequence number — to a duplicate profile that determines the resolution semantics applied when duplicate keys are encountered.

From a modeling perspective, the mined relationship structure classifies this object heuristically as a link table. This is a modeling suggestion: the table does not hold descriptive transactional attributes of its own beyond audit columns, but instead resolves a many-to-many association between interface column definitions and duplicate profiles.

Key Information Stored

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

The composite primary key, BNE_DUP_INTERFACE_COLS_PK, spans INTERFACE_APP_ID, INTERFACE_CODE, INTERFACE_SEQ_NUM, DUP_PROFILE_APP_ID, and DUP_PROFILE_CODE. A unique index, BNE_DUP_INTERFACE_COLS_UK1, extends these same business-key columns with ZD_EDITION_NAME, confirming the natural key is the full composite of interface identity plus duplicate profile identity.

Common Use Cases and Queries

Typical usage involves diagnosing why an upload produced duplicate rejection messages, auditing which duplicate profile applies to a given column, or reporting profile coverage across interfaces.

To find all duplicate profile assignments for an interface:

  • SELECT INTERFACE_CODE, INTERFACE_SEQ_NUM, DUP_PROFILE_APP_ID, DUP_PROFILE_CODE, RESOLVER_CLASSNAME FROM BNE.BNE_DUP_INTERFACE_COLS WHERE INTERFACE_APP_ID = :app_id AND INTERFACE_CODE = :code ORDER BY INTERFACE_SEQ_NUM;

To trace resolution logic used by a specific column:

  • SELECT c.INTERFACE_SEQ_NUM, c.DUP_PROFILE_CODE, c.RESOLVER_CLASSNAME FROM BNE.BNE_DUP_INTERFACE_COLS c WHERE c.INTERFACE_APP_ID = :app_id AND c.INTERFACE_CODE = :code AND c.INTERFACE_SEQ_NUM = :seq;

Reporting queries frequently join to BNE_DUP_INTERFACE_PROFILES to render profile descriptions, and to BNE_INTERFACE_COLS_B to render the human-readable column prompt. Because of the ZD_EDITION_NAME column, queries on 12.2 should generally filter or account for the active edition when duplicate rows across editions may exist.

Related Objects

  • BNE_INTERFACE_COLS_B — referenced by the foreign key on INTERFACE_APP_ID, INTERFACE_CODE, INTERFACE_SEQ_NUM. This is the base interface column definition table and the primary parent in the relationship.
  • BNE_DUP_INTERFACE_PROFILES — referenced by the foreign key on INTERFACE_APP_ID and DUP_PROFILE_CODE (via INTERFACE_APP_ID and DUP_PROFILE_CODE), supplying the duplicate-handling profile definition enriched by BNE_DUP_INTERFACE_COLS.
  • BNE_DUP_INTERFACE_COLS_PK — the primary key constraint enforcing uniqueness of interface column and duplicate profile combinations.
  • BNE_DUP_INTERFACE_COLS_UK1 — the unique business-key index including ZD_EDITION_NAME for edition-aware enforcement.
  • Web ADI upload engine APIs and concurrent programs consume this table indirectly through the interface loader to determine duplicate resolution behavior during row processing.