Search Results publish_progress

Overview

PA_PROGRESS_PUB is the public PL/SQL API package within the Oracle E-Business Suite Projects (PA) module responsible for managing project and task progress records, including percent-complete values, physical progress, and the rollup of progress across the project structure. It serves as the sanctioned interface through which other Oracle EBS modules, forms, concurrent programs, and external integrations create, update, delete, and publish progress information without directly manipulating the underlying progress tables. In Oracle EBS 12.1.1 and 12.2.2, the package is classified as a PUB (public) API, meaning its signatures are treated as a supported integration surface, in contrast to the private PVT packages that contain the corresponding business logic. The package is central to project performance measurement, feeding cost and revenue recognition, earned value reporting, and workplan-to-financials reconciliation.

Key Procedures and Functions

The documented interface exposes approximately 28 procedures and functions. Core progress maintenance is handled by UPDATE_PROGRESS and UPDATE_TASK_PROGRESS, which manage percent-complete and status updates for tasks and assignments. Progress rollup across the work breakdown structure is performed by ROLLUP_PROGRESS_PVT, UPDATE_ROLLUP_PROGRESS_PVT, ROLLUP_FUTURE_PROGRESS_PVT, and PROGRAM_ROLLUP_PVT, supporting both current and forward-looking rollup scenarios. Project-level progress attributes are managed through CREATE_PROJ_PROG_ATTR, UPDATE_PROJ_PROG_ATTR, and DELETE_PROJ_PROG_ATTR.

• DELETE_PROGRESS_RECORD and DELETE_WORKING_WP_PROGRESS remove progress and working workplan records.
• PUSH_DOWN_TASK_STATUS propagates parent task status to subordinate tasks.
• UPDATE_PC_PARTY_MERGE reconciles percent-complete data when project parties are merged.
• APPLY_LP_PROG_ON_CWV applies latest-progress values to capital work in progress processing.
• PULL_SUMMARIZED_ACTUALS, GET_SUMMARIZED_ACTUALS, PUSH_WORKPLAN_ACTUALS, and POPULATE_PJI_TAB_FOR_PLAN move and summarize actual quantities between progress and financial planning structures.
• TRANSFER_WP_PERCENT_TO_FIN transfers workplan percentages into financials.
• PUBLISH_PROGRESS makes stored progress data available to downstream reporting and integration consumers.

Tables Accessed

Through APPS synonyms the package reads and writes the primary progress and project structures, including PA_PERCENT_COMPLETES and PA_PERCENT_COMPLETES_S, which store percent-complete values and their translated/language variants, and PA_PROGRESS_ROLLUP and PA_PROGRESS_ROLLUP_S, which hold rolled-up progress by project or task. PA_PROJECTS and PA_PROJECTS_ALL supply project definitions, while PA_PROJECT_STATUSES supports status validation. PA_OBJECT_RELATIONSHIPS links progress records to structural objects. Period validation and summarization rely on GL_PERIODS and PA_PERIODS, and PA_ASGMT_PLAN_CHANGE_T, PA_BUDGET_VERSIONS, PA_COST_DISTRIBUTION_LINES_ALL, PA_PROG_ACT_BY_PERIOD_TEMP, and PA_IMPLEMENTATIONS_ALL support planning changes, budget references, actual cost distribution, temporary progress-by-period staging, and installation configuration.

Usage Notes

PA_PROGRESS_PUB is typically invoked from Projects forms such as Project Status and Progress Entry, from concurrent programs that roll up progress or publish project data, and from custom PL/SQL integrations that must conform to supported API behavior. The package is referenced by 14 other packages, including PA_STATUS_PUB, PA_PROJECT_PUB, PA_TASK_PUB1, PA_ASSIGNMENT_PROGRESS_PUB, PA_PROGRESS_PVT, PA_PROJECT_STRUCTURE_PUB1, PA_PROJ_TASK_STRUC_PUB, PA_STRUCT_TASK_ROLLUP_PUB, and PJI flow-manufacturing/rollup packages, indicating that status maintenance, project and task maintenance, and rollup processes depend on it. It in turn depends on FND_API for standard API error and message handling, PA_INTERFACE_UTILS_PUB, PA_SCHEDULE_OBJECTS_PVT, and a set of PA collection types (date, number, and various VARCHAR2 table types) used for bulk processing. Developers invoking the API should use a valid APPS session, follow the standard FND_API return-status convention, and avoid direct DML against the underlying PA progression tables.