Search Results get_act_effort_this_period

Overview

PA_PROGRESS_UTILS is a utility package within the Oracle Projects (PA) module of Oracle E-Business Suite, responsible for supporting project progress tracking, percent-complete calculation, and progress rollup processing. The package encapsulates the shared logic used by the Progress workbench, progress entry forms, and related concurrent programs to derive, validate, and store progress data across project structures and reporting cycles.

Its primary business purpose is to manage the relationship between tasks, project elements, versions, and progress cycles so that percent-complete values, as-of dates, and rollup attributes remain consistent. This is particularly relevant to burden and revenue recognition schedules, where incremental actual effort and earned value calculations depend on accurate progress records. The header comment referencing the as-of-date APIs (previous_record_count, next_record_count, x_bill_thru_date, and related globals) indicates that the package evolved to support date-sensitive progress retrieval, an essential requirement for recurring progress reporting.

Key Procedures and Functions

The package exposes 124 documented procedures and functions. The following represent the principal entry points relevant to progress and structural version management:

• GET_LATEST_TASK_VER_ID — Returns the most recent version identifier for a given project and task, ensuring calculations reference the current task definition.
• GET_LATEST_STRUCTURE_VER_ID — Returns the latest project structure version, used to align progress data with the active work breakdown structure.
• PROGRESS_RECORD_EXISTS — Determines whether a progress record exists for a specified element version and object type within a project.
• PROJ_TASK_PROG_EXISTS — Checks for the existence of task-level progress records prior to insertion or update.
• ISUSERPROJECTMANAGER — Validates whether a user holds the project manager role for a given project, supporting authorization checks.
• GET_WORKING_PROGRESS_ID — Retrieves the working progress identifier for a project and task, distinguishing draft from submitted progress.
• GET_PRIOR_PERCENT_COMPLETE — Returns the previously recorded percent-complete value, enabling incremental calculation of actual effort.
• GET_AS_OF_DATE / GET_LATEST_AS_OF_DATE / CHECK_VALID_AS_OF_DATE / AS_OF_DATE — Manage the as-of date parameter that governs which progress snapshot is retrieved or written.
• GET_NEXT_PPC_ID / GET_PPC_ID — Retrieve percent-complete cycle identifiers used to sequence progress records.
• GET_NEXT_PROGRESS_CYCLE / GET_PROG_DT_CLOSEST_TO_SYS_DT / CHECK_PROG_EXISTS_ON_AOD — Support progress cycle determination and validation against system dates.
• CALC_BASE_PERCENT — Computes the base percent-complete value used in rollup calculations.
• GET_ROLLUP_ATTRS — Returns the attributes required for progress rollup processing.
• UPDATE_TASK_PROG_REQ_DATE and ADJUST_REMINDER_DATE — Maintain requested and reminder dates associated with task progress, invoking the standard FND_API commit and return-status conventions.

Tables Accessed

The package reads and writes several core Oracle Projects tables through APPS synonyms, including:

• PA_PROGRESS_ROLLUP — Stores rolled-up progress values by project and structure.
• PA_PROJECTS_ALL and PA_PROJ_ELEMENTS — Provide project and element definitions used in progress validation.
• PA_BUDGET_LINES and PA_BUDGET_VERSIONS — Supply budget baselines for percent-complete computation.
• PA_COST_DISTRIBUTION_LINES_ALL — Source of actual cost and effort data.
• PA_LABOR_COST_MULTIPLIERS — Applied when converting labor effort.
• GL_PERIODS and PA_BILLING_CYCLES — Used to align progress cycles with accounting periods and billing schedules.
• PA_IMPLEMENTATIONS / PA_IMPLEMENTATIONS_ALL / PA_FIN_PLAN_TYPES_B / PA_FP_RES_ASSIGNMENTS_TMP / PA_FP_TXN_CURRENCIES / PA_OBJECT_PAGE_LAYOUTS — Support configuration, plan-type, and form layout resolution.

Usage Notes

PA_PROGRESS_UTILS is referenced by 47 other packages, confirming its role as a shared foundation for progress processing. It is typically invoked from the Progress Entry and Progress Workbench forms, from concurrent programs that calculate project progress, and from custom extensions that need to retrieve or validate progress records. Because several routines write data, callers should pass the p_commit parameter deliberately and handle the standard x_return_status, x_msg_count, and x_msg_data out parameters to surface errors correctly.

When searching for get_incremental_actual_effort, note that no such member is documented in the ETRM metadata for this package. Incremental actual effort is generally derived using the prior percent-complete values returned by GET_PRIOR_PERCENT_COMPLETE together with as-of-date functions such as GET_AS_OF_DATE and GET_LATEST_AS_OF_DATE. Custom logic must therefore combine these documented functions rather than relying on a dedicated API.