Search Results bne_interface_keys_uk1

Overview

BNE.BNE_INTERFACE_KEYS is a metadata repository table within the Oracle E-Business Suite BNE (Business Intelligence/Interface) schema. It defines the logical keys over an interface, meaning it records the unique identifiers that govern how records flowing through an Oracle EBS interface are distinguished from one another. Each row associates a business key definition with a specific application and interface, allowing the integration layer to detect duplicates and enforce uniqueness during data transformation and load. In ETRM 12.1.1 and 12.2.2 the object is marked VALID and resides in the APPS_TS_TX_DATA tablespace with an FND Design Data registration of BNE.BNE_INTERFACE_KEYS.

From a dimensional modeling perspective, the mined heuristic classifies this table as satellite-leaning. This suggests it functions primarily as an attribute-bearing description of a parent interface definition rather than an independent transactional hub, with its foreign key to BNE_INTERFACES_B anchoring the surrounding context. The 12.2.2 edition also carries the ZD_EDITION_NAME column, indicating participation in the EBS online patching editioning model.

Key Information Stored

The table carries thirteen documented columns. The most operationally significant are summarized below.

• APPLICATION_ID (NUMBER, 15) — Foreign key to FND_APPLICATIONS.APPLICATION_ID, identifying the owning application. Part of the surrogate primary key BNE_INTERFACE_KEYS_PK.
• KEY_CODE (VARCHAR2, 30) — A code uniquely identifying the entity for a given APPLICATION_ID. The second component of the primary key and the core business identifier.
• OBJECT_VERSION_NUMBER (NUMBER, 15) — Optimistic locking control used by the framework for concurrent updates.
• INTERFACE_APP_ID (NUMBER, 15) — The application id of the interface this key belongs to; joins to BNE_INTERFACES_B.
• INTERFACE_CODE (VARCHAR2, 30) — The interface code that this key definition describes.
• KEY_TYPE (VARCHAR2, 30) — Classifies the nature of the key (for example primary versus alternate).
• KEY_CLASS (VARCHAR2, 240) — Names the pluggable Java class responsible for generating duplicate keys, enabling extensibility of key handling.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard WHO audit columns tracking row provenance and change history.
• ZD_EDITION_NAME — Editioning selector introduced under the 12.2.2 online patching architecture.

The documented unique index BNE_INTERFACE_KEYS_UK1 covers (APPLICATION_ID, KEY_CODE, ZD_EDITION_NAME), confirming that the combination of application and key code is the intended business-key candidate. The non-unique index BNE_INTERFACE_KEYS_N1 covers (INTERFACE_APP_ID, INTERFACE_CODE), supporting interface-driven lookups. The primary key BNE_INTERFACE_KEYS_PK is (APPLICATION_ID, KEY_CODE).

Common Use Cases and Queries

Developers and integration analysts query this table to determine which keys define uniqueness for a given interface prior to loading data, and to understand how duplicate detection is configured via KEY_CLASS. A typical reporting pattern joins the interface definition to retrieve human-readable interface names while filtering by interface code:

SELECT k.APPLICATION_ID, k.KEY_CODE, k.INTERFACE_CODE, k.KEY_TYPE, k.KEY_CLASS FROM BNE.BNE_INTERFACE_KEYS k WHERE k.INTERFACE_APP_ID = :p_app_id AND k.INTERFACE_CODE = :p_code;

Another common use is auditing which applications define key policies, or resolving a duplicate-key error encountered during interface processing by tracing KEY_CLASS back to its Java implementation. Column usage analysis can be performed against BNE_INTERFACE_KEY_COLS to enumerate the individual columns that compose each logical key.

Related Objects

• BNE.BNE_INTERFACES_B — The interface definition header; joined via INTERFACE_APP_ID and INTERFACE_CODE.
• BNE.BNE_INTERFACE_KEY_COLS — Child table referencing BNE_INTERFACE_KEYS via APPLICATION_ID, listing the columns comprising each key.
• FND_APPLICATIONS — Source of APPLICATION_ID and application names.
• FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to user identities.
• FND_LOGINS — Resolves LAST_UPDATE_LOGIN to an operating-system login session.