Search Results csp_forecast_rules_b




Overview
Explore in AI Chat

Overview

The CSP_FORECAST_RULES_B table is a core data structure within the Oracle E-Business Suite Spares Management (CSP) module. It serves as the master repository for defining and storing forecast rules, which are critical configuration entities used to govern the demand forecasting process for spare parts. These rules determine the mathematical models and parameters applied to historical consumption data to generate future demand projections. The table's role is foundational, as its stored rules are referenced by other key planning and configuration entities to drive automated inventory planning and replenishment workflows in both EBS 12.1.1 and 12.2.2.

Key Information Stored

While the provided metadata does not list specific columns, the structure and relationships indicate the table's primary purpose. The central column is the FORECAST_RULE_ID, which serves as the unique primary key identifier for each forecast rule definition. Based on standard EBS design patterns and the existence of a corresponding translation table (CSP_FORECAST_RULES_TL), it is inferred that the base table stores seeded or user-defined codes, effective dates, and other control attributes. The translation table would store the language-specific name and description for each rule. The data stored in this table collectively defines the forecasting methodology, such as specifying a moving average, exponential smoothing, or other statistical model to be applied.

Common Use Cases and Queries

This table is primarily accessed during the setup and execution of the spares planning engine. Common operational scenarios include associating a forecast rule with a specific part or planning parameter, and generating reports on rule utilization. A typical query would join the base and translation tables to retrieve a meaningful list of available rules for a user interface LOV or setup page.

  • Retrieving Active Forecast Rules:
    SELECT b.forecast_rule_id, tl.name, tl.description
    FROM csp_forecast_rules_b b, csp_forecast_rules_tl tl
    WHERE b.forecast_rule_id = tl.forecast_rule_id
    AND tl.language = USERENV('LANG')
    AND SYSDATE BETWEEN b.start_date_active AND NVL(b.end_date_active, SYSDATE);
  • Identifying Parts Using a Specific Rule:
    SELECT pp.organization_id, pp.inventory_item_id, msib.segment1 part_number
    FROM csp_planning_parameters pp, mtl_system_items_b msib
    WHERE pp.forecast_rule_id = &RULE_ID
    AND pp.inventory_item_id = msib.inventory_item_id
    AND pp.organization_id = msib.organization_id;

Related Objects

The CSP_FORECAST_RULES_B table maintains critical referential integrity with several other Spares Management tables, as documented by its foreign key relationships. The primary key (FORECAST_RULE_ID) is referenced by the following objects:

  • CSP_FORECAST_RULES_TL: Provides translated names and descriptions for the forecast rules (join on FORECAST_RULE_ID).
  • CSP_PLANNING_PARAMETERS: Associates a specific forecast rule with the planning setup for an inventory item (join on FORECAST_RULE_ID).
  • CSP_PARTS_LOOPS_B: References the forecast rule within parts loop definitions, which group items for planning (join on FORECAST_RULE_ID).
  • CSP_MSTRSTCK_LISTS_ITMS: Links the forecast rule to items on a master stock list (join on FORECAST_RULE_ID).

These relationships underscore that CSP_FORECAST_RULES_B acts as a master source of configuration data, directly influencing planning parameters, part groupings, and critical inventory lists.