Results for “as_forecast_categories”

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

Overview

AS_FORECAST_CATEGORIES is a reference (setup) table within the Oracle E-Business Suite AS – Sales Foundation product family. Its role is to define the forecast categories that govern which interest types are eligible for forecast processing within the Sales/TeleSales application. Per the documented description, a forecast category determines the selection of interest types available for forecast, and any opportunity whose interest types are mapped to a given forecast category can only be used for forecasting purposes. This makes the table a controlling lookup that filters the universe of opportunities that enter forecast pipelines.

From a Data Vault modeling perspective, the mined FK classification identifies AS_FORECAST_CATEGORIES as a standalone object. This heuristic suggests modeling it as a small reference hub (or a hub with an attached descriptive satellite), since it is not documented as participating in any downstream FK link relationships. It should be treated as a stable, low-volume configuration table rather than a transactional entity.

Key Information Stored

The ETRM metadata for this object is intentionally thin, so only the columns explicitly documented are enumerated below. The most significant are:

• FORECAST_CATEGORY_ID — the surrogate primary key, defined by constraint AS_FORECAST_CATEGORIES_PK. This uniquely identifies each forecast category row and is the column referenced by any dependent setup or forecasting logic.

Beyond the primary key, the documented metadata does not enumerate additional columns, so no business-key column list can be asserted with authority. In practice, a reference table of this type typically carries a user-visible name and description, an enabled/disable flag, a start/end date range for effective dating, and standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY). These are inferred conventions and are not confirmed by the supplied ETRM excerpt; DBA verification against the deployed instance is required before relying on them.

The metadata explicitly records that the object is "Not implemented in this database," meaning the table has not been created in the environment examined. Any column-level assertions should therefore be validated against the target EBS instance before use.

Common Use Cases and Queries

Because forecast categories gate which interest types participate in forecasting, the table is primarily consumed by setup validation, forecasting configuration reports, and integration queries that must translate a forecast category into its permitted interest types. Typical reporting patterns include:

• Listing all defined forecast categories for a setup audit:

SELECT forecast_category_id
FROM   as_forecast_categories;

• Resolving a category to its permitted interest types by joining to the interest-type mapping table (name to be confirmed against the instance):

SELECT fc.forecast_category_id, it.interest_type_id
FROM   as_forecast_categories fc,
       <interest_type_mapping> it
WHERE  fc.forecast_category_id = it.forecast_category_id;

• Confirming whether an opportunity's interest types fall within a forecast-eligible category before including it in a forecast extract. Where the table is implemented, this is best handled via the appropriate AS public API rather than direct DML.

Since the object is not implemented in the documented database, queries against it will fail until the AS Sales Foundation setup is completed.

Related Objects

The supplied metadata lists no FK relationships originating from or referencing AS_FORECAST_CATEGORIES, consistent with its standalone Data Vault classification. The definitive related objects are therefore not enumerated by the ETRM extract. The only documented relationship is the primary key constraint AS_FORECAST_CATEGORIES_PK on FORECAST_CATEGORY_ID, which ties the table to any dependent object that stores a forecast_category_id foreign key.

Candidate related objects to investigate in a deployed instance include the interest-type mapping table that links forecast categories to interest types, the opportunity/interest-type tables in AS Sales Foundation, and the forecast-related views or APIs that accept a forecast category as a selection parameter. Each of these should be confirmed through the EBS data dictionary (for example, via ALL_CONSTRAINTS and ALL_CONS_COLUMNS) rather than assumed, given the limited metadata provided.