Results for “as_view_forecast_v”

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

Overview

AS_VIEW_FORECAST_V is a reporting view within the Oracle E-Business Suite AS – Sales Foundation module. Its documented description is "Forecast detail view." The view consolidates sales quota, forecast, and pipeline information at the level of an individual salesperson (employee) within a sales group for a given period. It is designed to expose forecasted revenue and quantity figures alongside the corresponding quota, interest type, and interest code attributes, making it suitable for downstream reporting and integration scenarios in both 12.1.1 and 12.2.2.

The view plays a bridging role in ETRM reporting because it denormalizes several related Sales Foundation entities — quota assignments, forecast freezes, sales group definitions, person names, and interest classifications — into a single queryable structure. A user searching for employee_last_name will find that attribute is surfaced here as EMPLOYEE_LAST_NAME, joined from the person (Per_People_F / PER_ALL_PEOPLE_F) source.

Underlying Base Objects

The ETRM metadata records no explicit referenced base objects and notes that the view is "Not implemented in this database" in the captured environment. However, the documented view text reveals the principal objects in its definition:

• ASQ — the sales quota source table (AS_SALES_QUOTAS), supplying PERIOD_NAME, FREEZE_PERIOD, SALES_QUOTA_ID, SALES_GROUP_ID, SALESFORCE_ID, EMPLOYEE_PERSON_ID, interest types/codes, ITEM_ID, REVENUE_FLAG, and QUOTA_AMOUNT.
• AF — the forecast detail table (AS_FORECASTS), supplying CURRENCY_CODE, FORECAST_AMOUNT, UPSIDE_AMOUNT, LEAD_* amounts, UOM_CODE, FORECAST_QUANTITY, and UPSIDE_QUANTITY.
• ASG — the sales group table (AS_SALES_GROUPS), providing the SALES_GROUP name.
• PP — the person table (PER_ALL_PEOPLE_F), providing EMPLOYEE_FIRST_NAME and EMPLOYEE_LAST_NAME.
• AIT, AIC1, AIC2 — interest type and primary/secondary interest code lookup tables.

Pipeline amounts and quantities are not stored but computed at runtime through calls to the package AS_LEADS_PKG.GET_PIPELINE_AMOUNT and GET_PIPELINE_QUANTITY.

Key Columns

• EMPLOYEE_LAST_NAME / EMPLOYEE_FIRST_NAME — the salesperson's name, joined from PER_ALL_PEOPLE_F via EMPLOYEE_PERSON_ID. The last name is the attribute most commonly used to identify or group the report owner.
• PERIOD_NAME, FREEZE_PERIOD — the forecast period and its freeze status, which governs whether live quota amounts or frozen amounts are returned.
• SALES_GROUP, SALESFORCE_ID, SALES_QUOTA_ID — organizational identifiers for the forecast line.
• INTEREST_TYPE, PRIMARY_INTEREST_CODE, SECONDARY_INTEREST_CODE — product/interest classification of the forecast.
• FORECAST_AMOUNT, UPSIDE_AMOUNT, LEAD_WON_AMOUNT, LEAD_FORECAST_AMOUNT, LEAD_UPSIDE_AMOUNT — monetary pipeline measures, derived or frozen depending on FREEZE_PERIOD.
• FORECAST_QUANTITY, UPSIDE_QUANTITY, UOM_CODE — quantity measures for the same forecast lines.

Common Use Cases and Queries

Typical uses include sales forecast-by-rep reporting, quota-versus-forecast variance analysis, and extraction of pipeline data for external BI tools. Because the view computes pipeline values through package calls, queries may perform best when filtered by period and sales group.

• Retrieve forecast by rep last name:

  SELECT EMPLOYEE_LAST_NAME, PERIOD_NAME, SALES_GROUP,
         FORECAST_AMOUNT, UPSIDE_AMOUNT, FORECAST_QUANTITY
  FROM   AS_VIEW_FORECAST_V
  WHERE  EMPLOYEE_LAST_NAME = :p_last_name
  AND    PERIOD_NAME = :p_period;

• Quota-versus-forecast comparison grouped by sales group for a period.
• Pipeline extraction selecting LEAD_WON_AMOUNT and LEAD_FORECAST_AMOUNT for CRM or data-warehouse loading.

Note that the object may not be deployed in every environment; confirm its presence in ALL_VIEWS before relying on it in production queries.