Search Results delete_dlv_actions_in_bulk

Overview

PA_ACTIONS_PVT is a private PL/SQL package body in the APPS schema that implements the core action-management logic for Oracle Projects. Its principal responsibility is the processing, creation, maintenance, and propagation of "actions" associated with project entities such as deliverables and project elements. Actions are the transactional records that drive workflow, deliverable management, and status transitions within Oracle Projects and, through integration points, Oracle E-Business Suite's order and deliverable frameworks. The package is classified as a PVT (private) API, meaning it is intended to be called by other Oracle Projects packages and public APIs rather than invoked directly by end users or external customizations.

In release 12.1.1 and 12.2.2 the package sits within the Projects action framework and operates against the object-relationship model that links projects, tasks, elements, and deliverables. It encapsulates bulk DML against the underlying relationship tables, enforces deletion eligibility rules, and supports copying of action definitions between project structures. Because it is a package body, its specification is not exposed in this dependency list, but the body is documented as VALID and is referenced by two other database objects.

Key Procedures and Functions

• CREATE_DLV_ACTIONS_IN_BULK — Creates deliverable-related action records in a single bulk operation, avoiding row-by-row processing for performance. It is intended for scenarios where many actions must be generated for a set of deliverables.
• UPDATE_DLV_ACTIONS_IN_BULK — Performs bulk updates to existing deliverable actions, applying supplied changes across multiple action records.
• DELETE_DLV_ACTIONS_IN_BULK — Removes multiple deliverable action records in bulk, generally after eligibility validation.
• DELETE_DLV_ACTION — Deletes a single deliverable action record, enforcing the same underlying business rules as the bulk variant.
• COPY_ACTIONS — Copies action definitions and their associated records from a source project structure to a target, supporting project templates, project duplication, and deliverable rollover.
• IS_DELETE_ACTION_ALLOWED — A validation function that determines whether a given action may be deleted, based on the current state of its parent entity and related records.

Tables Accessed

The package reads and writes the project relationship and element structures that underpin the action model. PA_OBJECT_RELATIONSHIPS holds the associations between projects, tasks, elements, and deliverables; the _S variant is the corresponding sequence object used for surrogate key generation. PA_PROJECTS_ALL and PA_PROJECT_TYPES_ALL supply project header and project-type context, including whether action processing is enabled. PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEMENT_VERSIONS_S, PA_PROJ_ELEM_VER_SCHEDULE, and PA_PROJ_ELEM_VER_SCHEDULE_S provide element, version, and schedule information that actions reference. PA_TASKS_S provides task surrogate keys. FND_NEW_MESSAGES and FND_MSG_PUB are used for message resolution and error reporting, while PLITBLM supports PL/SQL table handling. The package also depends on API utilities such as FND_API, FND_GLOBAL, PA_DEBUG, PA_UTILS, PA_INTERFACE_UTILS_PUB, PA_DELIVERABLE_UTILS, and the OKE deliverable utilities for cross-module actions.

Usage Notes

PA_ACTIONS_PVT is a private API and is not exposed directly on Oracle Projects forms or concurrent programs. It is invoked by public Oracle Projects APIs and by other packages such as PA_DELIVERABLE_UTILS and PA_INTERFACE_UTILS_PUB, which in turn are called from the Projects forms, deliverable management flows, and interface/concurrent processing. Custom code should never call PA_ACTIONS_PVT directly; instead, use the supported public API that wraps it. Because the package operates on relationship and element tables, any custom extension must respect the deletion rules enforced by IS_DELETE_ACTION_ALLOWED and the bulk processing conventions implemented in the CREATE, UPDATE, and DELETE procedures. No database object references PA_ACTIONS_PVT, confirming its private, internal role in the Projects action framework.