Search Results bne_interfaces_b_pk

Overview

BNE_INTERFACES_B is the foundational definition table for interfaces within Oracle EBS Web Applications Desktop Integrator (BNE). Each row represents a single interface belonging to an Integrator — the logical container that groups the interface's columns, keys, layouts, mappings, and upload parameters. In the ETRM 12.2.2 schema the table resides in the BNE schema and is classified as VALID, comprising 17 documented columns. Primary key BNE_INTERFACES_B_PK is defined on (APPLICATION_ID, INTERFACE_CODE).

The heuristic Data Vault classification for this object is hub-leaning: it carries the durable business key (APPLICATION_ID, INTERFACE_CODE) that anchors interface identity and is referenced by many dependent satellites and link tables. This classification should be treated as a modeling suggestion rather than a physical constraint.

Key Information Stored

The most operationally significant columns are:

• APPLICATION_ID and INTERFACE_CODE — the composite business key and primary key; they uniquely identify an interface within an application.
• INTERFACE_NAME — the user-visible label for the interface.
• INTEGRATOR_APP_ID and INTEGRATOR_CODE — foreign key to BNE_INTEGRATORS_B, identifying the parent Integrator.
• UPLOAD_TYPE and UPLOAD_OBJ_NAME — control how data uploads are directed to the target object.
• UPLOAD_PARAM_LIST_APP_ID and UPLOAD_PARAM_LIST_CODE — reference a parameter list used during upload processing.
• UPLOAD_ORDER — sequencing for upload execution.
• OBJECT_VERSION_NUMBER — optimistic locking control for concurrent updates.
• ZD_EDITION_NAME — editioning column supporting the EBS edition-based redefinition model.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard Who columns for audit and row-level traceability.

The unique index BNE_INTERFACES_B_UK1 on (APPLICATION_ID, INTERFACE_CODE, ZD_EDITION_NAME) reinforces that the business key is unique across editions and is the strongest candidate for logical key modeling.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include enumerating all interfaces for an Integrator, tracing upload configuration, and validating that interfaces have associated columns, keys, or layouts.

• List interfaces by Integrator: SELECT interface_code, interface_name FROM bne_interfaces_b WHERE integrator_app_id = :app_id AND integrator_code = :code;
• Find interfaces missing column definitions by left-joining to BNE_INTERFACE_COLS_B on (APPLICATION_ID, INTERFACE_CODE).
• Report upload sequencing: order results by UPLOAD_ORDER within an Integrator.
• Audit recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

These patterns support Web ADI troubleshooting, integration inventory reporting, and impact analysis prior to patching interface definitions.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• BNE_INTEGRATORS_B — referenced via INTEGRATOR_APP_ID / INTEGRATOR_CODE; the parent Integrator definition.
• BNE_INTERFACE_COLS_B — child table of interface column definitions, joined on APPLICATION_ID / INTERFACE_CODE.
• BNE_INTERFACE_KEYS — child table holding interface key definitions, joined on INTERFACE_APP_ID / INTERFACE_CODE.
• BNE_LAYOUTS_B — references the interface via REPORTING_INTERFACE_APP_ID / REPORTING_INTERFACE_CODE.
• BNE_MAPPINGS_B — references the interface via REPORTING_INTERFACE_APP_ID / REPORTING_INTERFACE_CODE.
• BNE_DUP_INTERFACE_PROFILES — references the interface via INTERFACE_APP_ID / INTERFACE_CODE.
• BNE_PARAM_LISTS_B — referenced indirectly through UPLOAD_PARAM_LIST_APP_ID / UPLOAD_PARAM_LIST_CODE.

Together these objects form the interface metadata model underpinning Web ADI integration and upload processing.