Search Results ibe_section_search_part




Overview
Explore in AI Chat

Overview

IBE_SECTION_SEARCH_PART is a table within the IBE (iStore) product module of Oracle E-Business Suite, owned by the IBE schema. It stores the associations that map inventory items, per organization, to the iStore sections in which they participate in search results and section-level browsing. In practical terms, the table functions as the intersection that determines which catalog items appear within a given store section for a given minisite and organization, supporting the storefront navigation and search experience delivered by iStore.

From a heuristic Data Vault modeling perspective, the ETRM metadata classifies this object as standalone, meaning no incoming foreign-key dependencies were mined from the FK structure. The business-key candidate unique index IBE_SECTION_SEARCH_PART_U1 (INVENTORY_ITEM_ID, ORGANIZATION_ID, SECTION_ID, MINISITE_ID) suggests a natural composite key that behaves more like a link-style relationship between item, organization, section, and minisite dimensions rather than a pure hub. This classification should be treated as a modeling suggestion derived from the documented constraints, not as an authoritative Data Vault design.

Key Information Stored

The documented physical schema at ETRM 12.2.2 contains 11 columns. The most significant columns are:

  • INVENTORY_ITEM_ID — identifies the inventory item associated with the section search relationship; part of the unique business key.
  • ORGANIZATION_ID — the inventory organization context under which the item qualifies; part of the unique business key.
  • SECTION_ID — the iStore section to which the item is assigned for search/display; part of the unique business key.
  • MINISITE_ID — the minisite (storefront site) in which the section assignment applies; part of the unique business key.
  • OBJECT_VERSION_NUMBER — optimistic locking/versioning column used by the Oracle Applications framework.
  • SECURITY_GROUP_ID — the security group that governs row-level access; documented as a foreign key to FND_SECURITY_GROUPS.
  • CREATED_BY, CREATION_DATE — standard audit columns capturing who created the row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the last modification context.

The metadata does not document a separate surrogate primary key column beyond the composite business-key candidate IBE_SECTION_SEARCH_PART_U1. Where a surrogate identifier is expected by convention, the unique index columns collectively serve as the row identifier in the documented schema.

Common Use Cases and Queries

Typical usage involves determining which items are exposed within a section for a storefront, and reporting on catalog coverage. A representative query joining the section search partition to item and section metadata is:

  • Filtering by MINISITE_ID and SECTION_ID to list all items presented in a storefront section for a given ORGANIZATION_ID.
  • Validating coverage gaps by comparing IBE_SECTION_SEARCH_PART entries against the full item master for an organization.
  • Auditing changes using LAST_UPDATED_BY and LAST_UPDATE_DATE to trace who altered section-to-item mappings.
  • Enforcing access control checks by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.
  • Detecting duplicate or conflicting assignments using the composite of INVENTORY_ITEM_ID, ORGANIZATION_ID, SECTION_ID, and MINISITE_ID.

Because the table is tightly coupled to the storefront presentation layer, queries are frequently combined with the parent section and minisite definitions to reconstruct the catalog hierarchy.

Related Objects

The documented relationship data identifies a single foreign key:

  • FND_SECURITY_GROUPS — referenced via IBE_SECTION_SEARCH_PART.SECURITY_GROUP_ID; supplies the security group definition governing row access.

Beyond the documented FK, functional dependencies typically include iStore section and minisite definition tables (referenced through SECTION_ID and MINISITE_ID), the inventory item and organization definitions (through INVENTORY_ITEM_ID and ORGANIZATION_ID), and the standard Oracle Applications audit/security infrastructure. The ETRM metadata for this object is limited to schema and FK facts; additional join targets should be confirmed against the deployed IBE schema before use in production queries.