Results for “parent_section_id”

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

Overview

The IBE_DSP_MSITE_SCT_SECTS table is an iStore (IBE) module object within the Oracle E-Business Suite 12.1.1 and 12.2.2 schema. It stores the association between mini-sites and the sections that belong to them, effectively functioning as the mapping layer that binds a publishing mini-site to the content sections rendered within it. Because a section may appear in more than one mini-site and a mini-site may contain many sections, the table carries both a primary surrogate identifier and several composite unique indexes that enforce the business rules governing those associations, including parent-to-child nesting of sections inside a mini-site context.

From a Data Vault modeling perspective, the mined FK structure classifies this table heuristically as a link. This is consistent with its role: it is not a hub of unique business entities but a relationship object connecting independent keys — IBE_MSITES_B and IBE_DSP_SECTIONS_B — through the columns MINI_SITE_ID, PARENT_SECTION_ID, and CHILD_SECTION_ID.

Key Information Stored

The physical schema documents 17 columns. The most significant are the following:

• MINI_SITE_SECTION_SECTION_ID — the surrogate primary key column defined by the constraint IBE_DSP_MSITE_SCT_SECTS_PK, and the anchor of the first unique index IBE_DSP_MSITE_SCT_SECTS_U1 (paired with ZD_EDITION_NAME).
• MINI_SITE_ID — the foreign key referencing IBE_MSITES_B; it identifies which mini-site the section association belongs to.
• PARENT_SECTION_ID and CHILD_SECTION_ID — both foreign keys to IBE_DSP_SECTIONS_B, expressing the hierarchical relationship between a parent section and its child section within the mini-site.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, implementing the multi-tenant style access restriction used throughout EBS iStore.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating pair controlling when a mini-site/section association becomes visible and when it expires.
• LEVEL_NUMBER and SORT_ORDER — control the nesting depth and the display sequence of sections in the rendered mini-site.
• CONCAT_IDS — a materialized concatenation of the section identifier path, typically used to simplify recursive traversal of the section hierarchy.
• ZD_EDITION_NAME — the editioning column required by the EBS online patching model (12.2.x); it participates in all three unique indexes U1, U2, and U3.
• The standard who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER provide audit and optimistic-locking metadata.

The three unique indexes — U1 on (MINI_SITE_SECTION_SECTION_ID, ZD_EDITION_NAME), U2 on (MINI_SITE_ID, PARENT_SECTION_ID, CHILD_SECTION_ID, ZD_EDITION_NAME), and U3 on (CHILD_SECTION_ID, MINI_SITE_ID, ZD_EDITION_NAME) — represent the documented business-key candidates that govern valid combinations of mini-site, parent, and child sections.

Common Use Cases and Queries

Typical usage includes resolving which sections appear in a given mini-site, reconstructing the section tree for a storefront, and filtering out associations that fall outside their effective dates. A representative query joining the association to the section definition is:

SELECT m.MINI_SITE_ID, m.PARENT_SECTION_ID, m.CHILD_SECTION_ID, m.LEVEL_NUMBER, m.SORT_ORDER
FROM IBE.IBE_DSP_MSITE_SCT_SECTS m
WHERE m.MINI_SITE_ID = :p_mini_site_id
AND SYSDATE BETWEEN m.START_DATE_ACTIVE AND NVL(m.END_DATE_ACTIVE, SYSDATE+1)
ORDER BY m.LEVEL_NUMBER, m.SORT_ORDER;

Reporting scenarios include auditing which sections are shared across multiple mini-sites, validating section hierarchy integrity, and checking effective-dating overlaps. These queries are typically restricted by SECURITY_GROUP_ID to honor the iStore security model.

Related Objects

• IBE_MSITES_B — joined on IBE_DSP_MSITE_SCT_SECTS.MINI_SITE_ID = IBE_MSITES_B.MINI_SITE_ID; defines the hosting mini-site.
• IBE_DSP_SECTIONS_B — joined twice, on PARENT_SECTION_ID and on CHILD_SECTION_ID, to retrieve parent and child section definitions.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to enforce access partitioning.
• IBE_DSP_MSITE_SCT_SECTS_PK / U1 / U2 / U3 — the primary key and three unique indexes that constrain and support query access paths on this table.