Search Results usage_indicator




Overview
Explore in AI Chat

Overview

AS_SALES_STAGES is an APPS-owned reporting view in the Oracle E-Business Suite Sales Foundation (AS) product family. It exposes the defined sales stages — the ordered milestones a sales opportunity progresses through, such as qualification, proposal, negotiation, and closed/won — together with the probability ranges that govern each stage. The view is described in the ETRM metadata as "Sales stages (single org, no MLS columns)," indicating that it is a single-organization, non-Multi-Lingual-Support projection of the underlying sales stage data. It therefore presents stage definitions as they exist for the operating unit context established at query time, without the language-specific columns that would otherwise be required for translated names and descriptions.

The search term "min_win_probability" maps directly to a column exposed by this view. MIN_WIN_PROBABILITY and its companion MAX_WIN_PROBABILITY together define the win-probability band associated with a sales stage. These values are used by opportunity management and forecasting logic to derive expected revenue and to default or validate the win probability recorded against an opportunity at a given stage. Because the view is read-only and defined over the base table, it is the appropriate access point for custom reports, conversions, and integrations that need stage definitions without touching the underlying transactional structures.

Underlying Base Objects

The view is defined over a single documented base object: AS_SALES_STAGES_ALL_B, accessed through a synonym. The view text is a straightforward projection of the base table's columns, filtered implicitly to a single organization by the absence of MLS and translation joins. The column list runs from SALES_STAGE_ID and the standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) through NAME, MIN_WIN_PROBABILITY, MAX_WIN_PROBABILITY, ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE, DESCRIPTION, ORG_ID, the fifteen ATTRIBUTE descriptor columns, USAGE_INDICATOR, and INTERNAL_UPGRADE_STAGE_ID.

Because the view is a direct projection rather than a join, there is a one-to-one correspondence between its rows and rows in AS_SALES_STAGES_ALL_B. The "_B" suffix on the base table denotes a base (non-translated) table in the EBS Multi-Lingual Support convention; the corresponding "_TL" table holds translated name and description values. This view deliberately excludes those translations, which is consistent with its stated purpose as a single-org, non-MLS view.

Key Columns

  • SALES_STAGE_ID — Primary identifier for the sales stage; used as the foreign key in opportunity and pipeline records.
  • NAME — The stage name as defined in the base (non-translated) table.
  • MIN_WIN_PROBABILITY / MAX_WIN_PROBABILITY — The lower and upper bounds of the win-probability band for the stage. These are the columns relevant to the user's search and are central to forecast weighting.
  • ENABLED_FLAG — Indicates whether the stage is active and selectable.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range during which the stage is valid.
  • ORG_ID — Operating unit identifier, supporting the single-org projection.
  • USAGE_INDICATOR — Distinguishes the intended usage context of the stage.
  • INTERNAL_UPGRADE_STAGE_ID — Reference to a related stage used during internal upgrade or migration processing.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns for customer-defined extensions.

Common Use Cases and Queries

Typical uses include building sales-stage lookup lists for opportunity entry forms, joining stage definitions to opportunity pipelines to weight forecasts, and validating that a recorded win probability falls within the stage's band. A minimal query returning the win-probability bands is:

SELECT sales_stage_id, name, min_win_probability, max_win_probability
FROM apps.as_sales_stages
WHERE enabled_flag = 'Y'
ORDER BY min_win_probability;

To restrict results to stages active as of the current date, add SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE). Because the view is single-org and non-MLS, joins to translated tables are not required, but queries spanning multiple operating units should filter on ORG_ID explicitly.