Search Results pa_project_sets_pvt




Overview
Explore in AI Chat

Overview

PA_PROJECT_SETS_PVT is a private PL/SQL package in the APPS schema that implements the core business logic for maintaining project sets in Oracle EBS Projects. A project set is a named grouping of projects that allows users to build and save a reusable list of projects for reporting, inquiry, and processing purposes — for example, defining a set of projects to be run through a concurrent report or an inquiry screen in Oracle Projects.

The package is classified as a PVT (private) API, meaning it is intended to be called by other Oracle Projects packages rather than directly by external or customer code. Its status is VALID in both 12.1.1 and 12.2.2 releases, and the documented metadata confirms it references the base tables PA_PROJECT_SETS_B, PA_PROJECT_SETS_TL, PA_PROJECT_SET_LINES and HZ_PARTIES, and is referenced by PA_PROJECT_SETS_PUB, PA_PROJECT_CORE and PA_PROJECT_SETS_PVT itself. This dependency pattern confirms that PA_PROJECT_SETS_PUB is the public wrapper through which the application and custom code should access the same functionality.

Key Procedures and Functions

The ETRM metadata documents six procedures/functions in this package:

  • CREATE_PROJECT_SET — Creates a new project set header, inserting the base row in PA_PROJECT_SETS_B and the corresponding translated name/description row in PA_PROJECT_SETS_TL.
  • UPDATE_PROJECT_SET — Modifies the attributes of an existing project set, updating the base and translated records as required.
  • DELETE_PROJECT_SET — Removes a project set definition, including its header and associated lines.
  • CREATE_PROJECT_SET_LINE — Adds a project to an existing project set by inserting a record in PA_PROJECT_SET_LINES.
  • DELETE_PROJECT_SET_LINE — Removes a single project line from a project set by deleting the corresponding PA_PROJECT_SET_LINES row.
  • DELETE_PROJ_FROM_PROJ_SET — An alternate/legacy routine that removes a project from a project set, typically invoked from project-set maintenance flows.

Parameter lists are not reproduced here because they are not part of the documented metadata; callers should obtain signatures from the package specification in the database or from the companion public package PA_PROJECT_SETS_PUB.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

  • PA_PROJECT_SETS_B — the base (non-translated) project set header; stores set identifiers and attributes used by the APIs.
  • PA_PROJECT_SETS_TL — the translation table holding the language-specific name and description of each project set.
  • PA_PROJECT_SET_LINES — the detail table mapping individual projects to a project set; inserted and deleted by the line-level procedures.
  • HZ_PARTIES — the Trading Community Architecture party table, referenced for validation/lookup of party-related information associated with the project set.
  • PLITBLM — a standard Oracle Projects PL/SQL index table type (table-of-varchar2) used as a PL/SQL collection rather than a database table; it appears in the dependency list because the package declares parameters or variables of this type.

Usage Notes

PA_PROJECT_SETS_PVT is a private implementation package and should not normally be invoked directly from custom code. It is called by PA_PROJECT_SETS_PUB (the documented public API layer) and by PA_PROJECT_CORE, which drives project-set creation and maintenance from Oracle Projects forms and internal processing routines. Typical invocation paths include:

  • Oracle Projects forms where users define, update, or delete a project set and add or remove projects within it.
  • Concurrent programs or report flows that persist or retrieve project sets used as report selection criteria.
  • Other Oracle Projects packages that require project-set validation or line maintenance as part of a larger transaction.

Custom integrations requiring project-set functionality should call PA_PROJECT_SETS_PUB rather than this private package, to remain aligned with Oracle's supported API surface. Because the package is marked VALID and its dependencies are stable in 12.1.1 and 12.2.2, the same call patterns apply across both releases; the only significant structural difference in 12.2.2 is the underlying file system/online patching architecture, which does not alter this package's PL/SQL contract. Direct dependencies on private packages should be avoided where an equivalent public API exists, as Oracle may change private signatures without notice in future patches or upgrades.