Search Results bne_import_programs_uk1

Overview

BNE.BNE_IMPORT_PROGRAMS is a transactional configuration table within the Oracle E-Business Suite 12.1.1 / 12.2.2 application schema (BNE). It stores the definition of the multiple import programs that are available for an upload against a referenced integrator. In the E-Business Suite Integrated SOA Gateway and Business Event System architecture, this table acts as the registry that determines which concurrent or API-driven import routines are invoked when data is loaded through a given integrator interface.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than a physical implementation: the table's composite unique key of APPLICATION_ID, INTEGRATOR_CODE, and SEQUENCE_NUM reads more like a natural business key (hub-style) than a surrogate-key distribution hub. Its attributes (import type, parameter lists, parent sequence) are largely descriptive and versioned via OBJECT_VERSION_NUMBER and ZD_EDITION_NAME, which is why the classification leans toward a satellite containing descriptive, change-tracked context around an integrator/import-program relationship. Treat the classification as guidance only; the physical object remains a standard EBS relational table.

Key Information Stored

The primary key is BNE_IMPORT_PROGRAMS_PK, defined on APPLICATION_ID, INTEGRATOR_CODE, and SEQUENCE_NUM. These three columns also form the leading portion of the business-key candidate unique index BNE_IMPORT_PROGRAMS_UK1 (APPLICATION_ID, INTEGRATOR_CODE, SEQUENCE_NUM, ZD_EDITION_NAME). The most significant columns are:

• APPLICATION_ID — Application identifier; foreign key to FND_APPLICATIONS and to BNE_INTEGRATORS_B. Identifies which application owns the integrator.
• INTEGRATOR_CODE — The integrator code this import interface belongs to; the primary business identifier for the upload definition.
• SEQUENCE_NUM — Unique sequence number for the entity, allowing multiple import programs to be ordered within a single integrator.
• PARENT_SEQ_NUM — Links child import programs to a parent entry of the same integrator, supporting hierarchical import flows.
• IMPORT_TYPE — Type of import: 1 = synchronous, 2 = asynchronous, 3 = API. This governs runtime execution behavior.
• IMPORT_PARAM_LIST_APP_ID and IMPORT_PARAM_LIST_CODE — Identify the parameter list (foreign key to BNE_PARAM_LISTS_B) passed to the import program.
• OBJECT_VERSION_NUMBER — Optimistic locking/versioning column used by the framework.
• ZD_EDITION_NAME — Editioning column enabling online patching and edition-based redefinition (EBR) in 12.2.x.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard WHO columns providing audit and accountability.

The table resides in tablespace APPS_TS_TX_DATA; indexes reside in APPS_TS_TX_IDX. A secondary nonunique index, BNE_IMPORT_PROGRAMS_N1, covers the parameter list columns.

Common Use Cases and Queries

Typical uses include diagnosing why an integrator upload fails, determining which import program runs for a given integrator, and reporting on configured integration interfaces. A sample query resolves the import programs for one integrator:

• SELECT import_type, sequence_num, import_param_list_code FROM bne.bne_import_programs WHERE application_id = :app_id AND integrator_code = :code ORDER BY sequence_num;
• Join to BNE_INTEGRATORS_B on APPLICATION_ID and INTEGRATOR_CODE to obtain descriptive integrator names.
• Join to BNE_PARAM_LISTS_B on IMPORT_PARAM_LIST_APP_ID and IMPORT_PARAM_LIST_CODE to audit parameter bindings.
• Traverse PARENT_SEQ_NUM to reconstruct child ordering in multi-step import flows.

Because IMPORT_TYPE drives synchronous versus asynchronous versus API execution, this is a primary diagnostic table when investigating upload timing or commitment behavior.

Related Objects

• BNE.BNE_INTEGRATORS_B — parent integrator definition; joined on APPLICATION_ID (and INTEGRATOR_CODE).
• BNE.BNE_PARAM_LISTS_B — parameter list referenced by IMPORT_PARAM_LIST_APP_ID / IMPORT_PARAM_LIST_CODE.
• FND_APPLICATIONS — application lookup for APPLICATION_ID.
• FND_USER / FND_LOGINS — WHO-column foreign keys for CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• BNE_IMPORT_PROGRAMS — self-referencing relationship on APPLICATION_ID (and PARENT_SEQ_NUM) for hierarchical programs.

Indexes BNE_IMPORT_PROGRAMS_UK1 and BNE_IMPORT_PROGRAMS_N1, together with the BNE_IMPORT_PROGRAMS_PK constraint, complete the documented dependency surface.