Search Results as_opp_worksheet_lines




Overview

The AS_OPP_WORKSHEET_LINES table is a core data structure within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It serves as the primary repository for storing detailed forecast information related to sales opportunities, which are managed within the forecasting worksheets. This table is essential for the sales forecasting and pipeline management functionality, enabling the system to track and analyze potential revenue from opportunities at a granular level, whether assigned to an individual salesperson or a sales group. Its existence is critical for generating accurate sales forecasts, managing quotas, and analyzing sales performance against targets in releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores transactional forecast data for each opportunity line linked to a forecast worksheet. While the full column list is not provided in the excerpt, the documented foreign key relationships reveal several critical data points. The primary key is a composite of FORECAST_WORKSHEET_ID and another column, likely a line identifier. Key foreign key columns include LEAD_ID, which links to the originating lead in AS_LEADS_ALL; SALES_STAGE_ID, which references the current stage in the sales cycle from AS_SALES_STAGES_ALL_B; CUSTOMER_ID, which links to the party record in HZ_PARTIES; and STATUS, which references the status code in AS_STATUSES_B. The table would also typically contain columns for forecast amounts, probabilities, close dates, product or service details, and revenue recognition attributes.

Common Use Cases and Queries

This table is central to sales operations reporting and forecasting analysis. Common use cases include generating a detailed forecast report for a specific sales representative, analyzing pipeline health by sales stage, and calculating weighted forecast values. A typical query might join this table to its related dimensions to produce a comprehensive pipeline view. For example:

  • Retrieving all opportunity lines for a specific forecast worksheet to review or adjust forecasts.
  • Aggregating forecast amounts by sales stage to assess pipeline distribution.
  • Comparing forecasted revenue against actual bookings for performance analysis.
  • Identifying opportunities stuck in a particular stage for follow-up actions.

A sample SQL pattern would involve joining AS_OPP_WORKSHEET_LINES to AS_FORECAST_WORKSHEETS, AS_SALES_STAGES_ALL_B, and HZ_PARTIES to enrich the raw line data with descriptive information.

Related Objects

The AS_OPP_WORKSHEET_LINES table is integral to the Sales Foundation data model, with documented foreign key relationships to several key tables. These relationships enforce data integrity and define the table's context within the application.

  • AS_FORECAST_WORKSHEETS: The parent table. Each line must belong to a forecast worksheet, joined via FORECAST_WORKSHEET_ID.
  • AS_LEADS_ALL: Links the opportunity line back to its source lead, joined via LEAD_ID.
  • AS_SALES_STAGES_ALL_B: Provides the definition for the opportunity's current sales stage, joined via SALES_STAGE_ID.
  • HZ_PARTIES: Provides the customer or prospect information, joined via CUSTOMER_ID.
  • AS_STATUSES_B: Defines the status code (e.g., Open, Closed Won) for the opportunity line, joined via the STATUS column.