Search Results get_scheduled_flag

Overview

PA_PROJECT_PARTIES_UTILS is a PL/SQL utility package in the Oracle EBS Projects (PA) module, defined with AUTHID CURRENT_USER and owned by APPS. It centralizes the validation, retrieval, and maintenance logic that governs project parties — the roles (project manager, customer contact, team member, and similar) assigned to a project through PA_PROJECT_PARTIES. The package enforces business rules around effective dates, overlapping assignments, mandatory fields, scheduling eligibility, and role/resource resolution. A prominent global variable, G_PROJECT_MANAGER_ID, exposes a cached project manager identifier, and the package includes dedicated functions for returning current project manager details and names — the area that most commonly drives searches such as "get_current_project_manager." The package is referenced by 28 other packages, confirming its role as a shared services layer for project party processing across the Projects suite.

Key Procedures and Functions

The documented API exposes 25 procedures and functions. Principal groupings include:

• Project manager functions — GET_PROJECT_MANAGER, GET_PROJECT_MANAGER_NAME, and GET_CURR_PROJ_MGR_DETAILS retrieve the current (or effective) project manager identity and descriptive attributes; VALIDATE_NO_OVERLAP_MANAGER verifies that a proposed manager assignment does not conflict with an existing one.
• Validation logic — VALIDATE_PROJECT_PARTY is the primary validation routine, accepting a validation level, debug mode, object and role identifiers, resource details, and active dates, and returning status along with overlap and assignment action indicators. Supporting validators include VALIDATE_DELETE_PARTY_OK, CHECK_MANDATORY_FIELDS, VALIDATE_DATES, VALIDATE_PERSON_NOT_OVERLAPPED, VALIDATE_ROLE_PARTY, and VALIDATE_SCHEDULE_ALLOWED.
• Lookup/retrieval functions — GET_PROJECT_DATES returns project start and end dates; ACTIVE_PARTY determines whether a party is active within a supplied date range; GET_SCHEDULED_FLAG returns the scheduled flag for a party record; GET_PROJECT_ROLE_ID resolves a role type to a project role; GET_RESOURCE_SOURCE_ID and GET_PERSON_PARTY_ID resolve resource and party identifiers; GET_GRANT_ID and GET_CUSTOMER_PROJECT_PARTY_ID return related surrogate keys; ENABLE_EDIT_LINK reports whether editing is permitted.

Parameter lists are intentionally not reproduced here; callers should consult the package specification for exact signatures and NOCOPY OUT parameters.

Tables Accessed

Through APPS synonyms, the package reads PA_PROJECTS_ALL and PA_PROJECT_STATUSES to establish project validity and date ranges, PA_PROJECT_PARTIES to read and validate party assignments, PA_PROJECT_ROLE_TYPES_B for role definitions, PA_PROJECT_TYPES and PA_PROJECT_TYPES_ALL for project classification-driven behavior, and PER_ALL_PEOPLE_F for person/employee lookups that underpin manager and party resolution. HZ_PARTIES supplies TCA party data, and DUAL is used for singleton evaluations. These tables are accessed primarily for read and validation purposes, with write activity limited to party maintenance flows invoked by callers.

Usage Notes

PA_PROJECT_PARTIES_UTILS is typically invoked from Oracle Forms (project and team member maintenance), from other Projects APIs that need party validation or project manager resolution, and from custom PL/SQL extensions requiring consistent enforcement of party rules. It is not registered as a standalone concurrent program; instead, concurrent and form-based processes reach it indirectly. When integrating, developers should pass a meaningful calling module and validation level, and should honor the returned status, overlap, and assignment action values rather than relying solely on the project manager global variable, which reflects the most recently resolved context.