Search Results get_proj_set_name




Overview
Explore in AI Chat

Overview

PA_PROJECT_SET_UTILS is a utility package in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and classified as an "OTHER" API. Its central purpose is to support the creation, validation, and maintenance of project sets — named groupings of projects that are used throughout Oracle Projects for reporting, portfolio analysis, security scoping, and search filtering. Rather than exposing a transactional business flow, PA_PROJECT_SET_UTILS provides the low-level validation and lookup routines that higher-level set management packages depend upon.

The package is tightly coupled to the core project set tables PA_PROJECT_SETS_B and PA_PROJECT_SET_LINES, and it relies on FND_API and FND_GLOBAL for standard API error handling and session context. Its status is VALID in the documented ETRM 12.2.2 metadata. Dependency information confirms that the package both consumes and is consumed by other project set components, indicating it sits in the middle of the project set subsystem rather than at its edge.

Key Procedures and Functions

The package documents eleven procedures and functions. Their names indicate a mix of validation, retrieval, and mutation operations:

  • GET_PROJECT_SET_LINES — returns the set lines (projects) belonging to a given project set.
  • DO_LINES_EXIST — determines whether a project set already contains any lines, typically used before allowing deletion or modification.
  • CHECK_PROJECTS_IN_SET — validates whether specified projects are present in a project set.
  • CHECK_SECURITY_ON_SET — applies Projects security rules to a project set, confirming the caller may access it.
  • IS_NAME_UNIQUE — verifies that a proposed project set name is not already in use.
  • GET_PROJ_SET_NAME — retrieves the name of a project set from its identifier.
  • ADD_PROJECTS_TO_PROJ_SET — the principal mutation routine, inserting projects as lines into an existing set.
  • CHECK_PROJECTSETNAME_OR_ID — resolves and validates a project set supplied either by name or by internal ID.
  • CHECK_PARTYNAME_OR_ID — validates a party (customer or organization) referenced by name or ID.
  • GETPARTYIDNAME — returns the identifier and name of a party.
  • IS_PARTY_INTERNAL — determines whether a party is an internal organization, which affects eligibility for certain project sets.

No parameter lists are documented, so callers should obtain signatures from the package specification in the APPS schema.

Tables Accessed

The package operates across several documented tables accessed through APPS synonyms:

  • PA_PROJECT_SETS_B — the base table holding project set definitions.
  • PA_PROJECT_SET_LINES — the child table holding individual project-to-set assignments.
  • PA_PROJECT_SETS_TL — the translation table supplying set names and descriptions.
  • PA_PROJECTS_ALL — the master project table, used to validate project membership.
  • FND_USER and PER_ALL_PEOPLE_F — used for security and party resolution.
  • HZ_PARTIES — TCA party records underpinning the party validation routines.
  • PLITBLM — a PL/SQL index-by table type used for bulk collection handling.

Usage Notes

PA_PROJECT_SET_UTILS is not typically invoked directly by end users. It is referenced by four documented packages — FPA_PORTFOLIO_PROJECT_SETS_PVT, FPA_PROCESS_PVT, PA_PROJECT_SEARCH_UTILS, and PA_PROJECT_SETS_PVT — and is also referenced by the PA_PROJECT_SETS_V view. This means it fires indirectly during portfolio set maintenance, project search operations, and any private API that constructs or validates project sets. Custom extensions that must create or validate project sets should prefer the public PA_PROJECT_SETS_PVT API where available, treating PA_PROJECT_SET_UTILS routines such as ADD_PROJECTS_TO_PROJ_SET as internal building blocks. Because the package enforces security through CHECK_SECURITY_ON_SET, FND_GLOBAL context must be initialized before invocation.