Search Results bne_viewers_b_pk

Overview

BNE_VIEWERS_B is a core configuration table in the BNE schema (Web Applications Desktop Integrator, commonly known as Web ADI) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of "viewers" — the integration components that render and display data within the Web ADI desktop framework, driving how spreadsheet-based integrations present their content. Each row defines a specific viewer, identified by a viewer code and the application context in which it is registered.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object is best treated as a link table. It resolves relationships between viewers and the parameter lists that govern their behavior, rather than functioning as a pure reference hub or a transactional satellite. This classification is a heuristic derived from the FK topology and should be validated against the actual integration design before being adopted in any downstream model.

Key Information Stored

The primary key, BNE_VIEWERS_B_PK, is a composite surrogate key over (VIEWER_CODE, APPLICATION_ID). A second unique index, BNE_VIEWERS_B_UK1, spans (APPLICATION_ID, VIEWER_CODE, ZD_EDITION_NAME), making it the strongest documented business-key candidate and confirming that edition awareness is built into the identity of a viewer record. The table holds fifteen physical columns; the most operationally significant include:

• VIEWER_CODE — the functional identifier for each viewer; together with APPLICATION_ID it forms the natural key.
• APPLICATION_ID — the owning application context, scoping viewers per product.
• VIEWER_JAVA_CLASS — the Java implementation class invoked to render or process the viewer at runtime; the core behavioral attribute.
• PARAM_LIST_APP_ID / PARAM_LIST_CODE — the foreign key to BNE_PARAM_LISTS_B, defining the parameter list that configures the viewer.
• CREATE_DOC_LIST_APP_ID / CREATE_DOC_LIST_CODE — a second FK to BNE_PARAM_LISTS_B, governing document-creation behavior.
• ENABLED_FLAG — controls whether the viewer is active and selectable.
• OBJECT_VERSION_NUMBER — optimistic locking for concurrent modifications.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-columns for audit and change tracking.
• ZD_EDITION_NAME — edition identifier supporting the Editions-based redefinition architecture introduced in 12.2.x.

Common Use Cases and Queries

Administrators and developers query BNE_VIEWERS_B to audit which viewers are registered, determine the Java classes driving them, and trace parameter-list dependencies. A typical listing filters enabled viewers by application:

• Inventory enabled viewers: SELECT APPLICATION_ID, VIEWER_CODE, VIEWER_JAVA_CLASS FROM BNE_VIEWERS_B WHERE ENABLED_FLAG = 'Y';
• Parameter-list traceability: join PARAM_LIST_CODE back to BNE_PARAM_LISTS_B to see viewer configuration sources.
• Change auditing: order by LAST_UPDATE_DATE to identify recently modified viewer definitions.
• Edition-aware reporting in 12.2.2: filter on ZD_EDITION_NAME to isolate the active edition.

Related Objects

BNE_VIEWERS_B is tightly coupled to the BNE parameter framework and broader Web ADI integration objects. The primary dependencies are the two documented foreign keys into BNE_PARAM_LISTS_B (via PARAM_LIST_APP_ID/PARAM_LIST_CODE and CREATE_DOC_LIST_APP_ID/CREATE_DOC_LIST_CODE), which supply the parameter definitions consumed by each viewer. Its unique index BNE_VIEWERS_B_UK1 interacts with edition handling shared across BNE configuration tables. Practically, it is queried alongside other BNE_PARAM_LISTS_B-family objects that define parameters, integrators, and layouts, since a viewer cannot function without its associated parameter list.