Results for “bne_stylesheets_b_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BNE_STYLESHEETS_B is a core configuration table within the BNE schema (Web Applications Desktop Integrator, commonly known as Web ADI or ADI) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of a collection of stylesheets — logical groupings of layout and formatting attributes used by Desktop Integrator to render spreadsheet-based integrators, journals, and upload templates consistently. Each row represents one stylesheet definition, scoped by application, and serves as the header record for the broader stylesheet configuration model.

Under a heuristic Data Vault classification mined from the foreign key structure, this object is assessed as standalone. No dependent FK relationships were identified, which suggests the table operates as an independent reference of style definitions rather than as a transactional hub or link. Practically, this means it is best treated as a reference/definition table that other BNE objects consume by code value rather than through enforced referential integrity.

Key Information Stored

The table carries 12 documented columns. The most operationally significant are:

• APPLICATION_ID — the owning Oracle application, part of both the primary key and the unique business key; it scopes stylesheet codes to a product/application context.
• STYLESHEET_CODE — the human-readable identifier for the stylesheet definition; also part of the PK and UK.
• ZD_EDITION_NAME — the edition (data-vault style) discriminator, completing the unique index BNE_STYLESHEETS_B_UK1.
• DEFAULT_FLAG — indicates whether this stylesheet is the default used when no explicit style is chosen.
• READ_ONLY_FLAG — controls whether the stylesheet may be modified by end users or is locked for system use.
• IMAGE_FILE_NAME — the associated image/preview file rendered in the Desktop Integrator UI.
• OBJECT_VERSION_NUMBER — optimistic locking/versioning column used by the OAF/BC4J framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard EBS WHO (Who columns) audit trail fields.

The surrogate primary key is BNE_STYLESHEETS_B_PK (APPLICATION_ID, STYLESHEET_CODE). The unique index BNE_STYLESHEETS_B_UK1 (APPLICATION_ID, STYLESHEET_CODE, ZD_EDITION_NAME) is the business-key candidate, adding the edition name to the PK columns.

Common Use Cases and Queries

Typical scenarios include auditing which stylesheets are configured per application, identifying the default stylesheet, and validating that codes are unique within an application. A reporting query to list active definitions:

• SELECT application_id, stylesheet_code, default_flag, read_only_flag, image_file_name FROM bne.bne_stylesheets_b WHERE default_flag = 'Y';
• SELECT a.application_name, s.stylesheet_code, s.default_flag FROM bne.bne_stylesheets_b s, fnd_application_vl a WHERE s.application_id = a.application_id ORDER BY a.application_name, s.stylesheet_code;
• SELECT stylesheet_code, COUNT(*) FROM bne.bne_stylesheets_b GROUP BY stylesheet_code HAVING COUNT(*) > 1; — used to detect cross-application duplicate codes.

Because the object is standalone, joins to related BNE stylesheet attribute tables are driven by APPLICATION_ID and STYLESHEET_CODE rather than enforced FK constraints.

Related Objects

The following objects are most relevant to BNE_STYLESHEETS_B, joined on the composite key columns APPLICATION_ID and STYLESHEET_CODE:

• BNE_STYLESHEET_COLS / BNE_STYLESHEETS_TL — the child/translated definition tables that reference the stylesheet by code.
• BNE_LAYOUTS_B — layouts that bind to a stylesheet for rendering.
• BNE_INTEGRATORS_B — integrator definitions that consume stylesheets during upload/download.
• BNE_CONTENT_COLS_B — content/column metadata associated with a stylesheet.
• FND_APPLICATION / FND_APPLICATION_VL — source of the APPLICATION_ID and application name for reporting.
• FND_STYLESHEET / Desktop Integrator setup APIs — the configuration and generation routines that read stylesheet definitions.

These relationships are logical rather than FK-enforced, consistent with the standalone classification.