Search Results copy_entire_task

Overview

PA_TASKS_MAINT_PVT is a private (PVT classification) PL/SQL package in the APPS schema that implements the low-level maintenance logic for project tasks within Oracle Projects. It provides the internal engine behind the public task maintenance API, APPS.PA_TASKS_MAINT_PUB, which is the only known package that references it. The private package encapsulates the actual insert, update, delete, hierarchy manipulation, copying, and financial-task synchronization operations against the PA_TASKS and PA_TASKS_S tables, while the public package exposes the supported, externally callable interface. As a private package, it is not intended to be invoked directly by customer code; it exists to centralize validation, multi-org-aware data manipulation, and error handling so that the public API can remain thin and stable across Oracle EBS 12.1.1 and 12.2.2. The package depends on FND_API for the standard API programming constructs (message handling, returned status, and savepoint management) and on PA_INTERFACE_UTILS_PUB for shared interface utilities used when task elements are pushed into Oracle Projects structures.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions:

• CREATE_TASK — creates a new task record, including its PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS entries.
• UPDATE_TASK — modifies attributes of an existing task.
• DELETE_TASK — removes a task and its associated project element data.
• INDENT_TASK — moves a task one level deeper in the work breakdown structure hierarchy.
• OUTDENT_TASK — moves a task one level higher in the work breakdown structure hierarchy.
• COPY_ENTIRE_PROJECT — copies all tasks when an entire project is duplicated.
• COPY_SELECTED_TASK — copies a specifically identified task, typically including its subtree.
• COPY_ENTIRE_TASK — copies a task together with its full descendant hierarchy.
• MOVE_TASK — relocates a task to a different parent or project position.
• SET_UNSET_FINANCIAL_TASK — toggles the financial-task indicator that controls whether a task is charged in financial transactions.
• SYNC_UP_WP_TASKS_WITH_FIN — synchronizes Workplan tasks with their financial task counterparts.

Parameter lists are not reproduced here; the public wrapper PA_TASKS_MAINT_PUB is the documented entry point.

Tables Accessed

The package reads and writes PA_TASKS and its alternate key/audit table PA_TASKS_S, the primary and shadow store for task definitions. It references PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS to maintain the project-element representation of tasks, and PA_PROJECTS_ALL and PA_PROJECT_TYPES_ALL to validate the owning project and its task-enabling project type. PA_PROJECT_CUSTOMERS and PA_OBJECT_RELATIONSHIPS support customer and relationship data associated with tasks. FND_NEW_MESSAGES provides message lookup for error reporting. ALL_TAB_COLUMNS and USER_SYNONYMS are used for metadata introspection, consistent with dynamic SQL patterns. FND_API provides the standard API layering and savepoint support.

Usage Notes

PA_TASKS_MAINT_PVT is invoked indirectly through APPS.PA_TASKS_MAINT_PUB. Typical callers include the Oracle Projects task maintenance forms (which route user actions such as create, indent, outdent, copy, and move through the public API), concurrent programs that build or restructure work breakdown structures, and project-copy logic that uses COPY_ENTIRE_PROJECT or COPY_ENTIRE_TASK. Because the package is classified PVT, Oracle does not support direct calls to it from custom code; customizations should use PA_TASKS_MAINT_PUB or other documented public interfaces. Any direct reference risks breakage across patches and upgrades, since private signatures may change without notice. Customers should also avoid referencing the underlying PA_TASKS tables directly, as this bypasses validation performed by the package.