Search Results do_lines_exist

Overview

APPS.PA_PROJECT_SET_UTILS is a utility package body within the Oracle E-Business Suite Projects (PA) module. It provides a centralized set of reusable PL/SQL routines for managing and validating project sets — the named groupings of projects used across Oracle Projects for reporting, costing, billing, and security scoping. Rather than embedding this logic in individual forms or concurrent programs, the package consolidates common operations such as resolving a user to a party identity, retrieving the lines of a project set, checking whether a set already contains lines, verifying security access to a set, validating unique names, and adding projects to an existing set.

The header comment $Header: PAPPSUTB.pls 120.2.12000000.2 2007/10/09 ...$ indicates the package has been stable since the 11i/R12 era and is shipped with later releases including 12.1.1 and 12.2.2 essentially unchanged. Its classification of OTHER reflects that it is an internal support package rather than a published public API, though it remains callable from custom code in APPS.

Key Procedures and Functions

• GETPARTYIDNAME — Returns the party_id and party_name for a given FND_USER user_id, resolving the user first through PER_ALL_PEOPLE_F / HZ_PARTIES when they are an employee, and otherwise through HZ_PARTIES using the person_party_id. It is the foundational identity-resolution helper used by the security and validation routines.
• GET_PROJECT_SET_LINES — Returns the collection of lines belonging to a specified project set as a PL/SQL table type, enabling callers to iterate or validate the contents of a set.
• DO_LINES_EXIST — Determines whether a given project set already has one or more lines. This is the routine the user searched for; it is typically used as a guard before insert or delete operations on a set.
• CHECK_PROJECTS_IN_SET — Validates that specified projects belong to (or can be added to) a given project set.
• CHECK_SECURITY_ON_SET — Verifies that the current user has security access to a specified project set, supporting Projects security profiles.
• IS_NAME_UNIQUE — Confirms that a proposed project set name is not already in use.
• GET_PROJ_SET_NAME — Retrieves the name of a project set, typically from PA_PROJECT_SETS_TL for the appropriate language.
• ADD_PROJECTS_TO_PROJ_SET — Inserts project lines into a project set, the principal write operation in the package.
• CHECK_PARTYNAME_OR_ID — Validates a supplied party name or identifier, used during set ownership or security checks.
• CHECK_PROJECTSETNAME_OR_ID — Validates a supplied project set name or identifier before further processing.
• IS_PARTY_INTERNAL — Determines whether a party is an internal (employee) party, which affects security and visibility rules.

Tables Accessed

The package reads and writes the core project-set tables, chiefly PA_PROJECT_SETS_B (the base set definition) and PA_PROJECT_SET_LINES (the projects contained in each set), with PA_PROJECT_SETS_TL supplying translated set names. FND_USER is queried to map the session user to an employee or person party. HZ_PARTIES and PER_ALL_PEOPLE_F provide party and person attributes for identity resolution. PA_PROJECTS_ALL is accessed to validate that referenced projects are valid and available. PLITBLM is referenced for PL/SQL table operations.

Usage Notes

PA_PROJECT_SET_UTILS is invoked primarily from Oracle Projects forms and concurrent programs that create, populate, or query project sets, and it is referenced by at least four other packages, indicating a shared internal dependency. Custom code in APPS should treat the package as internal rather than a guaranteed public API; callers should rely on the documented routines above and avoid assuming specific parameter signatures beyond the documented behavior. Because the package enforces both name uniqueness and security-on-set checks, it is the appropriate entry point whenever custom logic must add projects to a set or confirm access before exposing set contents.