Results for “ibe_section_search”

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

Overview

The IBE_SECTION_SEARCH table is an Oracle E-Business Suite iStore (IBE) repository object that governs which inventory items are searchable within specific storefront sections. In EBS releases 12.1.1 and 12.2.2, the table acts as an intersection between the merchandise catalog hierarchy (sections and mini-sites) and the item master, allowing administrators to constrain search results to a defined set of sections rather than exposing the entire item catalog to a given storefront context. It resides in the IBE schema and is classified as VALID in the data dictionary.

Under a heuristic Data Vault classification inferred from its foreign key structure, IBE_SECTION_SEARCH is best modeled as a link table. It carries no descriptive attributes beyond audit and versioning columns; instead, it resolves the many-to-many relationship between items and storefront sections within a mini-site and organization context. This modeling suggestion aligns with the fact that every meaningful column in the table participates in a foreign key or a composite unique key.

Key Information Stored

The table contains eleven documented columns. The most significant are the four that form the composite unique key and the business identity of each record:

• INVENTORY_ITEM_ID — Foreign key to MTL_SYSTEM_ITEMS_B, identifying the item eligible for section-restricted search.
• ORGANIZATION_ID — The inventory organization context in which the item is valid; part of the composite key to MTL_SYSTEM_ITEMS_B.
• SECTION_ID — Foreign key to IBE_DSP_SECTIONS_B, identifying the storefront section to which the item is bound for search purposes.
• MINISITE_ID — Foreign key to IBE_MSITES_B, scoping the association to a specific mini-site.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the iStore framework during concurrent updates.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing row-level data security in multi-tenant deployments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns providing audit lineage and supporting concurrent program diagnostics.

Two unique indexes are documented. IBE_SECTION_SEARCH_UK1 (INVENTORY_ITEM_ID, MINISITE_ID, ORGANIZATION_ID, SECTION_ID) is designated the primary key, while IBE_SECTION_SEARCH_U1 (INVENTORY_ITEM_ID, ORGANIZATION_ID, SECTION_ID, MINISITE_ID) represents the same attribute set in a different column order and serves as the business-key candidate. There is no separate surrogate primary key column; the composite business key is the identity.

Common Use Cases and Queries

Typical use cases revolve around storefront search configuration and diagnostics. Administrators verify which items are indexed for a given section, reconcile section assignments after catalog refreshes, and audit security group isolation across mini-sites.

A representative query listing items restricted to a section:

• SELECT s.section_id, s.minisite_id, s.organization_id, s.inventory_item_id FROM ibe.ibe_section_search s WHERE s.minisite_id = :p_minisite AND s.section_id = :p_section;

To detect items referenced by a section that no longer exist in the item master:

• SELECT s.* FROM ibe.ibe_section_search s WHERE NOT EXISTS (SELECT 1 FROM mtl_system_items_b m WHERE m.inventory_item_id = s.inventory_item_id AND m.organization_id = s.organization_id);

Reporting queries commonly join to IBE_DSP_SECTIONS_B to obtain section display names and to IBE_MSITES_B for mini-site identification. Because the table lacks descriptive columns, it is almost always consumed through joins rather than queried in isolation.

Related Objects

• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID; supplies item number, description, and status.
• IBE_DSP_SECTIONS_B — joined on SECTION_ID; provides section names and storefront structure.
• IBE_MSITES_B — joined on MINISITE_ID; defines the mini-site scope.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; enforces data security.
• IBE_SECTION_SEARCH_UK1 / IBE_SECTION_SEARCH_U1 — unique indexes supporting key lookups and preventing duplicate item/section associations.
• MTL_SYSTEM_ITEMS_VL / MTL_SYSTEM_ITEMS_KFV — commonly substituted for the base table in reporting views to obtain translated item information.