Results for “add_project_set_lines”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The package body APPS.FPA_PORTFOLIO_PROJECT_SETS_PVT is a private PL/SQL implementation unit within the Oracle E-Business Suite applications schema. It belongs to the Portfolio Analysis (FPA) product family, which provides functionality for grouping projects into portfolios and project sets so that management can evaluate performance across aggregated collections of capital and non-capital projects. A project set in this context represents an ordered, reusable grouping of projects that can be assigned to a portfolio for analysis, budgeting, and reporting purposes.

The "_PVT" suffix denotes that this is a private package body, meaning its procedures and functions are intended to be invoked by sibling public APIs and other internal application logic within the FPA schema rather than directly by external or customer-written code. The body encapsulates the core insert, validation, and association logic that supports higher-level public packages and forms. According to the ETRM metadata, the object holds a status of INVALID, which indicates the compiled body is in a non-executable state and must be recompiled before it can be relied upon at runtime.

Key Procedures and Functions

The documented metadata identifies two procedures within this package body:

  • CREATE_PROJECT_SET — Creates a new project set definition within the FPA data model, establishing the header record that subsequent project membership can be attached to. It is the entry point for establishing a new named set of projects used in portfolio analysis.
  • ADD_PROJECT_SET_LINES — Adds individual project entries (lines) to an existing project set, associating specific projects with the parent set. This enables incremental population of a set after the header has been created.

No parameter lists are documented in the ETRM extract, and the metadata does not enumerate the detailed signatures of these units. The package body is documented as being referenced by two other database objects, confirming that it operates as an internal dependency rather than a standalone public API.

Tables Accessed

The ETRM metadata excerpt does not explicitly list the base tables referenced by APPS.FPA_PORTFOLIO_PROJECT_SETS_PVT, and it notes that the package is not itself referenced by any database object in the dependency view captured. Functionally, a package of this nature would be expected to operate against the FPA project set definition and line tables together with their underlying synonyms exposed in the APPS schema, writing the header records produced by CREATE_PROJECT_SET and the member project rows produced by ADD_PROJECT_SET_LINES. Because the documented excerpt omits explicit table names, any specific table identification should be confirmed by inspecting the package source and its dependency tree at the site.

Usage Notes

Because this is a private package body (classification PVT), it is not intended for direct invocation by end users, forms, or customer extensions. It is typically called from within the FPA module's public APIs and internal processing logic — for example, when a user or concurrent program defines a new project set or appends projects to an existing one through the Portfolio Analysis application. The documented fact that it is referenced by two other packages reinforces this role as a supporting implementation layer.

The INVALID status recorded in the metadata is operationally significant: any dependent public package or concurrent program that relies on this body may fail or raise compilation errors until the body is successfully recompiled. Administrators should run the standard AD compile utilities or recompile the package body after upgrades or patches to restore validity. Given the limited documented metadata, developers requiring precise behavior should review the actual package source and the objects that reference it before integrating with it.