Search Results delete_task_ver_wo_val

Overview

PA_TASK_PVT1 is a private PL/SQL package body within the Oracle E-Business Suite Projects (PA) module that supports the task and task version management APIs exposed through the public PA_TASK_PVT package. In Oracle EBS 12.1.1 and 12.2.2, this package encapsulates the low-level business logic required to create, update, version, and weight project tasks (also referred to as project elements) within the Project Management and Project Costing architecture. Tasks represent the lowest level of the project work breakdown structure and carry schedule, progress, and financial attributes that roll up to the project level. PA_TASK_PVT1 mediates between the public API layer and the underlying PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS tables, enforcing validation, versioning rules, and structural integrity of the task hierarchy. The package header identifies "Create_Task" as a private procedure with an extensive parameter list covering task number, name, description, location, manager, priority, status, and product management references. The presence of the requested function "get_latest_task_ver_id" reflects the package's role in resolving the most recent version identifier for a task, a prerequisite for any version-aware update or delete operation.

Key Procedures and Functions

The package exposes 17 documented procedures spanning the full task lifecycle. Task-level operations include CREATE_TASK, UPDATE_TASK, UPDATE_TASK_WEIGHTING, RECALC_TASKS_WEIGHTING, INHERIT_TASK_TYPE_ATTR, SET_NEW_TASKS_TO_TBD, and DEFER_CALC_TASK_WEIGTHAGE, which govern task creation, attribute maintenance, and progress weighting calculations. Version-level operations include CREATE_TASK_VERSION, UPDATE_TASK_VERSION, DELETE_TASK_VERSION, DELETE_TASK_VER_WO_VAL, UPDATE_TASK_VER_DELETE_STATUS, and UPDATE_WORKING_VER_WEIGHT, which manage the versioned nature of task definitions, including soft deletion and the designation of the working version. Schedule operations are handled by CREATE_SCHEDULE_VERSION and UPDATE_SCHEDULE_VERSION, while UPDATE_DATES_TO_ALL_VERSIONS propagates date changes across every task version. DISP_SEQ_NUM_LEVEL_DEFER supports display sequence numbering within the level structure. The internal helper get_latest_task_ver_id, though not surfaced in the documented procedure list, is referenced by these version-aware routines to determine the current version of a task before applying changes.

Tables Accessed

The package reads and writes several core Projects tables through APPS synonyms. PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS store the master and versioned task records. PA_PROJ_ELEM_VER_SCHEDULE and PA_PROJ_ELEM_VER_STRUCTURE hold schedule and structural hierarchy data for each version. PA_PROJ_ELEM_VER_TMP and PA_PROJ_ELEMENT_VERSIONS_S support temporary and seed version processing. PA_PROJ_ELEM_RELATIONSHIP_T and PA_OBJECT_RELATIONSHIPS maintain relationships between tasks and related objects. PA_ALTERNATE_TASKS supports alternate task definitions. PA_PERCENT_COMPLETES and PA_PROGRESS_ROLLUP capture progress measurement data used in weighting calculations. PA_PROJECTS_ALL provides the parent project context, while PA_PROJ_STRUCTURE_TYPES defines the allowable structure types. PA_OBJECT_PAGE_LAYOUTS and PA_PAGE_LAYOUTS govern UI layout metadata associated with task objects.

Usage Notes

PA_TASK_PVT1 is invoked indirectly through the public PA_TASK_PVT API rather than called directly by custom code, since it is a private package body. It is most commonly triggered by the Project Management and Project Costing forms when users create, modify, or version tasks, and by concurrent programs that perform bulk task maintenance such as weighting recalculation and schedule date propagation. The package is referenced by eight other packages within the Projects module, indicating broad internal reuse. Developers extending Oracle Projects should target the public PA_TASK_PVT interfaces and rely on the documented validation and versioning behavior implemented in PA_TASK_PVT1, taking care not to bypass the version resolution logic that get_latest_task_ver_id and its callers provide.