Results for “content_class”

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

Overview

BNE_CONTENTS_B is a core configuration table within the BNE (Web Applications Desktop Integrator) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the definition of Content Components — the logical building blocks that make up the content published to desktop-integrated spreadsheets, such as Oracle Web ADI, Web ADI integrators, and the associated parameter and column definitions consumed during document generation.

Each row represents a content definition scoped to a specific application, identified by the combination of APPLICATION_ID and CONTENT_CODE. The table acts as a parent or header record that downstream detail objects, most notably BNE_CONTENT_COLS_B, reference for their column layouts. It also maintains self-referencing relationships to integrators and parameter lists, enabling a content definition to inherit behavior from an integrator and a named parameter list.

With respect to Data Vault modeling, the mined foreign key structure suggests this table is satellite-leaning. In practice this means BNE_CONTENTS_B behaves more like a descriptive, attribute-bearing structure that hangs off a business key (APPLICATION_ID plus CONTENT_CODE) rather than acting as a pure hub or a pure link. This is offered as a heuristic modeling suggestion rather than a documented Data Vault classification.

Key Information Stored

The table is documented with 15 physical columns in the 12.2.2 ETRM schema, owned by BNE. The most significant columns are:

• APPLICATION_ID and CONTENT_CODE — together these form the business key of the table. They are the components of the unique index BNE_CONTENTS_B_UK1 and also part of the primary key.
• CONTENT_CLASS — indicates the classification or category of the content component, driving how the content is rendered or consumed.
• INTEGRATOR_APP_ID and INTEGRATOR_CODE — identify the integrator associated with the content definition, forming a foreign key to the parent integrator record.
• PARAM_LIST_APP_ID and PARAM_LIST_CODE — identify the parameter list used by the content, forming a second foreign key reference.
• ONCE_ONLY_DOWNLOAD_FLAG — controls whether the content may be downloaded only once, governing refresh and re-download behavior.
• OBJECT_VERSION_NUMBER — supports optimistic locking and change detection.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard EBS audit columns that record who created and last modified the row and when.

The documented surrogate primary key is BNE_CONTENT_B_PK over (APPLICATION_ID, CONTENT_CODE). The unique index BNE_CONTENTS_B_UK1 spans (APPLICATION_ID, CONTENT_CODE, ZD_EDITION_NAME), which introduces ZD_EDITION_NAME as a third business-key candidate — relevant where edition-based redefinition or multi-edition data is present.

Common Use Cases and Queries

BNE_CONTENTS_B is queried primarily during troubleshooting and auditing of Web ADI content definitions. Typical scenarios include identifying which integrator and parameter list a given content uses, and auditing when content definitions were last changed.

A representative query joins the content header to its column definitions:

• SELECT c.application_id, c.content_code, c.content_class, cc.column_name FROM bne_contents_b c JOIN bne_content_cols_b cc ON cc.application_id = c.application_id AND cc.content_code = c.content_code;
• SELECT application_id, content_code, integrator_code, param_list_code, once_only_download_flag FROM bne_contents_b WHERE application_id = :app_id;
• SELECT content_code, last_update_date, last_updated_by FROM bne_contents_b WHERE last_update_date > SYSDATE - 30;

Reporting use cases include inventorying all content components per application and reconciling integrator-to-content mappings. Because the table is a definition or setup table, it is generally read-only in production and should not be updated outside of supported Web ADI configuration flows.

Related Objects

The following objects are most significant in relation to BNE_CONTENTS_B:

• BNE_CONTENT_COLS_B — the primary dependent detail table; it references BNE_CONTENTS_B via (APPLICATION_ID, CONTENT_CODE) and holds the column-level definition for each content component.
• BNE_CONTENTS_B (self-reference) — references its own INTEGRATOR_APP_ID/INTEGRATOR_CODE and PARAM_LIST_APP_ID/PARAM_LIST_CODE, establishing parent-child content relationships within the same table.
• BNE_INTEGRATORS / integrator definitions — referenced through INTEGRATOR_APP_ID and INTEGRATOR_CODE.
• BNE_PARAM_LISTS / parameter list definitions — referenced through PARAM_LIST_APP_ID and PARAM_LIST_CODE.

Any customization, extraction, or report referencing Web ADI content should account for the parent-child link to BNE_CONTENT_COLS_B and for the edition column ZD_EDITION_NAME where applicable.