Search Results bne_integrator_viewers_pk

Overview

The BNE_INTEGRATOR_VIEWERS table is a core metadata object within the BNE (Web Applications Desktop Integrator) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Its documented purpose is the "Definition of Viewers" for integrators. In practical terms, it is an association table that maps a given integrator to one or more viewer definitions, thereby controlling which viewer applications can render or display the output produced by a particular integrator. This mapping drives the Desktop Integrator architecture that supports Web ADI, spreadsheet-based data entry, and document generation workflows.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is a link. This is a modeling suggestion only: the table sits between two hub-like parent objects (BNE_INTEGRATORS_B and BNE_VIEWERS_B) and resolves their many-to-many relationship through the composite key. It should not be treated as a transactional hub or a descriptive satellite.

Key Information Stored

The table is implemented in the BNE schema and is documented with 11 columns. The most significant columns are:

• INTEGRATOR_APP_ID – Application identifier of the integrator; part of the composite primary key and a foreign key to BNE_INTEGRATORS_B.
• INTEGRATOR_CODE – Business code identifying the integrator; the second component of the integrator-side reference.
• VIEWER_APP_ID – Application identifier of the viewer; part of the composite primary key and a foreign key to BNE_VIEWERS_B.
• VIEWER_CODE – Business code identifying the viewer definition.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE – Standard WHO audit columns recording insert user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE – Standard WHO audit columns recording the most recent modification user and timestamp.
• LAST_UPDATE_LOGIN – Login identifier associated with the last update.
• ZD_EDITION_NAME – Editioning column supporting the Online Patching / Edition-Based Redefinition model introduced in EBS 12.2.

The surrogate primary key is documented as BNE_INTEGRATOR_VIEWERS_PK, composed of INTEGRATOR_APP_ID, INTEGRATOR_CODE, VIEWER_APP_ID, and VIEWER_CODE. A unique index, BNE_INTEGRATOR_VIEWERS_UK1, extends the same four columns with ZD_EDITION_NAME, confirming the business-key candidate under the editioning model.

Common Use Cases and Queries

Typical usage centers on configuration validation and integrator/viewer dependency analysis. Administrators may query this table to determine which viewers are configured for a given integrator before running a Web ADI upload or layout generation. A representative query pattern joins the parent tables:

• Listing viewers for an integrator: SELECT iv.VIEWER_APP_ID, iv.VIEWER_CODE FROM BNE_INTEGRATOR_VIEWERS iv WHERE iv.INTEGRATOR_APP_ID = :app_id AND iv.INTEGRATOR_CODE = :code.
• Verifying integrity against parents: join to BNE_INTEGRATORS_B and BNE_VIEWERS_B on the respective APP_ID and CODE column pairs.
• Edition-aware reporting: filter or group by ZD_EDITION_NAME when comparing configurations across patched editions.
• Audit trailing: order by LAST_UPDATE_DATE to identify recently modified viewer assignments.

Related Objects

The following objects are most significant in relation to BNE_INTEGRATOR_VIEWERS, based on documented foreign-key relationships:

• BNE_INTEGRATORS_B – Referenced by INTEGRATOR_APP_ID and INTEGRATOR_CODE; the integrator definition parent.
• BNE_VIEWERS_B – Referenced by VIEWER_APP_ID and VIEWER_CODE; the viewer definition parent.
• BNE_INTEGRATOR_VIEWERS_PK – Primary key constraint enforcing uniqueness of the association.
• BNE_INTEGRATOR_VIEWERS_UK1 – Unique index extending the business key with the edition name.
• BNE_INTEGRATORS_TL – Translation table typically joined to resolve integrator display names.
• BNE_VIEWERS_TL – Translation table typically joined to resolve viewer display names.
• BNE_INTEGRATOR_VIEWERS APIs – DML against this table is generally performed through the BNE integrator configuration APIs rather than direct SQL.