Search Results bne_integrators_b_uk1




Overview

BNE.BNE_INTEGRATORS_B is the master definition table for Oracle Web Applications Desktop Integrator (Web ADI) in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row describes a complete "integrator" — a configured integration solution that bridges desktop tools such as Microsoft Word and Excel with Oracle Applications. The table represents the highest-level entity in the Web ADI data model; layouts, mappings, interfaces, import programs, and duplicate-handling profiles all hang beneath a given integrator. In a heuristic Data Vault sense the table is hub-leaning: the combination of APPLICATION_ID and INTEGRATOR_CODE forms the natural business key, while the numerous parameter, layout, and session attributes behave like descriptive satellite columns attached to that hub. The table is owned by the BNE schema and resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, with all unique and non-unique indexes placed in APPS_TS_TX_IDX. Documented physical schema for 12.2.2 lists 29 columns and records status VALID.

Key Information Stored

The primary key is BNE_INTEGRATORS_B_PK, composed of INTEGRATOR_CODE and APPLICATION_ID. The unique index BNE_INTEGRATORS_B_UK1 enforces the business key; in the 12.2.2 edition-aware schema the indexed columns are APPLICATION_ID, INTEGRATOR_CODE, and ZD_EDITION_NAME, reflecting Oracle's editioning support.

Common Use Cases and Queries

The primary diagnostic use case is resolving a user-reported Desktop Integrator failure back to its integrator definition. Because INTEGRATOR_CODE is only unique within an application, queries should always filter or join on APPLI CATION_ID as well.

  • Locate an integrator by code: SELECT * FROM bne.bne_integrators_b WHERE integrator_code = :code AND application_id = :app_id;
  • List all enabled integrators: SELECT integrator_code, application_id FROM bne.bne_integrators_b WHERE enabled_flag = 'Y';
  • Trace layouts for an integrator by joining BNE_LAYOUTS_B on INTEGRATOR_APP_ID and INTEGRATOR_CODE.
  • Audit parameter-list wiring by decoding the six *_PARAM_LIST_APP_ID / *_PARAM_LIST_CODE column pairs against FND_DESCR_FLEX_COL_USAGE or the parameter list definition tables.
  • Reporting on recent maintenance using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Related Objects

BNE_INTEGRATORS_B is referenced by several dependent tables through the INTEGRATOR_APP_ID foreign key, and it in turn references parameter-list application IDs. Significant related objects include:

  • BNE_LAYOUTS_B — Layout definitions for each integrator (INTEGRATOR_APP_ID join).
  • BNE_MAPPINGS_B — Column-to-interface mappings (INTEGRATOR_APP_ID join).
  • BNE_INTERFACES_B — Interface/API definitions invoked during upload (INTEGRATOR_APP_ID join).
  • BNE_IMPORT_PROGRAMS — Concurrent programs used for import (APPLICATION_ID join).
  • BNE_DUPLICATE_PROFILES_B — Duplicate-handling rules (INTEGRATOR_APP_ID join).
  • BNE_ASYNC_UPLOAD_JOBS — Runtime asynchronous upload records (INTEGRATOR_APP_ID join).
  • FND_APPLICATIONS — Parent application for APPLICATION_ID.