Search Results csp_curr_sup_dem_sums




Overview
Explore in AI Chat

Overview

The CSP_CURR_SUP_DEM_SUMS table is a core data object within the Oracle E-Business Suite (EBS) Spares Management (CSP) module, applicable to both versions 12.1.1 and 12.2.2. It serves as a summary repository for consolidated supply and demand information related to spare parts inventory. This table is fundamental to the module's ability to analyze inventory positions, forecast requirements, and support planning decisions by providing a pre-aggregated, current snapshot of material flow. Its role is to act as a performance-optimized data source for reporting and analytical processes within the spares management lifecycle, eliminating the need for real-time aggregation from transactional tables.

Key Information Stored

The table's structure is designed to store summarized data at a specific organizational and item granularity. Its primary key is the system-generated SUPPLY_DEMAND_ID. The most critical columns define the context of the summary and the aggregated quantities. The documented unique key (CSP_CURR_SUP_DEM_UK) highlights the core dimensions: ORGANIZATION_ID, INVENTORY_ITEM_ID, and SUBINVENTORY_CODE. This indicates summaries are stored per item, per organization, and per specific stock location (subinventory). While the exact quantity columns are not detailed in the provided metadata, based on its description, the table would typically contain numeric columns summarizing total demand (e.g., from service requests, work orders), total supply (e.g., on-hand, on-order, in-transit), and potentially calculated net availability or projected shortages for the defined part-loop and hierarchy node contexts.

Common Use Cases and Queries

This table is primarily accessed for inventory analysis and reporting. Common use cases include generating dashboards showing current spare part availability across depots, running shortage reports to trigger procurement, and analyzing demand patterns within a specific parts loop or organizational hierarchy. A typical analytical query would join this summary table to item and organization master data to produce a readable report. For example:

  • Sample Query Pattern: SELECT msib.segment1 item_code,
    cds.organization_id,
    cds.subinventory_code,
    cds.total_demand_qty,
    cds.total_supply_qty,
    (cds.total_supply_qty - cds.total_demand_qty) net_available
    FROM csp_curr_sup_dem_sums cds,
    mtl_system_items_b msib
    WHERE cds.inventory_item_id = msib.inventory_item_id
    AND cds.organization_id = msib.organization_id
    AND cds.parts_loop_id = :p_loop_id
    ORDER BY net_available ASC;
  • Reporting: Data from this table feeds standard CSP reports and can be extracted for custom inventory position or supply-demand variance analyses.

Related Objects

The table maintains strict referential integrity with several key EBS master and CSP transactional tables, as documented by its foreign key constraints. These relationships are essential for accurate data context and validation.

  • CSP_REP_HIERARCHIES: Joined via HIERARCHY_NODE_ID. This links the summary to a specific node within a reporting hierarchy, enabling rolled-up analysis across organizational structures.
  • CSP_PARTS_LOOPS_B: Joined via PARTS_LOOP_ID. This associates the summary data with a specific parts loop, which is a logical grouping of items and locations for planning purposes.
  • MTL_SYSTEM_ITEMS_B: Joined via INVENTORY_ITEM_ID and ORGANIZATION_ID. This provides access to the item master attributes like description, part number, and item status.
  • MTL_SECONDARY_INVENTORIES: Joined via SUBINVENTORY_CODE and ORGANIZATION_ID. This provides details about the specific stock location, such as its name and material status controls.