Search Results pa_projects_maint_pub




Overview
Explore in AI Chat

Overview

PA_PROJECTS_MAINT_PUB is the public maintenance API for Oracle Projects in Oracle E-Business Suite 12.1.1 and 12.2.2. Owned by the APPS schema and classified as a PUB (public) interface, it encapsulates the business logic required to create and maintain project and opportunity records without requiring callers to write directly to the underlying project tables. The package is the supported entry point for programmatic manipulation of the core project entity, covering project header information, customer associations, classifications, staffing assignments, organization roles, and project status transitions.

Because the package is public, it is the contract that Oracle exposes for external and internal consumers. Private implementation packages such as PA_PROJECT_PVT, PA_PROJECT_REQUEST_PVT, and PA_PROJECT_UTILS2 invoke PA_PROJECTS_MAINT_PUB rather than duplicating its logic, and the package calls back into itself recursively for certain maintenance operations. It also depends on PA_INTERFACE_UTILS_PUB, FND_API (the standard Oracle error and message handling framework), FND_TERRITORIES_VL, HR_ORGANIZATION_UNITS, PER_ORGANIZATION_STRUCTURES, and PA_PROJECTS_ALL.

Key Procedures and Functions

The ETRM documentation for 12.2.2 lists eleven documented procedures and functions:

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

Usage Notes

PA_PROJECTS_MAINT_PUB is typically invoked from Oracle Projects forms, concurrent programs, and custom PL/SQL integrations that need to create or modify project data through supported APIs rather than direct DML. The Project Maintenance and Project Request flows route through the related PA_PROJECT_PVT and PA_PROJECT_REQUEST_PVT packages, which in turn call this public API. Customizations that require project creation, customer or classification maintenance, staffing updates, or status changes should call these procedures so that validation, message handling, and audit history remain consistent with standard Oracle Projects behavior. Because the package relies on FND_API for error handling, callers should follow the standard API error-checking pattern after each invocation.