Search Results delete_project_party

Overview

PA_PROJECT_PARTIES_PUB is a public PL/SQL API package in the Oracle E-Business Suite Projects (PA) module. It encapsulates the business logic required to create, maintain, and remove project party assignments — the association of a resource (typically an employee, supplier contact, or other party) with a project role on a specific project. Project parties underpin key member and role-based functionality, including project management, progress rollup, and workflow-driven notifications. The package exposes a controlled, validated API surface so that callers do not write directly to the underlying PA_PROJECT_PARTIES table, and it returns standard FND_API message and return-status information consistent with the EBS PL/SQL API framework. The header revision ($Header: PARPPPMB.pls 120.5 2008/04/18) indicates a long-standing, stable interface carried forward into 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents five entry points in this package:

• CREATE_PROJECT_PARTY — Creates a new project party record, applying validation of the project, role, resource, and date range before inserting into PA_PROJECT_PARTIES. It also determines workflow routing information that is returned to the caller for downstream processing.
• UPDATE_PROJECT_PARTY — Modifies an existing project party, permitting changes to role, resource, or effective dates while preserving validation and workflow consistency.
• DELETE_PROJECT_PARTY — Removes a project party assignment. This is the procedure most relevant to the search term "delete_project_party." It performs the logical or physical removal of the party from the project, along with any associated assignment handling and validation checks, returning status and message data through standard API OUT parameters.
• GET_KEY_MEMBER_START_DATE — A query function that returns the effective start date associated with a key member designation, supporting callers that need to determine when a party's key-member status began.
• CREATE_PROJECT_PARTY_WRP — A wrapper procedure that provides a simplified or alternate calling convention over the create logic, typically used where the full API signature is not required.

All procedures follow FND_API conventions: an API version, initialization and commit flags, validation-only and validation-level parameters, a debug mode flag, and standard OUT parameters for return status, message count, and message data.

Tables Accessed

The documented tables touched directly or indirectly through APPS synonyms include:

• PA_PROJECT_PARTIES — The primary transactional table holding project party assignments; read, inserted, updated, and deleted here.
• PA_PROJECT_ROLE_TYPES_B — Supplies valid project role definitions used during validation.
• PA_RESOURCES and PA_RESOURCE_TYPES — Provide resource identity and classification (for example, employee resource type) required to validate and resolve the party.
• PA_TASKS — Used where assignment or role validation is scoped to a project task.
• PA_PROGRESS_ROLLUP — Consulted or maintained to support progress rollup behavior tied to project parties.
• FND_NEW_MESSAGES — Supports message retrieval and the standard FND_API error/message stack.

Usage Notes

PA_PROJECT_PARTIES_PUB is invoked from Oracle Projects forms (such as project and team member maintenance), from concurrent programs that manage project staffing, and from custom extensions requiring programmatic control of project parties. Because the ETRM metadata records that the package is referenced by eleven other packages, custom code should call these public procedures rather than modifying PA_PROJECT_PARTIES directly. Callers must supply valid API version, initialization, and commit flags, and should inspect x_return_status and the message stack before committing. When removing assignments — the "delete_project_party" use case — the DELETE_PROJECT_PARTY procedure should be used to ensure validation and workflow consistency are preserved.