Search Results bne_import_programs




Overview
Explore in AI Chat

Overview

BNE_IMPORT_PROGRAMS is a Web Applications Desktop Integrator (BNE) configuration table that stores the definition of multiple import programs associated with a given integrator. In Oracle EBS 12.1.1 and 12.2.2, integrators uploaded through the Desktop Integration framework frequently require more than a single import routine; this table provides the ordered, hierarchical container that maps an integrator to the sequence of programs executed during the import of uploaded spreadsheet data.

The table sits in the BNE schema and is owned by the Web Applications Desktop Integrator product. Its primary key is BNE_IMPORT_PROGRAMS_PK, defined on the composite of APPLICATION_ID, INTEGRATOR_CODE, and SEQUENCE_NUM. A unique index, BNE_IMPORT_PROGRAMS_UK1, extends this business key with the ZD_EDITION_NAME column, reflecting an edition-based redefinition (EBR) aware uniqueness rule in 12.2.2. From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning: it carries descriptive, versioned attributes about an integrator and depends on parent business entities rather than acting as an independent hub of its own identifiers.

Key Information Stored

The 14 documented columns capture both the structural identity of each import program entry and its descriptive configuration. The most significant columns are:

  • APPLICATION_ID – Identifies the Oracle application context for the integrator and forms part of the primary key.
  • INTEGRATOR_CODE – Business identifier of the parent integrator; also part of the primary key.
  • SEQUENCE_NUM – Orders the import programs within an integrator; the third component of the primary key.
  • PARENT_SEQ_NUM – Self-referencing column that establishes hierarchical/nested program relationships, enabling a tree of import steps.
  • IMPORT_TYPE – Classifies the import program behavior or execution category.
  • IMPORT_PARAM_LIST_APP_ID and IMPORT_PARAM_LIST_CODE – Reference the parameter list definition (in BNE_PARAM_LISTS_B) that supplies runtime parameters to the import program.
  • OBJECT_VERSION_NUMBER – Optimistic locking token used by the OAF/BC4J middle tier.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – Standard EBS audit columns.
  • ZD_EDITION_NAME – Editioning column supporting EBR in 12.2.2; it participates in the unique index as a business-key qualifier.

The surrogate/composite primary key is therefore distinct from the extended unique business key, which adds ZD_EDITION_NAME to the same three columns plus the sequence qualifier.

Common Use Cases and Queries

Typical scenarios involve verifying that an integrator is correctly configured to run multiple import steps in order, diagnosing failed imports, and reporting on parameter lists attached to each step. A representative query retrieves the ordered program list for a given integrator:

  • SELECT sequence_num, parent_seq_num, import_type, import_param_list_code FROM bne.bne_import_programs WHERE application_id = :app_id AND integrator_code = :code ORDER BY sequence_num;
  • Locating child programs nested under a parent: SELECT * FROM bne_import_programs WHERE parent_seq_num = :parent AND application_id = :app_id AND integrator_code = :code;
  • Cross-checking parameter lists: joining IMPORT_PARAM_LIST_APP_ID and IMPORT_PARAM_LIST_CODE to BNE_PARAM_LISTS_B to validate that each import step has a valid parameter list.
  • Auditing recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

  • BNE_INTEGRATORS_B – Parent master table; joined on APPLICATION_ID and INTEGRATOR_CODE.
  • BNE_PARAM_LISTS_B – Provides parameter list definitions; joined via IMPORT_PARAM_LIST_APP_ID and IMPORT_PARAM_LIST_CODE.
  • BNE_IMPORT_PROGRAMS (self-reference) – Uses APPLICATION_ID, INTEGRATOR_CODE, and PARENT_SEQ_NUM to model nested import program hierarchies.
  • BNE_IMPORT_PROGRAMS_PK / BNE_IMPORT_PROGRAMS_UK1 – Primary key constraint and unique index enforcing identity and business-key uniqueness.

Together these relationships establish BNE_IMPORT_PROGRAMS as the ordered, hierarchical configuration backbone that links integrators to their import programs and parameter lists within the Desktop Integrator framework.