Search Results get_proj_res_accum

Overview

GMS_BUDGET_CORE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Grants Management (GMS) module family and provides the internal engine that manages budget records for awarded grants, cooperative agreements, and similar sponsored projects. Its principal responsibility is to create, copy, verify, and roll forward budget versions and budget lines held in the GMS schema, and to derive accumulated balances from project transaction and resource data stored by Oracle Projects.

In the repository terminology used by EBS, GMS_BUDGET_CORE is classified as an "OTHER" API rather than a public, supported interface. It is a core processing package: the higher-level public API, GMS_BUDGET_PUB, and the workflow integration package GMS_WF_PKG both call into it. This layering means that GMS_BUDGET_CORE executes most of the actual budget manipulation work, while GMS_BUDGET_PUB exposes a controlled entry point for forms, concurrent programs, and external callers. The package is documented as VALID in both EBS 12.1.1 and 12.2.2, and its metadata is effectively identical across the two releases.

The package resolves its table references through APPS synonyms, so all I/O is performed against the shared APPS objects rather than schema-qualified GMS tables. Its dependency list also includes SYS.STANDARD, which is the standard Oracle PL/SQL package supplying fundamental language constructs.

Key Procedures and Functions

ETRM documents ten callable units within the package. Their names indicate the following responsibilities:

• BASELINE — Establishes a baseline budget version for an award, fixing the approved budget against which subsequent revisions are measured.
• COPY — Copies a budget version, typically to create a new working version from an existing approved or draft version.
• VERIFY — Validates a budget version or its lines, checking consistency against project, resource, and period data before the budget is accepted or baselined.
• COPY_LINES — Copies the individual budget line records belonging to a source budget version into a target version.
• START_END_PERIOD — Determines or derives the start and end accounting periods associated with a budget, providing the date range over which balances are accumulated.
• COPY_ACTUAL — Copies actual expenditure amounts into a budget context, supporting comparisons such as budget-to-actual or baseline-to-actual reporting.
• GET_PROJ_TXN_ACCUM — Returns accumulated project transaction amounts for a project, used to populate budget or comparison figures from expenditure transactions.
• GET_PROJ_RES_ACCUM — Returns accumulated amounts by project resource, allowing budget lines to be aligned with resource assignments.
• GET_PROJ_ACCUM_ACTUALS — Aggregates actual costs at project level, supplying the actuals side of budget-versus-actual analysis.
• COPY_DRAFT_LINES — Copies draft (unapproved) budget lines, supporting working versions that are not yet baselined.

Oracle does not publish parameter lists for these units in the ETRM metadata; callers should treat the signatures as internal and obtain them from the package specification in the target instance before use.

Tables Accessed

GMS_BUDGET_CORE reads and writes the core Grants budget tables GMS_BUDGET_VERSIONS and GMS_BUDGET_VERSIONS_S (the version header and its translation table), GMS_BUDGET_LINES (the individual line amounts), and GMS_BALANCES (accumulated budget balances). GMS_RESOURCE_ASSIGNMENTS and GMS_RESOURCE_ASSIGNMENTS_S supply the resource structure against which lines are defined.

Project-side data is drawn from PA_PROJECTS, PA_PROJECTS_ALL, PA_PROJECT_TYPES, and PA_IMPLEMENTATIONS for project identity and configuration; PA_BUDGET_TYPES and PA_BUDGET_ENTRY_METHODS for budget type and entry-method validation; PA_RESOURCES for resource definition; and PA_PERIODS together with GL_PERIOD_STATUSES for accounting period derivation and open/closed status checks.

Usage Notes

GMS_BUDGET_CORE is not intended for direct invocation by customers. It is reached indirectly through GMS_BUDGET_PUB, which provides the supported public interface, and through GMS_WF_PKG when budget-related workflow events are processed. In a typical EBS deployment, the package is triggered by the Grants Management budget forms and by concurrent programs that baseline, copy, or compare award budgets. Custom extensions that require budget manipulation should call GMS_BUDGET_PUB rather than GMS_BUDGET_CORE, since the core package is subject to change without notice between patch levels. Because it references PA_ and GL_ objects through APPS synonyms, any custom code interacting with it must run under an APPS-privileged session.