Search Results pa_struct_task_rollup_pub




Overview
Explore in AI Chat

Overview

PA_STRUCT_TASK_ROLLUP_PUB is a public PL/SQL package in the APPS schema that supports the task and structure rollup functionality of Oracle Projects. It belongs to the Project Management and Workplan family of APIs and is classified as a PUB (public) API, meaning it is intended for invocation by other application modules and by customer extensions rather than being restricted to internal use. In Oracle EBS 12.1.1 and 12.2.2 the package coordinates the propagation of status, progress, and scheduling attributes from subordinate project elements (subprojects, tasks, and workplan structures) up to their parent elements, and in some cases pushes attributes downward. It therefore sits at the center of hierarchical project structures where dates, statuses, and progress must remain consistent across levels of the work breakdown. The package body is documented as VALID in the ETRM repository and exposes six documented procedures. It references a broad set of Projects foundation tables and utility packages, and the documentation notes that it is referenced by five other database objects.

Key Procedures and Functions

  • TASKS_ROLLUP_UNLIMITED — Performs rollup of task information across an unbounded hierarchy, allowing the caller to roll up all descendant tasks without an imposed level restriction.
  • TASKS_ROLLUP — Performs the standard task rollup operation, aggregating task-level attributes upward through the project structure in accordance with the configured structure and rollup rules.
  • TASK_STATUS_ROLLUP — Rolls up task status values from lower-level elements to their parents, ensuring parent task status reflects the state of the underlying work.
  • TASK_STAT_PUSHDOWN_ROLLUP — Combines pushdown and rollup behavior for task status, propagating a status change in one direction down to descendants and subsequently recomputing affected rollups.
  • ROLLUP_FROM_SUBPROJECT — Rolls up data originating at a subproject level into its owning parent project, supporting structures that span multiple project definitions.
  • PROGRAM_SCHEDULE_DATES_ROLLUP — Rolls up schedule dates across the program or project hierarchy, keeping parent-level start and finish dates aligned with the aggregated dates of their children.

The documented interface exposes these six procedures; no parameter lists are published in the extracted metadata, so callers should consult the package specification for exact signatures.

Tables Accessed

The package reads and writes the core Projects structure tables through APPS synonyms. PA_PROJECTS_ALL provides project-level context; PA_PROJECT_STATUSES and PA_PROJ_STRUCTURE_TYPES supply valid status and structure type definitions. Task and element data reside in PA_PROJ_ELEMENTS, with versioned definitions in PA_PROJ_ELEMENT_VERSIONS and its schedule and structure companions, PA_PROJ_ELEM_VER_SCHEDULE and PA_PROJ_ELEM_VER_STRUCTURE. Workplan-specific attributes are held in PA_PROJ_WORKPLAN_ATTR, and PA_OBJECT_RELATIONSHIPS stores the relationships used to resolve hierarchy. PLITBLM is a standard Oracle PL/SQL table type used internally for bulk collections. Writes are performed against the element, version, schedule, and structure tables as rollup results are committed.

Usage Notes

PA_STRUCT_TASK_ROLLUP_PUB is typically invoked from Oracle Projects forms and concurrent programs when tasks are created, updated, or when status or schedule changes require hierarchical synchronization. It is also callable from custom PL/SQL using the standard FND_API error-handling conventions, since it depends on FND_API, FND_MSG_PUB, FND_GLOBAL, and FND_PROFILE. Internally it delegates to utilities such as PA_PROJECT_STRUCTURE_UTILS, PA_PROJ_ELEMENTS_UTILS, PA_TASK_ASSIGNMENT_UTILS, PA_WORKPLAN_ATTR_UTILS, PA_RELATIONSHIP_UTILS, and PA_PROJECT_DATES_PUB. Because it is referenced by five other packages and references none of its callers, it should be treated as a shared service. Custom code should call the public procedures rather than the underlying private utilities, and should account for the fact that rollup operations may process large hierarchies and therefore carry processing cost in high-volume project structures.