Results for “manager_review_date”

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

Overview

AS_FORECASTS is a transactional table in the Oracle E-Business Suite Sales Foundation module (product code AS), owned by the OSM schema. It functions as the primary repository for revenue forecasts and quota credit forecasts captured at the salesforce, sales group, employee, and partner level. Within the EBS 12.1.1 and 12.2.2 data models, the table supports the forecasting and pipeline-management processes that feed quota attainment reporting and territory-level revenue projections. Each row represents a discrete forecast record tied to a period, currency, and organizational unit, with separate amount and quantity columns that distinguish committed, best-case, upside, and lead-based forecast categories.

The mined Data Vault classification for this table is standalone. As a heuristic modeling suggestion, this implies the table behaves largely as a self-contained transactional entity rather than a pure hub, link, or satellite. Although it carries foreign keys to AS_SALES_QUOTAS and AS_SALESFORCE, its dominant business purpose is to record forecast facts, so treating it as a satellite-like fact holder keyed by its surrogate identifier is a reasonable starting point for downstream modeling.

Key Information Stored

The table contains 58 documented columns. The surrogate primary key is FORECAST_ID, enforced by the AS_FORECASTS_PK constraint and additionally protected by the unique index AS_FORECASTS_U1. The most operationally significant columns include:

• FORECAST_ID — Surrogate primary key and unique business-key candidate for the forecast row.
• PERIOD_NAME — The accounting or forecast period to which the record applies.
• CURRENCY_CODE — Currency in which the forecast amounts are expressed.
• FORECAST_AMOUNT and FORECAST_QUANTITY — The core committed forecast values in monetary and unit terms.
• UPSIDE_AMOUNT and UPSIDE_QUANTITY — Best-case or upside potential beyond the committed forecast.
• LEAD_WON_AMOUNT, LEAD_FORECAST_AMOUNT, LEAD_UPSIDE_AMOUNT — Monetary breakdown of pipeline by lead status, with matching LEAD_WON_QUANTITY, LEAD_FORECAST_QUANTITY, and LEAD_UPSIDE_QUANTITY.
• SALES_QUOTA_ID — Foreign key to AS_SALES_QUOTAS, linking the forecast to its quota record.
• SALESFORCE_ID — Foreign key to AS_SALESFORCE, identifying the sales organization.
• EMPLOYEE_PERSON_ID and SALES_GROUP_ID — Attribution of the forecast to a person and selling group.
• REVENUE_FLAG and COMMIT_FLAG — Indicators controlling whether the row counts toward revenue and commitment reporting.
• SALES_QUOTA_AMOUNT — The quota target associated with the forecast line.
• SHIP_DATE and END_SHIP_DATE — Shipping window used for revenue timing analysis.

Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and the ATTRIBUTE_CATEGORY plus ATTRIBUTE1–15 flexfield columns are also present for extensibility.

Common Use Cases and Queries

Typical reporting scenarios include quota-versus-forecast variance analysis, pipeline coverage ratios, and salesforce-level revenue projection. A representative query aggregates committed and upside amounts by salesforce for a given period:

• SELECT salesforce_id, period_name, SUM(forecast_amount), SUM(upside_amount) FROM as_forecasts WHERE period_name = :period GROUP BY salesforce_id, period_name;
• SELECT f.forecast_id, f.forecast_amount, q.quota_amount FROM as_forecasts f JOIN as_sales_quotas q ON f.sales_quota_id = q.sales_quota_id;
• SELECT employee_person_id, SUM(lead_won_amount), SUM(lead_forecast_amount) FROM as_forecasts WHERE revenue_flag = 'Y' GROUP BY employee_person_id;

These patterns support pipeline dashboards, commission-credit validation, and period-close revenue estimates.

Related Objects

The most significant related objects, based on the documented foreign-key structure, are:

• AS_SALES_QUOTAS — Referenced via AS_FORECASTS.SALES_QUOTA_ID; supplies the quota target against which forecasts are measured.
• AS_SALESFORCE — Referenced via AS_FORECASTS.SALESFORCE_ID; defines the sales organization owning the forecast.

Additional dependencies implied by column usage include the employee/person tables referenced through EMPLOYEE_PERSON_ID, the sales group definitions behind SALES_GROUP_ID, and the pricing entities PRICE_LIST_ID and PRICE, which connect the forecast to list pricing. Reporting views and concurrent programs in the Sales Foundation module typically join these objects to produce quota attainment and pipeline reports.