Search Results probability_list_id

Overview

PA_PROBABILITIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) product family. It presents project win-probability configuration data in a denormalized, business-friendly form by joining probability member records to their parent probability lists. The view is documented as VALID and is available in both EBS 12.1.1 and 12.2.2.

In project and proposal management, win probabilities are used to weight forecast revenue and pipeline amounts, most notably in Project Billing, Project Resource Management, and opportunity/pipeline reporting. Administrators define one or more probability lists, each containing members that pair a textual description with a numeric percentage. Rather than exposing the raw numeric foreign keys required to reconstruct that hierarchy, PA_PROBABILITIES_V flattens the relationship so that each row carries both the member-level attributes and the descriptive name of its list. This makes it suitable for concurrent program extracts, Oracle Reports, XML Publisher templates, and custom OAF or ADF integrations where a readable list name is required without a secondary lookup.

Underlying Base Objects

The view text defines a two-table equijoin. The documented referenced base objects are PA_PROBABILITY_LISTS and PA_PROBABILITY_MEMBERS, both exposed to APPS as synonyms. PA_PROBABILITY_MEMBERS supplies the member-level rows, while PA_PROBABILITY_LISTS supplies the parent list header. The join predicate is:

• MB.PROBABILITY_LIST_ID = LIST.PROBABILITY_LIST_ID

Because the join is an inner equijoin on the list identifier, a member row is returned only when its parent list row exists. Orphaned members, if any were ever created, would be excluded. The view performs no filtering on enabled/disabled flags, effective dates, or attribute columns; all rows present in the member table are surfaced. No aggregation, DISTINCT, or outer join is applied, so the row grain is one row per probability member.

Key Columns

The view exposes six columns, aliased in the view text as follows:

• PROBABILITY_MEMBER_ID — Primary identifier of the individual probability member (from MB.PROBABILITY_MEMBER_ID). Unique per member row.
• PROBABILITY_PERCENTAGE — The numeric win probability assigned to that member, from MB.PROBABILITY_PERCENTAGE. This is the value consumed by weighted pipeline calculations.
• PROBABILITY_DESC — The description of the member, sourced from MB.DESCRIPTION. Typically a label such as "High", "Medium", "Low", or a percentage range descriptor.
• PROBABILITY_LIST_ID — Identifier of the parent probability list (from LIST.PROBABILITY_LIST_ID). Serves as the grouping key linking multiple members into one list.
• PROBABILITY_LIST_NAME — The user-defined name of the parent list (LIST.NAME). This is the primary reason the view exists, since it removes the need to join to the list table separately.
• PROBABILITY_LIST_DESC — The description of the parent list (LIST.DESCRIPTION).

Callers should be aware that both the list description and member description are surfaced under distinct aliases, avoiding the column-name collision that a direct join would produce.

Common Use Cases and Queries

Typical scenarios include populating a value set or LOV of valid probabilities for a project or opportunity form, extracting probability configuration for migration between instances, and validating that the percentages within a list sum to 100. A representative query returning all members for all lists:

• SELECT probability_list_name, probability_desc, probability_percentage FROM apps.pa_probabilities_v ORDER BY probability_list_name, probability_percentage;
• SELECT probability_member_id, probability_percentage FROM apps.pa_probabilities_v WHERE probability_list_id = :p_list_id;
• SELECT probability_list_id, SUM(probability_percentage) FROM apps.pa_probabilities_v GROUP BY probability_list_id HAVING SUM(probability_percentage) <> 100;

Because the object is a view rather than a table, it is read-only and must be queried through the APPS schema (or a synonym granted to a custom schema). It is not partitioned and carries no WHO columns, so it cannot be used for audit or change tracking. For that, the base tables PA_PROBABILITY_MEMBERS and PA_PROBABILITY_LISTS must be queried directly.