Search Results pa_projects_maint_pvt




Overview
Explore in AI Chat

Overview

PA_PROJECTS_MAINT_PVT is the private implementation package for project maintenance within the Oracle Projects (PA) module of Oracle E-Business Suite. It is owned by the APPS schema, holds a VALID status, and is classified as a PVT (private) API, meaning it is not intended for direct invocation by external or customer-written code. Its public counterpart, PA_PROJECTS_MAINT_PUB, delegates project creation and update operations to this package, which performs the substantive validation and data manipulation work against the underlying Projects tables. The package underpins the core business function of creating and maintaining project records — including basic project definition, classification assignments, customer associations, pipeline information, and staffing attributes — that flow through the Oracle Projects project-maintenance forms and integration points. By separating validation logic from the main processing logic, the package supports consistent rule enforcement across the project lifecycle.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions within this package. They fall into three functional groupings.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. PA_PROJECTS_ALL is the primary project master table and the central target of the create and update operations. PA_PROJECT_CLASSES and the related PA_CLASS_CATEGORIES and PA_CLASS_CODES tables support classification handling. PA_PROJECT_CUSTOMERS and HZ_CUST_ACCOUNTS back the customer association logic. PA_PROJECT_TYPES, PA_PROJECT_STATUSES, PA_PROBABILITY_MEMBERS, PA_BUDGETARY_CONTROL_OPTIONS, PA_IMPLEMENTATIONS, and PA_LOCATIONS supply validation and defaulting reference data. PA_MASS_UPDATE_BATCHES and FND_TERRITORIES_TL are also referenced, the latter for territory-based validation of project attributes.

Usage Notes

Because PA_PROJECTS_MAINT_PVT is a private package, it should not be called directly from custom code. The supported entry point is PA_PROJECTS_MAINT_PUB, which is the only documented package that references it. Internally, the package depends on FND_API for the Oracle Application Object Library API framework (including standard message and return-status handling), PA_INTERFACE_UTILS_PUB for interface utilities, and the STANDARD schema package. Typical invocation occurs through Oracle Projects project-maintenance forms and any concurrent or integration processes that funnel project creation and updates through the public API layer. Customizations that require project maintenance behavior should route through PA_PROJECTS_MAINT_PUB to preserve validation integrity and upgrade safety.