Search Results summerize_project_totals

Overview

PA_BUDGET_UTILS is a foundational PL/SQL utility package in the Oracle EBS Projects (PA) module, owned by APPS and classified as an OTHER API. It centralizes the low-level logic that governs project and task budget creation, versioning, and validation. Rather than exposing a single business transaction, the package provides the shared building blocks used by the Budgets form, concurrent processes, and other APIs that must create drafts, resolve baseline or original versions, determine budget amount and entry-method codes, and verify that budget rules are honored before data is committed.

The package maintains global variables—including G_ENTRY_LEVEL_CODE, G_BGT_INTG_FLAG, G_PROJECT_ID, and the project, functional, and transaction currency globals—that are populated on demand and reused across calls, particularly when the project context changes. This caching pattern reduces repeated lookups of project currency information during interactive budgeting sessions.

The user search term "summerize_project_totals" corresponds directly to the documented procedure SUMMERIZE_PROJECT_TOTALS, which aggregates budget line amounts to produce project-level totals. Note that the packaged identifier retains the historical spelling "SUMMERIZE" (rather than "SUMMARIZE"), a naming artifact carried forward for backward compatibility. Custom code must reference the procedure using the exact packaged spelling.

Key Procedures and Functions

The documented interface comprises twenty-nine procedures and functions, grouped by purpose below.

• Currency and code resolution: CHECK_CURRENCY_UOM determines whether a given unit of measure represents a currency; GET_BUDGET_AMOUNT_CODE returns the amount code (cost or revenue) tied to a budget type; GET_BUDGET_TYPE_CODE and GET_BUDGET_ENTRY_METHOD_CODE return the corresponding type and entry-method codes; GET_CHANGE_REASON_CODE resolves the applicable change reason.
• Version resolution: GET_DRAFT_VERSION_ID, GET_BASELINED_VERSION_ID, and GET_ORIGINAL_VERSION_ID return the version identifiers for the draft, baselined, and original budget versions of a project or task.
• Defaults and setup: GET_DEFAULT_RESOURCE_LIST_ID and GET_DEFAULT_ENTRY_METHOD_CODE retrieve default resource lists and entry methods; CHECK_RESOURCE_MEMBER_LEVEL validates resource membership; VERIFY_BUDGET_RULES enforces budgetary control rules (referencing G_BGT_INTG_FLAG).
• Existence and amount checks: CHECK_PROJ_BUDGET_EXISTS and CHECK_TASK_BUDGET_EXISTS test whether budgets exist at project or task level; GET_PROJ_BUDGET_AMOUNT and GET_TASK_BUDGET_AMOUNT return budgeted amounts.
• Draft maintenance and totals: DELETE_DRAFT, CREATE_DRAFT, and CREATE_LINE manage draft versions and budget lines; SUMMERIZE_PROJECT_TOTALS rolls line-level amounts into project totals.

Tables Accessed

The package reads and writes against the core budgeting and project tables through APPS synonyms. PA_PROJECTS_ALL, PA_PROJECTS, and PA_TASKS supply project and task context. PA_BUDGET_VERSIONS, PA_BUDGET_VERSIONS_S, PA_BUDGET_LINES, and PA_BUDGET_LINES_S hold budget version headers and detail lines, including draft and baselined data. PA_BUDGET_TYPES supplies budget type definitions, while PA_BUDGET_ENTRY_METHODS and PA_BUDGETARY_CONTROL_OPTIONS drive entry-method and rule-checking behavior. PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_ASSIGNMENTS_S, and PA_RESOURCE_LIST_MEMBERS support resource list and membership validation, and PA_PROJECT_TYPES together with PA_PROJ_FP_OPTIONS govern project-type-level budgeting options.

Usage Notes

PA_BUDGET_UTILS is referenced by twenty-six other packages, confirming its role as a shared dependency rather than an end-user entry point. It is typically invoked indirectly: the Budgets form calls it to populate globals and validate entries, budget-related concurrent programs use it when creating or deleting drafts, and custom extensions call individual functions (for example, GET_BASELINED_VERSION_ID or SUMMERIZE_PROJECT_TOTALS) to obtain version identifiers or aggregated totals. Because the package caches project currency and project ID in package globals, callers operating in long-lived sessions should be aware that the cached context refreshes only when the incoming project ID differs from G_PROJECT_ID.