Search Results csp_supersede_items




Overview
Explore in AI Chat

Overview

The CSP_SUPERSEDE_ITEMS table is a core data object within the Oracle E-Business Suite Spares Management (CSP) module. Spares Management supports the depot repair, field service, and component replacement processes that Oracle EBS customers rely on for maintaining serviceable inventory. This table records the relationship between items planned for warehouses and the items supplied to specific subinventories, effectively capturing item supersession and substitution rules at the warehouse-to-subinventory level.

In the context of Oracle EBS 12.1.1 and 12.2.2, CSP_SUPERSEDE_ITEMS provides the configuration data that drives which replacement or equivalent item is issued when a demanded item is not available or has been superseded by a newer revision. The table resides in the CSP schema and is documented as VALID in the ETRM repository.

The heuristic Data Vault classification mined from the documented foreign key structure is standalone. From a dimensional modeling perspective, this suggests the table is not acting as a classic hub, link, or satellite anchored to surrounding relationships. Instead, it behaves as an independent reference or configuration entity keyed by its own surrogate identifier, and modelers should treat it accordingly when designing downstream reporting structures.

Key Information Stored

The table contains 26 documented columns. The most significant are described below.

The combination of INVENTORY_ITEM_ID, ORGANIZATION_ID, SUB_INVENTORY_CODE, and ITEM_SUPPLIED constitutes the effective business meaning of each row, even though only SUPERSEDE_ID carries a documented unique constraint.

Common Use Cases and Queries

Typical use cases include auditing supersession configuration across warehouses, validating that supplied items exist and are active in the target subinventory, and troubleshooting repair or fulfillment transactions where the wrong substitute item was issued.

A representative query to list supersession rules for a given organization:

  • SELECT s.SUPERSEDE_ID, s.INVENTORY_ITEM_ID, s.ORGANIZATION_ID, s.SUB_INVENTORY_CODE, s.ITEM_SUPPLIED FROM CSP.CSP_SUPERSEDE_ITEMS s WHERE s.ORGANIZATION_ID = :org_id;

A join pattern to resolve item descriptions through the item master:

  • SELECT s.SUPERSEDE_ID, m1.SEGMENT1 demanded_item, m2.SEGMENT1 supplied_item, s.SUB_INVENTORY_CODE FROM CSP.CSP_SUPERSEDE_ITEMS s, MTL_SYSTEM_ITEMS_B m1, MTL_SYSTEM_ITEMS_B m2 WHERE s.INVENTORY_ITEM_ID = m1.INVENTORY_ITEM_ID AND s.ORGANIZATION_ID = m1.ORGANIZATION_ID AND s.ITEM_SUPPLIED = m2.INVENTORY_ITEM_ID AND s.ORGANIZATION_ID = m2.ORGANIZATION_ID;

Reporting use cases include generating warehouse-level supersession matrices and identifying subinventories with sparse or missing replacement rules. The flexfield columns support customer-specific reporting when standard columns are insufficient.

Related Objects

The documented FK structure classifies CSP_SUPERSEDE_ITEMS as standalone, meaning no formal foreign key relationships are documented to external tables. The following objects are significant in practice because their key columns align with the columns stored here:

  • MTL_SYSTEM_ITEMS_B — Joined on INVENTORY_ITEM_ID and ORGANIZATION_ID to resolve item identifiers to segments and descriptions.
  • MTL_ITEM_SUB_INVENTORIES — Joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, and SUB_INVENTORY_CODE to validate item-subinventory eligibility.
  • MTL_SECONDARY_INVENTORIES — Joined on ORGANIZATION_ID and SUB_INVENTORY_CODE for subinventory attributes.
  • MTL_PARAMETERS — Joined on ORGANIZATION_ID to confirm warehouse context.
  • CSP_REPAIR_ORDERS and related CSP tables — Consume the supersession data during repair and replacement processing.

Because the ETRM metadata documents no external foreign keys, integrators should verify referential expectations through the Spares Management application logic rather than assuming database-enforced constraints.