Results for “relation_type_code”

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

Overview

IBE_CT_RELATED_ITEMS_V is a validation view owned by the APPS schema in Oracle E-Business Suite, belonging to the IBE (iStore) product family. In both Oracle EBS 12.1.1 and 12.2.2, the object carries a status of VALID and is exposed as a read-only projection of the related-items relationship data used by the iStore merchandising and catalog functionality. Its purpose is to present a deduplicated view of the relationships that exist between an inventory item and a related item, including the semantic nature of that relationship (for example cross-sell, up-sell, or accessory associations) and the inventory organization in which the association is defined.

The view plays a supporting role in reporting, integration, and personalization scenarios where customers or developers reference related_item_id — the identifier of the item that is related to the primary item. Rather than querying the underlying relationship store directly, the view provides a stable, DISTINCT-filtered access point that is commonly referenced in iStore catalog extensions, order capture cross-sell logic, and custom correlated-item reports.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists a single referenced base object: the synonym IBE_CT_RELATED_ITEMS (which resolves to the underlying APPS table of the same column layout). The view text is a straightforward projection:

• SELECT DISTINCT INVENTORY_ITEM_ID, RELATED_ITEM_ID, RELATION_TYPE_CODE, ORGANIZATION_ID FROM IBE_CT_RELATED_ITEMS

Because the definition uses SELECT DISTINCT, the view collapses any duplicate rows present in the base relationship table, ensuring that a given (item, related item, relation type, organization) tuple appears only once. This deduplication is the primary functional difference between the view and its underlying object; the view introduces no joins, filters, or derived columns of its own. Consequently, the view inherits the base table's dependency on organization-level item relationships and remains strictly a presentation-layer convenience.

Key Columns

• INVENTORY_ITEM_ID — The primary item in the relationship, referencing the inventory item master for the owning organization.
• RELATED_ITEM_ID — The item associated with the primary item. This is the column most often searched for (for example, by the term "related_item_id") when tracing recommendations, cross-sells, and accessory mappings.
• RELATION_TYPE_CODE — A lookup-style code that classifies the nature of the association, distinguishing one relationship category from another (e.g., cross-sell versus up-sell). It drives how the related item is presented in the storefront.
• ORGANIZATION_ID — The inventory organization context, confirming that related-item relationships are organization-specific. Two organizations may hold different related-item sets for the same base item.

Common Use Cases and Queries

Typical scenarios include catalog validation (confirming that every related item exists and is transactable), merchandising audits (identifying all cross-sell relationships for a category), and custom reports that surface related items adjacent to product detail pages. A representative query retrieving relationships for a given base item is:

SELECT inventory_item_id, related_item_id, relation_type_code, organization_id FROM apps.ibe_ct_related_items_v WHERE inventory_item_id = :p_item_id AND organization_id = :p_org_id;

To trace where a specific item is used as a related item (the classic related_item_id lookup), invert the predicate:

SELECT inventory_item_id, relation_type_code, organization_id FROM apps.ibe_ct_related_items_v WHERE related_item_id = :p_item_id;

Because the row set is deduplicated, results from these queries are safe to join directly to other iStore catalog views without introducing duplicate rows. The view should be treated as read-only; all maintenance of relationships occurs against the underlying base object, not through this view.