Results for “bne_content_cols_b_pk”

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

Overview

BNE_CONTENT_COLS_B is a base table in the BNE schema, owned by the Web Applications Desktop Integrator (BNE) product module. It stores the definition of Content Component columns, meaning each row describes a single column that belongs to a Content Component within the BNE content framework. Content Components are the reusable definitions that drive desktop integration layouts, Web ADI integrators, and related mapping structures in Oracle E-Business Suite 12.1.1 and 12.2.2.

The table exhibits a dependent, attribute-bearing structure anchored to BNE_CONTENTS_B. Heuristically, this suggests a satellite-leaning Data Vault classification: BNE_CONTENT_COLS_B records descriptive attributes (column names, sequence, read-only behavior) that hang off a parent content definition, rather than acting as an independent hub or a pure many-to-many link. The composite primary key BNE_CONTENT_COLS_B_PK (APPLICATION_ID, CONTENT_CODE, SEQUENCE_NUM) confirms that a content component's columns are uniquely identified together with their parent content identifier.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• APPLICATION_ID — Identifies the application context and forms part of the primary key and foreign key to BNE_CONTENTS_B.
• CONTENT_CODE — The content component code; jointly with APPLICATION_ID it ties each column to its parent content definition.
• SEQUENCE_NUM — Ordinal position of the column within the content component, completing the primary key.
• COL_NAME — The name of the content component column; participates in the unique index BNE_CONTENT_COLS_B_UK2.
• READ_ONLY_FLAG — Indicates whether the column is display-only within the integrator layout.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the BNE framework for concurrent update control.
• ZD_EDITION_NAME — Edition-based redefinition column enabling online patching; part of the business-key candidate index BNE_CONTENT_COLS_B_UK2.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard WHO audit columns tracking creation and modification.

The surrogate-style primary key is the composite (APPLICATION_ID, CONTENT_CODE, SEQUENCE_NUM). The documented unique index BNE_CONTENT_COLS_B_UK2 (APPLICATION_ID, CONTENT_CODE, COL_NAME, ZD_EDITION_NAME) represents a business-key candidate, ensuring a column name is not duplicated within the same content component for a given edition.

Common Use Cases and Queries

Typical scenarios include auditing the column layout of a Web ADI integrator, verifying read-only columns exposed to end users, and joining column definitions to their mappings. A representative query lists all columns for a content component in display order:

• SELECT sequence_num, col_name, read_only_flag FROM bne.bne_content_cols_b WHERE application_id = :app_id AND content_code = :code ORDER BY sequence_num;
• Reporting joins BNE_CONTENT_COLS_B to BNE_MAPPING_LINES on CONTENT_APP_ID, CONTENT_CODE, and CONTENT_SEQ_NUM to reconcile columns with their mapping targets.
• Edition-aware queries should filter on ZD_EDITION_NAME to align with the current edition when running under online patching in 12.2.2.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• BNE_CONTENTS_B — Parent table; joined via APPLICATION_ID and CONTENT_CODE.
• BNE_MAPPING_LINES — References this table through CONTENT_APP_ID, CONTENT_CODE, and CONTENT_SEQ_NUM.
• BNE_CONTENT_COLS_B_PK — Primary key constraint enforcing uniqueness of (APPLICATION_ID, CONTENT_CODE, SEQUENCE_NUM).
• BNE_CONTENT_COLS_B_UK2 — Unique index supporting business-key and edition validation.