Search Results pa_probability_lists




Overview
Explore in AI Chat

Overview

PA_PROBABILITY_LISTS is a foundational configuration table within the Oracle Projects (PA) module of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. The table stores the probability lists that are used in Oracle Projects — named, reusable collections of probability values and their associated win percentages that drive opportunity and pipeline forecasting throughout the project lifecycle. Rather than holding the individual probability values themselves, this header table defines the list identity, its validity window, and its descriptive and descriptive-flexfield attributes; the individual probability entries are held in a dependent detail table.

The documented physical schema exposes 26 columns owned by the PA schema, with a surrogate primary key constraint named PA_PROBABILITY_LISTS_PK and a unique index PA_PROBABILITY_LISTS_U1 enforcing uniqueness on NAME. The surrogate key column PROBABILITY_LIST_ID is the technically correct join path, while NAME serves as the business-key candidate exposed to users through the Projects setup and forecasting interfaces. The ETRM metadata classifies this object heuristically as standalone under the Data Vault model, indicating that it is not dependent on an upstream foreign key relationship for its identity. In practice it behaves as a reference-data hub: the list identity (PROBABILITY_LIST_ID) is the durable business key, while the descriptive, date-effective, and attribute columns constitute the satellite payload around that hub.

Key Information Stored

The most consequential columns fall into four groups. Identity and business key columns are PROBABILITY_LIST_ID, the system-generated surrogate primary key, and NAME, the user-facing name enforced by the PA_PROBABILITY_LISTS_U1 unique index. Descriptive content is carried by DESCRIPTION and the seeded ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns, which allow administrators to extend the list definition without a schema change.

  • PROBABILITY_LIST_ID — surrogate primary key and the column referenced by dependent probability detail records.
  • NAME — business-key candidate, uniquely indexed, and the value users recognize when assigning a list to a project or opportunity.
  • DESCRIPTION — free-text explanation of the list's purpose or scope.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective dating window that governs whether the list is selectable in setup and forecasting screens for a given transaction date.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit trail identifying who created or last modified the record and through which login.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values used for customer-specific extensions.

Note that the win-percentage values themselves are not stored here; they reside in the associated probability detail table keyed by PROBABILITY_LIST_ID.

Common Use Cases and Queries

Typical usage centers on setup validation, list-of-values construction, and forecasting/reporting joins. A standard pattern retrieves only currently active lists:

  • Active list lookup: SELECT probability_list_id, name, description FROM pa_probability_lists WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));
  • Duplicate-name validation before creating a setup record, since NAME is uniquely indexed.
  • Forecasting reports that join the list header to its probability detail rows to derive weighted pipeline values by project or opportunity.
  • Audit and change-tracking extracts using LAST_UPDATE_DATE, LAST_UPDATED_BY, and CREATION_DATE to identify recently maintained configuration.
  • Flexfield reporting that pivots ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 for client-specific categorizations.

Related Objects

The ETRM metadata reports no outbound foreign keys, consistent with its standalone classification. Dependencies are therefore inbound: the probability detail table that holds individual entries per list, joined on PROBABILITY_LIST_ID; project- and opportunity-level tables that carry a PROBABILITY_LIST_ID reference; and the standard EBS descriptive flexfield definition tables that resolve ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15. The Projects setup and forecasting concurrent programs and forms read this table to populate probability list list-of-values. Reports and extracts should join on PROBABILITY_LIST_ID rather than NAME, and should apply the START_DATE_ACTIVE / END_DATE_ACTIVE filter to reflect the same effective dating the application enforces.