Search Results rolling_forecast_flag
Overview
The view APPS.AST_OPPORTUNITY_LINES_V belongs to the Oracle EBS TeleSales (AST) product family and is registered as a VALID database object owned by the APPS schema in both 12.1.1 and 12.2.2. It presents opportunity line information stored in the underlying lead-line table, enriching each row with descriptive attributes drawn from item master, product hierarchy, campaign, and offer sources. Functionally, the view serves as a denormalized read layer for opportunity and lead-line reporting, supporting sales pipeline analysis, forecasting, and integration with external or custom applications that require a single query surface across multiple reference objects.
The view is particularly relevant to users investigating the ROLLING_FORECAST_FLAG column. That flag is exposed directly from AS_LEAD_LINES_ALL and indicates whether an opportunity line participates in a rolling forecast, which is a repeating forecasting pattern rather than a discrete, one-time forecast entry.
Underlying Base Objects
The documented base objects supporting this view are:
- AS_LEAD_LINES_ALL (accessed through a synonym) — the primary source table supplying opportunity and lead line records, including the
ROLLING_FORECAST_FLAG,FORECAST_DATE, and standard WHO columns. - MTL_SYSTEM_ITEMS_B_KFV — supplied via an outer join to provide concatenated item segments and item description.
- AMS_P_SOURCE_CODES_V — joined twice (aliases AMS1 and AMS2) to resolve campaign and offer names, codes, and identifiers.
- ENI_PROD_DEN_HRCHY_PARENTS_V — joined to derive product category hierarchy information, including concatenated category descriptions, disable dates, and purchase interest.
- HR_OPERATING_UNITS — referenced in the documented dependency list, supporting organizational context through
ORG_ID.
All joins to item and category sources are outer joins, ensuring opportunity lines remain visible even when item or category reference data is unavailable.
Key Columns
LEAD_LINE_ID— primary identifier of the opportunity or lead line.LEAD_ID— the parent lead or opportunity header reference.ROLLING_FORECAST_FLAG— indicates whether the line is associated with a rolling forecast.FORECAST_DATE— the forecast date for the line.QUANTITY,PRICE,TOTAL_AMOUNT— commercial values for the line.INTEREST_STATUS_CODE— the interest or qualification status of the line.CONCATENATED_CAT_DESC— resolved product category hierarchy description.CONCATENATED_SEGMENTSandITEM_DESCRIPTION— item flexfield and description.OFFER_NAME,OFFER_CODE,CAMPAIGN_NAME,CAMPAIGN_CODE— campaign and offer context.ORG_ID— operating unit identifier.
Common Use Cases and Queries
A typical reporting query selects all opportunity lines that participate in a rolling forecast for a given operating unit:
SELECT lead_line_id, lead_id, forecast_date, quantity, total_amount FROM ast_opportunity_lines_v WHERE rolling_forecast_flag = 'Y' AND org_id = :org_id;SELECT lead_id, concatenated_segments, item_description, offer_name, campaign_name FROM ast_opportunity_lines_v WHERE inventory_item_id IS NOT NULL;SELECT interest_status_code, SUM(total_amount) FROM ast_opportunity_lines_v GROUP BY interest_status_code;
These patterns support pipeline valuation, forecast participation tracking, and campaign attribution analysis without requiring joins to multiple underlying tables.
-
View: AST_OPPORTUNITY_LINES_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_OPPORTUNITY_LINES_V, object_name:AST_OPPORTUNITY_LINES_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_OPPORTUNITY_LINES_V ,
-
View: AST_OPPORTUNITY_LINES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AST.AST_OPPORTUNITY_LINES_V, object_name:AST_OPPORTUNITY_LINES_V, status:VALID, product: AST - TeleSales , implementation_dba_data: APPS.AST_OPPORTUNITY_LINES_V ,