Search Results create_project_set




Overview
Explore in AI Chat

Overview

FPA_PORTFOLIO_PROJECT_SETS_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema that supports the Portfolio Analysis (FPA) module, a component of Oracle Projects. Its business purpose is to manage project sets within portfolio analysis planning cycles. A "project set" in this context is a named assembly of projects that the portfolio analysis engine evaluates against scenarios, scoring models, and prioritization criteria. The package encapsulates the low-level create and populate logic for these sets, shielding callers from direct DML against the underlying FPA planning cycle and scenario tables.

The package is classified as PVT (private), meaning it is not part of the public, supported API surface. It is intended for internal use by other FPA packages and by Oracle's own forms and concurrent processing logic rather than by customer extension code. The header comment ($Header: FPAVPRSS.pls 120.1) indicates the file was last revised in 2005, and the package has remained structurally stable across 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented specification exposes two procedures:

  • CREATE_PROJECT_SET — Creates a project set record associated with a given planning cycle. The procedure accepts an API version parameter for standard EBS API versioning and a planning cycle identifier drawn from the FPA_AW_PC_INFO_V view. It returns the standard EBS API out parameters: return status, message data, and message count. This is the entry point invoked when a new portfolio project set must be instantiated for a planning cycle.
  • ADD_PROJECT_SET_LINES — Adds the individual project lines that constitute the membership of a project set. It takes an API version parameter and a scenario identifier from the FPA_AW_SCE_INFO_V view, and likewise returns the standard return status, message data, and message count outputs. This procedure populates the set with the projects selected for evaluation under the specified scenario.

Both procedures follow the conventional Oracle EBS API signature pattern: an input API version, one or more business key inputs, and the three canonical OUT NOCOPY parameters for error propagation and message retrieval via FND_MSG_PUB.

Tables Accessed

The documented metadata does not enumerate the base tables that the package reads or writes, as these are accessed indirectly through APPS synonyms and are not exposed in the ETRM extract. Based on the parameters and the FPA data model, the package operates against the portfolio analysis planning cycle and scenario structures underlying the FPA_AW_PC_INFO_V and FPA_AW_SCE_INFO_V views, together with the project set header and line tables that store set membership. The planning cycle identifier drives the set header creation, while the scenario identifier governs which project lines are added to the set. Because the package is PVT, the precise table list is intentionally not published as a supported interface.

Usage Notes

FPA_PORTFOLIO_PROJECT_SETS_PVT is referenced by two other packages within the Applications schema, confirming its role as an internal utility rather than a standalone entry point. In practice it is invoked from the Portfolio Analysis setup and administration flows — typically through the FPA forms or through higher-level FPA packages that orchestrate planning cycle and scenario processing — rather than being called directly by concurrent programs or customer code.

Because the package is classified PVT, Oracle does not guarantee its signature across patches or upgrades. Developers who have located this package via a search for "create_project_set" should treat it as an internal implementation detail. Customizations requiring project set creation should use the supported FPA public APIs where available, or work through the portfolio analysis forms, instead of invoking CREATE_PROJECT_SET directly. Any direct call must respect the API version convention and must inspect x_return_status and the message stack after each invocation.