Search Results bne_interfaces_b_uk1

Overview

BNE.BNE_INTERFACES_B is the definitional base table for integrator interfaces within the Oracle E-Business Suite Web ADI (Application Desktop Integrator) framework, owned by the BNE schema. An interface represents an external boundary across which data is passed during a Web ADI upload — typically an open interface table such as GL_INTERFACE for journal uploads, or a product-specific staging table. A single integrator may reference multiple interfaces, and this table records the metadata that binds each interface to its owning integrator, its physical upload mechanism, and its upload sequence.

Under the heuristic Data Vault classification supplied with the ETRM metadata, BNE_INTERFACES_B exhibits hub-leaning characteristics. Its composite business key (APPLICATION_ID, INTERFACE_CODE) is stable, non-volatile, and uniquely identifies each interface independent of descriptive attributes. A Data Vault model would therefore treat this table as the candidate hub, with the descriptive upload attributes (UPLOAD_TYPE, UPLOAD_OBJ_NAME, UPLOAD_ORDER) and the audit columns carried as satellite-like payload.

Key Information Stored

The table is defined in the APPS_TS_TX_DATA tablespace and holds seventeen documented columns. The most significant are:

• APPLICATION_ID (NUMBER, mandatory) — the application identifier, foreign key to FND_APPLICATIONS.APPLICATION_ID, and the first component of the business key.
• INTERFACE_CODE (VARCHAR2(30), mandatory) — the unique code identifying the interface for the given application; second component of the business key.
• INTERFACE_NAME (VARCHAR2(50)) — the descriptive name, frequently aligned with the underlying interface table name.
• INTEGRATOR_APP_ID and INTEGRATOR_CODE — the owning integrator's application ID and code, resolving against BNE_INTEGRATORS_B.
• UPLOAD_TYPE (NUMBER(15)) — controls upload behavior: 0 = Custom, 1 = SQL, 2 = PL/SQL, 3 = Validation only, 4 = None.
• UPLOAD_OBJ_NAME (VARCHAR2(240)) — the fully qualified Java class invoked when UPLOAD_TYPE = 0.
• UPLOAD_PARAM_LIST_APP_ID and UPLOAD_PARAM_LIST_CODE — the parameter list used to drive the upload.
• UPLOAD_ORDER (NUMBER(15)) — sequencing of this interface relative to others in the same integrator.
• OBJECT_VERSION_NUMBER — optimistic locking support.
• ZD_EDITION_NAME — editioning discriminator; part of the unique index in 12.2.x.

The surrogate primary key is BNE_INTERFACES_B_PK on (APPLICATION_ID, INTERFACE_CODE). The documented business-key candidate is the unique index BNE_INTERFACES_B_UK1 on (APPLICATION_ID, INTERFACE_CODE, ZD_EDITION_NAME) in APPS_TS_TX_IDX — this is the index users typically discover when searching for "bne_interfaces_b_uk1". Two non-unique indexes, BNE_INTERFACES_B_N1 (INTEGRATOR_APP_ID, INTEGRATOR_CODE) and BNE_INTERFACES_B_N2 (UPLOAD_PARAM_LIST_APP_ID, UPLOAD_PARAM_LIST_CODE), support integrator-driven and parameter-list-driven lookups respectively. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE) are also present.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios revolve around determining which interfaces exist for an integrator, which upload mechanism each uses, and the intended upload sequence.

• Listing interfaces for an integrator by code:

  SELECT interface_code, interface_name, upload_type, upload_order
  FROM   bne.bne_interfaces_b
  WHERE  integrator_code = :p_code
  ORDER BY upload_order;

• Validating upload mechanism distribution — identifying custom (UPLOAD_TYPE = 0) interfaces that require a Java class:

  SELECT application_id, interface_code, upload_obj_name
  FROM   bne.bne_interfaces_b
  WHERE  upload_type = 0;

• Confirming uniqueness and editioning behavior of the business key:

  SELECT interface_code, zd_edition_name
  FROM   bne.bne_interfaces_b
  WHERE  application_id = :app_id;

• Reconciling a parameter list across interfaces sharing UPLOAD_PARAM_LIST_CODE, leveraging index N2.

These queries are commonly executed during Web ADI integrator troubleshooting, pre-upgrade impact analysis of open interface tables, and documentation of custom integrator configurations.

Related Objects

BNE_INTERFACES_B participates in a hub-and-spoke relationship with several Web ADI definition tables:

• BNE.BNE_INTEGRATORS_B — referenced via INTEGRATOR_APP_ID; the parent integrator definition.
• BNE.BNE_INTERFACE_COLS_B — child table keyed by APPLICATION_ID; defines the columns exposed for each interface.
• BNE.BNE_INTERFACE_KEYS — child table via INTERFACE_APP_ID; defines interface key columns.
• BNE.BNE_MAPPINGS_B — references REPORTING_INTERFACE_APP_ID; maps interface columns to layout targets.
• BNE.BNE_LAYOUTS_B — references REPORTING_INTERFACE_APP_ID; layout definitions aligned to an interface.
• BNE.BNE_DUP_INTERFACE_PROFILES — references INTERFACE_APP_ID; duplicate-handling profiles per interface.
• FND_APPLICATIONS — provides the application name resolved from APPLICATION_ID.