Results for “ibe_dsp_section_items”

50+ results




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

Overview

The IBE_DSP_SECTION_ITEMS table is an iStore (IBE) repository object that stores the association between display sections and the inventory items merchandised within them. It resides in the IBE schema and is central to the personalization and storefront presentation layer of Oracle iStore, which consumes its content to render category, section, and product listing pages. Each row binds one section to one item within a specific inventory organization, subject to optional activation windows and explicit display ordering.

From a Data Vault modeling perspective, the mined relationship structure classifies this table as satellite-leaning. The surrogate primary key SECTION_ITEM_ID identifies each association instance, while the combination of SECTION_ID, INVENTORY_ITEM_ID, and ORGANIZATION_ID behaves as a natural business key. In Data Vault terms, IBE_DSP_SECTION_ITEMS can be modeled as a link between the section hub (IBE_DSP_SECTIONS_B) and the item hub (MTL_SYSTEM_ITEMS_B), carrying descriptive attributes such as sort order, activation dates, and association reason codes as satellite payload.

Key Information Stored

The table contains 16 documented columns in Oracle EBS 12.2.2. The most operationally significant are:

The composite unique index IBE_DSP_SECTION_ITEMS_U2 (SECTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID) is the business-key candidate preventing duplicate item placements within a section.

Common Use Cases and Queries

Typical uses include storefront rendering, merchandising audits, and personalization reporting. A representative query retrieves active items for a given section ordered by display sequence:

  • SELECT section_item_id, inventory_item_id, organization_id, sort_order FROM ibe.ibe_dsp_section_items WHERE section_id = :p_section_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) AND security_group_id = :p_org_id ORDER BY sort_order;
  • Identifying duplicate or conflicting item placements by grouping on SECTION_ID, INVENTORY_ITEM_ID, and ORGANIZATION_ID.
  • Reconciling orphaned associations where the referenced item no longer exists in MTL_SYSTEM_ITEMS_B.
  • Auditing expired associations for cleanup ahead of storefront refreshes.

Related Objects

The most significant dependent and referenced objects are:

  • IBE_DSP_SECTIONS_B — parent section definition; joined on SECTION_ID.
  • MTL_SYSTEM_ITEMS_B — inventory item master; joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • FND_SECURITY_GROUPS — security group lookup; joined on SECURITY_GROUP_ID.
  • IBE_DSP_MSITE_SCT_ITEMS — dependent child table referencing SECTION_ITEM_ID for multi-site section item assignments.
  • IBE_DSP_SECTION_ITEMS_PK / _U1 / _U2 — primary and unique indexes enforcing identity and business keys.

Together these objects form the merchandising backbone consumed by iStore rendering APIs and personalization engines.