Results for “relation_rule_id”

28 results




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

Overview

IBE_CT_RELATED_ITEMS is a denormalized, precomputed table owned by the IBE (iStore) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to persist the resolved output of iStore product cross-sell and up-sell mapping rules. Rather than evaluating mapping relationship rules at query time, the iStore "relationship content" publishing process flattens the rule definitions into concrete item-to-item pairs, allowing storefront pages, recommendation panels, and related-item lists to be rendered with a simple indexed lookup. The table therefore serves as a materialized relationship cache layered between the rule configuration tables and the runtime storefront UI.

From a Data Vault modeling perspective, the structure carries a heuristic classification of link. This is appropriate because each row connects a base inventory item to a related item at a given organization and relation type — the row is a relationship assertion, not a descriptive attribute of a single item. It contains no meaningful descriptive satellite payload of its own; the descriptive content (item descriptions, names, categories) resides in the referenced MTL_SYSTEM_ITEMS_B records.

Key Information Stored

The table exposes 16 documented columns. The most operationally significant are:

The primary key IBE_CT_RELATED_ITEMS_PK is a composite of INVENTORY_ITEM_ID, RELATED_ITEM_ID, RELATION_TYPE_CODE, and ORGANIZATION_ID. A separate unique index, IBE_CT_RELATED_ITEMS_U1, spanning INVENTORY_ITEM_ID, ORGANIZATION_ID, RELATED_ITEM_ID, RELATION_TYPE_CODE, and RELATION_RULE_ID, functions as the business-key candidate — ensuring that a single rule cannot publish the same item pair more than once. There is no single surrogate sequence key; the natural composite constitutes identity.

Common Use Cases and Queries

Typical consultation of this table centers on storefront rendering and merchandising analysis. A standard retrieval for related items of a given product scoped to an organization:

  • SELECT related_item_id, relation_type_code FROM ibe_ct_related_items WHERE inventory_item_id = :p_item AND organization_id = :p_org;
  • Joining to MTL_SYSTEM_ITEMS_B to resolve names and descriptions for display.
  • Auditing stale or orphaned relationships by comparing LAST_UPDATE_DATE against the last rule publish run.
  • Identifying which relation rules produced the largest fan-out of related pairs using RELATION_RULE_ID in a GROUP BY.
  • Diagnosing missing recommendations by confirming whether rows exist for a base item at all, versus a storefront configuration issue.

Because the data is derived, direct DML is discouraged; regeneration occurs through the iStore relationship publishing concurrent program, whose REQUEST_ID and PROGRAM_ID are stamped on each row.

Related Objects

  • MTL_SYSTEM_ITEMS_B — referenced twice, via INVENTORY_ITEM_ID and RELATED_ITEM_ID, both combined with ORGANIZATION_ID, supplying item master attributes.
  • IBE_CT_RELATION_RULES — parent rule definition table joined on RELATION_RULE_ID.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security partitioning.
  • IBE_CT_RELATED_ITEMS_PK / _U1 — the primary and unique indexes enforcing identity and deduplication.
  • FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — implicit parents of REQUEST_ID and PROGRAM_ID for publish-run tracing.
  • iStore storefront (IBE) runtime views and the item relationship publishing concurrent program, which together populate and consume this table.