Search Results probability_member_id




Overview

APPS.PA_FCST_PROJ_INFO_V is a lightweight reporting view in the Oracle E-Business Suite Projects (PA) module that joins project master data to forecast probability information. Its purpose is to expose a denormalized, single-row-per-project result set containing the project identifier, functional currency, name, number, and the associated probability percentage. This makes it convenient for forecast and pipeline reporting where a project's weighted value must be derived from a probability factor without requiring the caller to write explicit join logic against the probability tables.

The view is defined in the APPS schema and is owned by APPS, consistent with standard EBS object ownership. Because it is a view rather than a table, it carries no storage of its own and always reflects the current state of its two underlying base objects. In the context of the ETRM (Electronic Technical Reference Manual) for releases 12.1.1 and 12.2.2, the view is documented with a straightforward two-table definition and no additional PL/SQL logic.

Underlying Base Objects

The ETRM metadata lists two referenced base objects, both accessed through synonyms:

  • PA_PROJECTS_ALL (SYNONYM) — the primary project definition table, aliased as P1 in the view text. It supplies the project_id, projfunc_currency_code, name, and segment1 columns.
  • PA_PROBABILITY_MEMBERS (SYNONYM) — the probability lookup table, aliased as P2, supplying the probability_percentage column.

The join is expressed as p1.probability_member_id = p2.probability_member_id(+). This is an outer join on the probability side, meaning every project row is returned even when no matching probability member exists. This is significant for reporting because projects without an assigned probability member will still appear, with prob_per returning NULL. The presence of the probability_member_id column on PA_PROJECTS_ALL is the linkage that allows each project to be associated with exactly one probability member and therefore one probability percentage.

Key Columns

  • project_id — Surrogate primary key of the project, sourced from PA_PROJECTS_ALL.project_id. Used to join to other project-related views and tables.
  • project_currency — The project functional currency code (PA_PROJECTS_ALL.projfunc_currency_code), indicating the currency in which project amounts are held.
  • project_name — The descriptive name of the project (PA_PROJECTS_ALL.name).
  • project_num — The project number (PA_PROJECTS_ALL.segment1), the user-visible project identifier.
  • prob_per — The probability percentage from PA_PROBABILITY_MEMBERS.probability_percentage. This is the forecast weighting factor. Because of the outer join it may be NULL when the project has no probability member assigned.

The column name probability_member_id that a user might search for does not appear as a projected column in the view; it exists only as the join key on the underlying PA_PROJECTS_ALL table. Users searching on that term are typically looking for how probability is resolved for a project, and this view is the exposed result of that resolution.

Common Use Cases and Queries

Typical scenarios include pipeline reports showing weighted forecast amounts, project listings requiring the probability multiplier, and integrations that need a compact project-plus-probability dataset.

SELECT project_num,
       project_name,
       project_currency,
       prob_per,
       NVL(prob_per, 0) / 100 AS prob_factor
FROM   apps.pa_fcst_proj_info_v;

To identify projects lacking a probability assignment (a common data-quality check):

SELECT project_id, project_num, project_name
FROM   apps.pa_fcst_proj_info_v
WHERE  prob_per IS NULL;

Because the view is a simple join of two base objects and exposes only five columns, it should be treated as a convenience layer. For broader project forecasting needs, it is generally joined back to PA_PROJECTS_ALL or to forecast amount tables using project_id. All access should respect standard EBS security and the APPS schema synonym.