Search Results okx_opp_win_prob_v

Overview

The OKX_OPP_WIN_PROB_V view is a reporting and integration object owned by the APPS schema within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKX - Contracts Integration product family and is documented with the description "Forecast Probability." The view is defined over the forecast probability reference data used by Oracle Sales / Contracts Integration, and its purpose is to expose the translation-resolved meaning of each probability value alongside its business attributes. In practice, the view presents the list of forecast probability values that can be attached to an opportunity or lead to indicate the likelihood of a win. Because it resolves the language-specific MEANING column at runtime, it supports multilingual reporting without requiring the calling application to join the translation table explicitly. The view is reported as VALID, meaning it is compiled and available for querying in a standard EBS installation.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• AS_FORECAST_PROB_ALL_B — the base table holding the language-independent forecast probability definitions, aliased as B in the view text.
• AS_FORECAST_PROB_ALL_TL — the translation table holding the language-specific display text, aliased as T in the view text.

The join condition links the two tables on PROBABILITY_VALUE (B.PROBABILITY_VALUE = T.PROBABILITY_VALUE) and restricts the translation rows using T.LANGUAGE = USERENV('LANG'). This means the view returns exactly one translation row per probability value, matching the language of the current database session. All descriptive attributes are drawn from the base table B, while the user-facing MEANING comes from the translation table T.

Key Columns

• PROBABILITY_VALUE — the numeric identifier for the forecast probability; the primary join key between the base and translation tables.
• MEANING — the translated display name of the probability, resolved for the current session language via USERENV('LANG').
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the probability value is valid for use.
• ENABLED_FLAG — indicates whether the probability value is currently active and selectable.
• LEAD_STATUS_CHANGE_CODE — the lead status code that should be applied when this probability is assigned.
• ORG_ID — the operating unit / organization identifier, supporting multi-org data partitioning.
• USAGE_INDICATOR — the indicator that distinguishes how the probability value is intended to be used, and the specific column the user searched for. It allows consumers of the view to filter probability values by their usage context.
• INTERNAL_UPGRADE_PROB_VALUE — the corresponding probability value used for internal upgrade forecast scenarios.

Common Use Cases and Queries

The view is typically used to populate list-of-values (LOV) queries, validation logic, and operational reports that need a localized list of active forecast probabilities. A common requirement is to restrict the result set to enabled probability values applicable to a given organization:

SELECT probability_value, meaning, usage_indicator, lead_status_change_code
FROM apps.okx_opp_win_prob_v
WHERE enabled_flag = 'Y'
AND org_id = :p_org_id
ORDER BY probability_value;

Where the usage_indicator is the attribute of interest, a targeted filter is often applied to isolate probability values belonging to a particular usage category:

SELECT probability_value, meaning, usage_indicator
FROM apps.okx_opp_win_prob_v
WHERE usage_indicator = :p_usage_indicator
AND enabled_flag = 'Y';

Because the view already resolves the translated MEANING, it is also well suited to reports that must render probability descriptions in the user's session language without additional joins to AS_FORECAST_PROB_ALL_TL. Note that USERENV('LANG') is evaluated from the session environment, so the language returned depends on the NLS configuration of the connecting session. As a view, OKX_OPP_WIN_PROB_V is read-only; it should not be used as a target for DML, and any maintenance of the underlying forecast probability setup must be performed against the base tables through the supported application forms.