Search Results lead_status_change_code




Overview
Explore in AI Chat

Overview

The AS_FORECAST_PROB view is a Sales Foundation (AS) dictionary object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents forecast probability configuration data — the seeded and user-defined probability values that sales organizations attach to forecast line items to express the likelihood that an opportunity will close. The view is classified as VALID in ETRM and is explicitly documented as a single-organization view with no MLS (Multi-Lingual Support) columns, meaning it does not join to the language-specific translation table that its "_TL" counterparts would use.

Because the object is a view rather than a table, it is intended primarily for reporting, inquiry, and integration purposes. It exposes a denormalized, organization-scoped read of the forecast probability model without requiring the caller to resolve the underlying base table or the translation mechanism themselves. This makes it convenient for custom concurrent programs, BI Publisher data templates, OAF-based inquiry pages, and outbound interfaces that need to reference forecast probability definitions by organization.

Underlying Base Objects

The view is defined over a single documented base object, AS_FORECAST_PROB_ALL_B, referenced through a synonym. The "_ALL_" segment in the base table name indicates that the underlying entity is partitioned by operating unit via ORG_ID, while the "_B" suffix denotes the base (non-translated) table in an MLS pair. The view text selects the standard WHO columns plus the business columns from that base table and projects them into the APPS schema under a fixed name.

Because AS_FORECAST_PROB is a thin projection over AS_FORECAST_PROB_ALL_B, no additional filtering predicates are documented in the provided metadata. The single-org designation reflects that the view itself does not carry a language or MLS join; organization scoping is achieved through the ORG_ID column that is carried through from the base table.

Key Columns

  • PROBABILITY_VALUE — The numeric probability associated with the forecast probability record, expressed as the win likelihood assigned to an opportunity or forecast line.
  • MEANING — The descriptive name of the probability record as presented to users.
  • LEAD_STATUS_CHANGE_CODE — Identifies the lead status transition associated with the probability. This is the column most directly relevant to the search term lead_status_change_code; it links the forecast probability definition to a lead status change event, allowing the system to infer or assign probability when a lead or opportunity advances stages.
  • ENABLED_FLAG — Indicates whether the probability record is active and selectable.
  • USAGE_INDICATOR — Distinguishes how the probability record is intended to be used within forecast processing.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Define the effective date range during which the probability record is valid.
  • ORG_ID — The operating unit that owns the probability definition.
  • INTERNAL_UPGRADE_PROB_VALUE — An internal column used during upgrade processing to preserve prior probability values.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle flexfield attribute columns for descriptive or extensible data capture.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried when building reporting on forecast probability configuration, when validating which probability values are active for an operating unit, or when tracing how lead status changes map to probability assignments.

Listing all enabled probabilities for a given organization:

  • SELECT probability_value, meaning, lead_status_change_code FROM apps.as_forecast_prob WHERE enabled_flag = 'Y' AND org_id = :org_id;

Identifying the probability associated with a specific lead status change:

  • SELECT probability_value, meaning FROM apps.as_forecast_prob WHERE lead_status_change_code = :code AND enabled_flag = 'Y' AND org_id = :org_id;

Reviewing effective-dated records:

  • SELECT meaning, probability_value, start_date_active, end_date_active FROM apps.as_forecast_prob WHERE org_id = :org_id AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

These queries support inquiry pages, integration extracts, and validation routines that must respect the organization scoping and effective dating carried through from AS_FORECAST_PROB_ALL_B.