Search Results get_summarized_actuals
Overview
APPS.PA_PROGRESS_PUB is the public PL/SQL API package for Oracle Project Management progress and performance reporting within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to capture, validate, roll up, and publish project and task progress data, including percent complete, physical progress status, actual and estimated dates, and summarized actual amounts. The package header is designated with an API classification of PUB in the ETRM documentation, meaning it is a supported public interface intended for external invocation by Oracle forms, concurrent programs, and custom extensions. The body implements 28 documented procedures and functions, several of which are private helper routines (suffixed _PVT) used to support the public API surface. The package spans project-level and task-level progress attributes, workplan progress rollup, actual cost summarization from distribution lines, and integration with financial percent-complete processing.
Key Procedures and Functions
The documented routines fall into several functional groups.
- Progress capture and maintenance: UPDATE_TASK_PROGRESS, UPDATE_PROGRESS, DELETE_PROGRESS_RECORD, CREATE_PROJ_PROG_ATTR, UPDATE_PROJ_PROG_ATTR, and DELETE_PROJ_PROG_ATTR manage task and project progress records and their attributes.
- Rollup and workflow: ROLLUP_PROGRESS_PVT, UPDATE_ROLLUP_PROGRESS_PVT, ROLLUP_FUTURE_PROGRESS_PVT, PROGRAM_ROLLUP_PVT, PUSH_DOWN_TASK_STATUS, and PUSH_WORKPLAN_ACTUALS handle hierarchical progress aggregation, status propagation, and workplan actuals movement.
- Actuals summarization: GET_SUMMARIZED_ACTUALS and PULL_SUMMARIZED_ACTUALS retrieve and pull summarized actual amounts from cost distribution data, supporting the user search term.
- Publishing and integration: PUBLISH_PROGRESS and POPULATE_PJI_TAB_FOR_PLAN expose progress information to downstream consumers and project intelligence structures.
- Support and utility: UPDATE_PC_PARTY_MERGE, APPLY_LP_PROG_ON_CWV, DELETE_WORKING_WP_PROGRESS, and TRANSFER_WP_PERCENT_TO_FIN address party merges, change-workflow progress application, working workplan cleanup, and transfer of workplan percent complete to financials.
Tables Accessed
The package operates against the core Project Management and financial progress schema. PA_PERCENT_COMPLETES and its _S sequence-backed synonym store percent-complete records; PA_PROGRESS_ROLLUP and PA_PROGRESS_ROLLUP_S hold rolled-up progress snapshots. PA_COST_DISTRIBUTION_LINES_ALL supplies the expenditure data summarized by GET_SUMMARIZED_ACTUALS and related routines. PA_PROG_ACT_BY_PERIOD_TEMP serves as a temporary staging structure for period-based actuals. PA_PROJECTS, PA_PROJECTS_ALL, PA_PROJECT_STATUSES, PA_OBJECT_RELATIONSHIPS, PA_ASGMT_PLAN_CHANGE_T, PA_BUDGET_VERSIONS, and PA_IMPLEMENTATIONS_ALL provide project, relationship, budget, and implementation context. GL_PERIODS and PA_PERIODS resolve accounting and project accounting period boundaries used in summarization and rollup.
Usage Notes
PA_PROGRESS_PUB is invoked from Project Management progress entry forms, progress rollup and publishing concurrent programs, and workplan and financial integration flows. The ETRM metadata records that it is referenced by 14 other packages, indicating broad internal dependency across project management and financial modules. Because the header is classified PUB, custom integrations may call the documented public procedures directly; custom code should honor the standard API conventions implied by the signatures, including p_api_version, p_init_msg_list, p_commit, p_validate_only, p_validation_level, p_max_msg_count, and message-stack retrieval via FND_MSG_PUB. The package supports a debug profile option (PA_DEBUG_MODE) and accepts calling-module and calling-mode parameters, and it uses sentinel values (PA_INTERFACE_UTILS_PUB.G_PA_MISS_NUM, _CHAR, _DATE) to distinguish omitted arguments, so callers should pass explicit values where updates are intended.
-
PACKAGE BODY: APPS.PA_PROGRESS_PUB
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_UTILS2
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_UTILS2
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_FP_MAINTAIN_ACTUAL_PUB
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_FP_MAINTAIN_ACTUAL_PUB
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_TASK_ASSIGNMENTS_PVT
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_TASK_ASSIGNMENTS_PVT
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_TASK_ASGMTS_V
12.2.2
-
PACKAGE: APPS.PA_PROGRESS_PUB
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_NUM_TBL_TYPE
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on FND_MSG_PUB
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_NUM_TBL_TYPE
12.2.2
-
PACKAGE: APPS.PA_PROGRESS_PUB
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PJI_FM_XBS_ACCUM_UTILS
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on FND_MSG_PUB
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PJI_FM_XBS_ACCUM_UTILS
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_PLSQL_DATATYPES
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_NUM_TBL_TYPE
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_NUM_TBL_TYPE
12.2.2
-
APPS.PA_PROGRESS_PUB SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PA_PROGRESS_PUB
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_PROGRESS_PVT
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_PROGRESS_PVT
12.1.1
-
PACKAGE BODY: APPS.PJI_FM_XBS_ACCUM_UTILS
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_UTILS
12.1.1
-
PACKAGE BODY: APPS.PJI_FM_XBS_ACCUM_UTILS
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_PROGRESS_PUB
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_UTILS
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_PROGRESS_PUB
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_DEBUG
12.2.2
-
APPS.PA_PROGRESS_PUB dependencies on PA_DEBUG
12.1.1
-
PACKAGE BODY: APPS.PA_PROGRESS_PVT
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_INTERFACE_UTILS_PUB
12.1.1
-
APPS.PA_PROGRESS_PUB dependencies on PA_INTERFACE_UTILS_PUB
12.2.2
-
PACKAGE BODY: APPS.PA_PROGRESS_PVT
12.2.2