Results for “ibe_section_search_part_u1”

16 results




Overview
Explore in AI Chat

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

Overview

IBE.IBE_SECTION_SEARCH_PART is a VALID table in the Oracle E-Business Suite iStore/IBE schema. It records the association between an inventory item (in a specific organization) and the "section" in which that item is searchable or displayable within an iStore minisite. In practical terms, it acts as a mapping table that drives which products appear in which storefront sections, and confirms the item's participation in section-level search or browse behavior. It is a child of the broader iStore content model, where sections and minisites are content containers, and inventory items are catalog products surfaced into those containers.

Based on the FK/PK relationship data supplied, the table is classified heuristically as standalone within a Data Vault modeling suggestion. That is, it does not act as a hub or a link to other IBE catalog objects through declared foreign keys; it holds its own descriptive/association rows. Only a single relationship is documented: SECURITY_GROUP_ID references FND_SECURITY_GROUPS, which is a standard Oracle Applications security/group construct rather than a business catalog parent. The 11 documented columns include the business-identifying keys plus the standard EBS WHO columns.

Key Information Stored

The table's identity and business meaning are carried mainly by four columns, which together form the unique index IBE_SECTION_SEARCH_PART_U1:

  • INVENTORY_ITEM_ID — the item (product) being placed into a searchable section; a core foreign key to the item master in most EBS contexts.
  • ORGANIZATION_ID — the inventory organization context in which the item is valid, allowing the same item to be sectioned differently per organization.
  • SECTION_ID — identifies the iStore section (content grouping) to which the item is assigned.
  • MINISITE_ID — identifies the iStore minisite (storefront) in which the section and item assignment applies.

The surrogate primary key is IBE_SECTION_SEARCH_PART_PK, whose documented definition is the same four columns (INVENTORY_ITEM_ID, ORGANIZATION_ID, SECTION_ID, MINISITE_ID), and the unique index IBE_SECTION_SEARCH_PART_U1 is documented as UNIQUE/NORMAL over exactly those four columns. The distinction between "surrogate PK" and "business-key candidate" is therefore not one of different columns here: the same composite defines both the PK and the unique constraint. Around that key the table stores audit and control columns: OBJECT_VERSION_NUMBER (optimistic locking / versioning), CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and SECURITY_GROUP_ID. No mandatory flags are documented in the excerpt.

Common Use Cases and Queries

Typical scenarios include confirming which sections an item belongs to, ensuring an item is searchable in a given minisite, and auditing section population for a storefront. The canonical retrieval query is:

  • SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, SECTION_ID, MINISITE_ID FROM IBE.IBE_SECTION_SEARCH_PART;
  • Filter by minisite and organization: WHERE MINISITE_ID = :minisite AND ORGANIZATION_ID = :org.
  • Locate all sections for an item: WHERE INVENTORY_ITEM_ID = :item_id.
  • Count items per section for reporting: SELECT SECTION_ID, COUNT(*) FROM IBE.IBE_SECTION_SEARCH_PART GROUP BY SECTION_ID.
  • Reconciliation: compare IBE_SECTION_SEARCH_PART rows against IBE section and minisite definitions to find orphaned or missing assignments.

Because the four key columns carry all business meaning, negative or duplicate search results usually indicate stale assignments rather than missing descriptive attributes.

Related Objects

The documented dependency information is sparse. The table does not reference any database object in the excerpt except the SECURITY_GROUP_ID foreign key to FND_SECURITY_GROUPS. It is referenced by IBE.IBE_SECTION_SEARCH_PART#, the internal IBE synonym/anchor object.

  • IBE.IBE_SECTION_SEARCH_PART# — internal anchor referenced by this table.
  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID.
  • INVENTORY_ITEM master — implied join via INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • iStore section and minisite definition tables (IBE section/minisite objects) — implied joins via SECTION_ID and MINISITE_ID.
  • IBE_SECTION_SEARCH_PART_U1 — the unique index enforcing the composite business key.
  • IBE_SECTION_SEARCH_PART_PK — the primary key constraint on the same four columns.

All other relationships, such as links to item master or iStore content, should be confirmed against the actual IBE schema before being treated as declared FK dependencies.