Search Results csp_usage_headers




Overview
Explore in AI Chat

Overview

The CSP_USAGE_HEADERS table is a core data object within the Oracle E-Business Suite Spares Management (CSP) module. It functions as the primary repository for storing summarized planning recommendations generated by the system's forecasting and replenishment engines. This table acts as a header record, aggregating key planning outputs for a specific inventory item within a particular subinventory and organization, based on a defined set of planning parameters. Its existence is critical for managing spare parts inventory, enabling planners to review, approve, and act upon system-generated suggestions for purchase orders, work orders, or transfers to maintain optimal stock levels and serviceability.

Key Information Stored

The table's structure centers on a unique identifier and essential foreign key relationships that contextualize the planning data. The primary key, USAGE_HEADER_ID, uniquely identifies each planning recommendation summary record. The table's integrity and meaning are derived from its relationships to other master data tables, as indicated by its foreign keys. The PLANNING_PARAMETERS_ID column links to CSP_PLANNING_PARAMETERS, defining the rule set used for the forecast. The INVENTORY_ITEM_ID and ORGANIZATION_ID columns jointly reference MTL_SYSTEM_ITEMS_B, identifying the specific spare part. Similarly, the SECONDARY_INVENTORY and ORGANIZATION_ID columns reference MTL_SECONDARY_INVENTORIES, pinpointing the specific subinventory location. While the provided metadata does not list detail columns, this header table typically stores high-level summary metrics such as total forecasted demand, recommended order quantity, and the planning date range.

Common Use Cases and Queries

This table is central to spares planning operations and related reporting. A primary use case is the generation of a planner workbench report, where planners query for pending recommendations needing review. A typical query would join to item and subinventory tables to display meaningful descriptions. For example:

SELECT cuh.USAGE_HEADER_ID, msib.SEGMENT1 ITEM, msi.SECONDARY_INVENTORY_NAME, cuh.* FROM CSP.CSP_USAGE_HEADERS cuh, INV.MTL_SYSTEM_ITEMS_B msib, INV.MTL_SECONDARY_INVENTORIES msi WHERE cuh.INVENTORY_ITEM_ID = msib.INVENTORY_ITEM_ID AND cuh.ORGANIZATION_ID = msib.ORGANIZATION_ID AND cuh.SECONDARY_INVENTORY = msi.SECONDARY_INVENTORY AND cuh.ORGANIZATION_ID = msi.ORGANIZATION_ID;

Another critical use case is the batch loading of approved recommendations into the procurement or manufacturing modules. Programs would select records from CSP_USAGE_HEADERS marked for processing to create requisitions or discrete jobs. Analysts also query this table to analyze forecast accuracy over time by comparing historical recommendations against actual usage recorded in transactional tables.

Related Objects

The CSP_USAGE_HEADERS table maintains documented foreign key relationships with several key inventory and planning tables. These relationships are fundamental to its purpose:

  • CSP_PLANNING_PARAMETERS: Linked via CSP_USAGE_HEADERS.PLANNING_PARAMETERS_ID. This defines the planning rules and policies applied.
  • MTL_SECONDARY_INVENTORIES: Linked via the composite key CSP_USAGE_HEADERS.SECONDARY_INVENTORY and CSP_USAGE_HEADERS.ORGANIZATION_ID. This identifies the specific subinventory location for the recommendation.
  • MTL_SYSTEM_ITEMS_B: Linked via the composite key CSP_USAGE_HEADERS.INVENTORY_ITEM_ID and CSP_USAGE_HEADERS.ORGANIZATION_ID. This provides the item master details for the spare part being planned.

It is highly probable that this header table has a detail child table (e.g., CSP_USAGE_LINES) storing period-by-period forecast details, though this is not specified in the provided metadata.