Results for “csp_forecast_rules_b”

50+ results




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

Overview

CSP_FORECAST_RULES_B is the base (language-independent) definition table for forecast rules within the Oracle E-Business Suite Spares Management (CSP) module. It stores the configurable parameters that govern how spare parts demand forecasting is performed, including the forecasting method, the number of historical periods consumed, the number of future periods projected, and the weighting or smoothing coefficients applied to that projection. Because it is a "_B" table, it holds the non-translatable business attributes of a forecast rule, while the corresponding "_TL" table carries the language-specific descriptive text. The object is owned by the CSP schema and is classified as VALID in the ETRM 12.2.2 documented schema, comprising 44 columns.

From a Data Vault modeling perspective, the mined FK structure suggests a hub-leaning classification. The table carries a single-column surrogate primary key (FORECAST_RULE_ID) with no upstream parent dependencies other than an optional reference to FND_SECURITY_GROUPS via SECURITY_GROUP_ID, and it is referenced by several downstream transactional and configuration tables. This positioning makes CSP_FORECAST_RULES_B a natural candidate for a hub entity, with a satellite holding the descriptive forecast parameters.

Key Information Stored

The table is anchored by the surrogate primary key FORECAST_RULE_ID, enforced by the CSP_FORECAST_RULES_B_PK constraint. Two unique indexes identify the business-key candidates: CSP_FORECAST_RULES_B_U1 on FORECAST_RULE_ID and CSP_FORECAST_RULES_B_U2 on FORECAST_RULE_NAME, meaning FORECAST_RULE_NAME functions as the human-readable unique identifier for a rule.

The most significant functional columns are:

Common Use Cases and Queries

Planners and administrators interrogate this table to understand or audit the forecast configuration in use. A typical query returns all active forecast rules with their methodology and period counts:

  • Listing configured rules: SELECT FORECAST_RULE_ID, FORECAST_RULE_NAME, FORECAST_METHOD, PERIOD_TYPE, FORECAST_PERIODS, HISTORY_PERIODS FROM CSP_FORECAST_RULES_B ORDER BY FORECAST_RULE_NAME;
  • Resolving a rule used by a part loop: join CSP_PARTS_LOOPS_B or CSP_PLANNING_PARAMETERS to CSP_FORECAST_RULES_B on FORECAST_RULE_ID to trace which rule drives a specific planning parameter.
  • Retrieving the translatable name: join CSP_FORECAST_RULES_TL on FORECAST_RULE_ID and filter by LANGUAGE to obtain the display name for reporting.
  • Inspecting smoothing configuration: SELECT FORECAST_RULE_NAME, ALPHA, BETA, TRACKING_SIGNAL_CYCLE FROM CSP_FORECAST_RULES_B WHERE FORECAST_METHOD IS NOT NULL;
  • Reviewing weighting profiles: select the WEIGHTED_AVG_PERIOD1 through WEIGHTED_AVG_PERIOD12 columns to audit weighted-average setup.

These queries support reporting on forecast governance, diagnosing unexpected forecast output caused by misconfigured periods or coefficients, and validating security group assignments.

Related Objects

The table participates in a well-defined foreign-key network:

  • CSP_FORECAST_RULES_TL — translation table joined on FORECAST_RULE_ID, supplying language-specific descriptions.
  • CSP_MSTRSTCK_LISTS_ITMS — master stock list items referencing FORECAST_RULE_ID, associating rules with specific spare items.
  • CSP_PARTS_LOOPS_B — parts loop definitions referencing FORECAST_RULE_ID.
  • CSP_PLANNING_PARAMETERS — planning parameters referencing FORECAST_RULE_ID, the primary operational consumer of forecast rules.
  • FND_SECURITY_GROUPS — referenced by this table through SECURITY_GROUP_ID for row-level security.