Results for “ibe_dsp_msite_sct_items”

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

Overview

IBE_DSP_MSITE_SCT_ITEMS is an iStore (IBE) application table that stores the association between mini-sites and the section items displayed within them. In the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, iStore mini-sites are targeted storefronts assembled from reusable content sections and merchandising items. This table functions as the junction that binds a given mini-site to a specific section item, controlling what merchandise or content appears on that storefront and during which active window. Because it resolves a many-to-many relationship between two substantive entities, the metadata’s heuristic Data Vault classification of link is appropriate: the table is best modeled as a link between the mini-site hub and the section-item hub, carrying its own descriptive and audit attributes.

Key Information Stored

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

• MINI_SITE_SECTION_ITEM_ID — surrogate primary key of the table (IBE_DSP_MSITE_SCT_ITEMS_PK) and the leading column of unique index IBE_DSP_MSITE_SCT_ITEMS_U1.
• MINI_SITE_ID — foreign key to IBE_MSITES_B; identifies the mini-site to which the item association belongs.
• SECTION_ITEM_ID — foreign key to IBE_DSP_SECTION_ITEMS; identifies the reusable section item being placed on the mini-site.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating window that determines when the association is live on the storefront.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-organization/security-group data partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework (OAF) and the iStore business object layer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording insert and update provenance.

The business-key candidate is documented through unique index IBE_DSP_MSITE_SCT_ITEMS_U2 on (SECTION_ITEM_ID, MINI_SITE_ID), which prevents the same section item from being assigned to the same mini-site more than once. Note that the published primary key naming references MINI_SITE_SECTION_ITEM_ID while the alternate index U1 is documented on the same column; the surrogate key should be treated as the technical identifier and U2 as the logical uniqueness constraint.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios include determining which section items are published on a given mini-site, auditing assignment history, and verifying active-date windows. A representative join is:

• SELECT m.mini_site_id, m.section_item_id, m.start_date_active, m.end_date_active FROM ibe.ibe_dsp_msite_sct_items m WHERE m.mini_site_id = :p_mini_site_id AND TRUNC(SYSDATE) BETWEEN m.start_date_active AND NVL(m.end_date_active, TRUNC(SYSDATE)+1);
• Resolving the section item definition: SELECT * FROM ibe.ibe_dsp_section_items si, ibe.ibe_dsp_msite_sct_items m WHERE si.section_item_id = m.section_item_id AND m.mini_site_id = :p_mini_site_id;
• Resolving the storefront: join MINI_SITE_ID to IBE_MSITES_B for mini-site name and context information.
• Audit queries leveraging CREATED_BY/LAST_UPDATED_BY to identify who added or changed a mini-site item assignment.

Related Objects

• IBE_DSP_SECTION_ITEMS — referenced via SECTION_ITEM_ID; the item definitions that can be placed on mini-sites.
• IBE_MSITES_B — referenced via MINI_SITE_ID; the mini-site base entity.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs data security partitioning.
• IBE_DSP_MSITE_SCT_ITEMS_PK / U1 / U2 — the primary key and unique indexes enforcing identity and uniqueness.
• iStore administrative UI and OAF-based mini-site management pages that maintain these associations and rely on OBJECT_VERSION_NUMBER for concurrency control.