Search Results bne_interface_key_cols_pk

Overview

BNE_INTERFACE_KEY_COLS is a reference definition table residing 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 logical key columns that participate in composite business keys used by Web ADI interfaces. When an interface is registered in the BNE framework, its logical key is composed of one or more interface columns that uniquely identify a row during upload, download, and validation processing. This table records which columns belong to each logical key and in what order they appear. As a definition/association table linking interface keys to interface columns, a Data Vault modeling exercise would most naturally classify it as a link table, capturing the relationship between a key definition and its constituent interface columns.

Key Information Stored

The physical table in 12.2.2 contains 13 documented columns. The most significant are listed below.

• APPLICATION_ID — Identifies the owning application; part of the composite primary key and a foreign key to BNE_INTERFACE_KEYS.
• KEY_CODE — The logical key identifier; part of the primary key and foreign key to BNE_INTERFACE_KEYS.
• SEQUENCE_NUM — Ordinal position of the column within the logical key; third component of the primary key.
• INTERFACE_APP_ID — Application associated with the referenced interface column; foreign key to BNE_INTERFACE_COLS_B.
• INTERFACE_CODE — Code of the interface column bound to this key position.
• INTERFACE_SEQ_NUM — Sequence number of the referenced interface column.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework.
• ZD_EDITION_NAME — Editioning column participating in the unique index for edition-aware queries.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard who-column audit tracking.

The surrogate primary key is BNE_INTERFACE_KEY_COLS_PK, defined on (APPLICATION_ID, KEY_CODE, SEQUENCE_NUM). A unique index, BNE_INTERFACE_KEY_COLS_UK1, extends those three columns with ZD_EDITION_NAME and serves as the business-key candidate under editioning.

Common Use Cases and Queries

Typical uses involve introspection of key definitions during interface design, debugging upload failures caused by key mismatches, and metadata reporting for integration governance.

• List all columns forming a given logical key, in order:

  SELECT k.key_code, k.sequence_num, c.column_name
  FROM   bne_interface_key_cols k,
         bne_interface_cols_b      c
  WHERE  k.application_id    = :app_id
  AND    k.key_code          = :key_code
  AND    c.interface_app_id  = k.interface_app_id
  AND    c.interface_code    = k.interface_code
  ORDER BY k.sequence_num;

• Identify duplicate or mis-sequenced key definitions for a set of interfaces.
• Audit population by who-columns to determine when a key definition was last changed.
• Feed downstream integration metadata catalogs and data-quality tooling.

Related Objects

• BNE_INTERFACE_KEYS — Parent table; joined on APPLICATION_ID and KEY_CODE.
• BNE_INTERFACE_COLS_B — Base interface column table; joined on INTERFACE_APP_ID, INTERFACE_CODE, and INTERFACE_SEQ_NUM.
• BNE_INTERFACE_COLS_TL — Translation of interface column names, referenced via the _B/_TL pattern.
• BNE_INTERFACES_B — Interface registration; supplies the interface context for the key.
• BNE_INTERFACE_KEY_COLS_PK and BNE_INTERFACE_KEY_COLS_UK1 — Primary and unique indexes enforcing key integrity.
• Web ADI interface registration and layout APIs that consume key-column metadata at runtime.

Together, these objects form the metadata backbone that Web ADI uses to translate logical business keys into concrete interface columns during integration processing.