Search Results as_forecast_categories_b




Overview
Explore in AI Chat

Overview

The AS_FORECAST_CATEGORIES_B table is a core reference data table within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It serves as the master repository for defining forecast categories, which are critical for configuring and executing the sales forecasting process. A forecast category determines the selection of interest types—specific classifications of sales opportunities—that are eligible for inclusion in a forecast. This establishes a fundamental business rule: only opportunities with interest types mapped to a defined forecast category can be utilized for forecasting purposes. The table is owned by the OSM schema and is a base table, as indicated by the '_B' suffix, which typically stores the core transactional or master data.

Key Information Stored

While the provided metadata does not list all columns, the primary key and foreign key relationships clearly identify the essential data elements. The central column is FORECAST_CATEGORY_ID, a unique system-generated identifier serving as the primary key for each forecast category record. This ID is the critical link used throughout the forecasting schema. Other columns in the table would typically store descriptive information such as the category name (e.g., 'Pipeline', 'Committed', 'Best Case'), an enabled flag, creation and last update dates, and the user IDs responsible for those actions. The table's purpose is to maintain this controlled list of categories that govern forecast data integrity.

Common Use Cases and Queries

The primary use case is the administration and validation of forecast data. Administrators use this table to define which opportunity stages or types are forecastable. A common operational query involves joining this table to opportunity or forecast data to validate entries or generate configuration reports. For example, to list all active forecast categories and their associated interest types (likely via a mapping table), a query might join AS_FORECAST_CATEGORIES_B to related entities. Another frequent pattern is using the FORECAST_CATEGORY_ID as a filter in reports on forecast accuracy (AS_FORECAST_ACTUALS) or internal forecast submissions (AS_INTERNAL_FORECASTS) to analyze performance by category. Sample SQL to retrieve all forecast categories would be: SELECT forecast_category_id, name FROM osm.as_forecast_categories_b WHERE enabled_flag = 'Y';

Related Objects

As documented in the foreign key relationships, the AS_FORECAST_CATEGORIES_B table is referenced by several key transactional tables in the forecasting module. The FORECAST_CATEGORY_ID column is the join point for these relationships:

  • AS_FORECAST_ACTUALS: This table stores historical forecast versus actuals data. It references AS_FORECAST_CATEGORIES_B via its FORECAST_CATEGORY_ID column to categorize the recorded actuals.
  • AS_FST_SALES_CATEGORIES: This is likely a mapping or assignment table that links forecast categories to specific sales categories or territories, also referencing the base category ID.
  • AS_INTERNAL_FORECASTS: This table holds internal forecast submissions. It uses the FORECAST_CATEGORY_ID to classify each forecast entry according to the predefined category.
These relationships enforce referential integrity, ensuring that all forecast-related data is tied to a valid, configured forecast category.