Search Results ibe_ct_rel_exclusions_pk

Overview

The IBE_CT_REL_EXCLUSIONS table is a core data object within the Oracle E-Business Suite iStore (IBE) module, versions 12.1.1 and 12.2.2. It serves a critical function in managing product relationship data for the iStore e-commerce platform. Specifically, this table stores records that define exclusions for precomputed product relationships. These relationships are automatically generated by the system based on configured mapping rules. The table's primary role is to provide a mechanism for administrators to override or fine-tune these system-generated relationships, ensuring that only intended product associations, such as cross-sells, up-sells, or accessories, are presented to customers on the storefront. By maintaining a list of exclusions, it allows for precise control over the product catalog's dynamic behavior.

Key Information Stored

The table's structure is designed to uniquely identify a specific product relationship to be excluded within a given organizational context. Its primary key is a composite of four columns, which together define the exact exclusion rule. The ORGANIZATION_ID specifies the operating unit or inventory organization. The RELATION_TYPE_CODE denotes the category of the product relationship (e.g., CROSS_SELL, UP_SELL). The INVENTORY_ITEM_ID and RELATED_ITEM_ID are foreign keys that identify the master item and the related item, respectively, whose precomputed relationship is to be suppressed. The existence of a record in this table for a given combination of these four values instructs the iStore application logic to exclude that particular relationship from being displayed or used in business logic.

Common Use Cases and Queries

A primary use case involves post-process refinement of bulk-generated relationship rules. For example, after running a concurrent program to create cross-sell suggestions based on product category mappings, a business user may identify specific item pairs that are not appropriate. An administrator would then insert a record into IBE_CT_REL_EXCLUSIONS to block those pairs. Common reporting queries focus on auditing existing exclusions. A typical SQL pattern joins this table to the inventory items table to retrieve item numbers and descriptions:

• SELECT excl.relation_type_code, org.organization_code, msi1.segment1 item1, msi2.segment1 item2 FROM ibe_ct_rel_exclusions excl, mtl_system_items_b msi1, mtl_system_items_b msi2, org_organization_definitions org WHERE excl.inventory_item_id = msi1.inventory_item_id AND excl.organization_id = msi1.organization_id AND excl.related_item_id = msi2.inventory_item_id AND excl.organization_id = msi2.organization_id AND excl.organization_id = org.organization_id;

Data maintenance is typically performed via seeded iStore administrative interfaces or custom scripts that validate item and organization IDs before performing INSERT or DELETE operations on this table.

Related Objects

The IBE_CT_REL_EXCLUSIONS table has defined foreign key relationships with the core inventory table, MTL_SYSTEM_ITEMS_B. These relationships enforce referential integrity for the item identifiers stored within the exclusions table.

• Foreign Key Reference to MTL_SYSTEM_ITEMS_B: The column IBE_CT_REL_EXCLUSIONS.INVENTORY_ITEM_ID references MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID, and the join condition includes IBE_CT_REL_EXCLUSIONS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID. This validates the master inventory item.
• Foreign Key Reference to MTL_SYSTEM_ITEMS_B: The column IBE_CT_REL_EXCLUSIONS.RELATED_ITEM_ID references MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID, with the same organization ID join. This validates the related inventory item.

This table is intrinsically linked to the iStore product relationship engine and is likely referenced by various iStore application programming interfaces (APIs) and concurrent programs responsible for generating and processing relationship data for the web store.