Search Results gms_budget_versions_s




Overview

GMS_BUDGET_CORE is the internal PL/SQL package body that implements the core budget processing logic for Oracle Grants Management (GMS) in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the APPS schema and is classified as an "OTHER" API, meaning it is not a formally published public interface but is relied upon internally, and is referenced by two other database packages. Its business function is to create, copy, verify, and snapshot award and project budgets, and to accumulate actual and commitment balances from Oracle Projects into grants budget lines. The package therefore serves as the engine behind grant budget versioning, baseline management, and the comparison of budgeted amounts against actual expenditure for sponsored projects.

Key Procedures and Functions

The documented package exposes ten procedures and functions:

  • BASELINE — establishes the baseline for a budget version, marking it as the approved reference against which subsequent changes are measured.
  • COPY — copies an entire budget, typically to create a new version from an existing one.
  • COPY_LINES — copies the individual budget lines belonging to a budget source into a target budget.
  • COPY_DRAFT_LINES — copies draft status budget lines, supporting working or unsubmitted budget versions.
  • COPY_ACTUAL — copies actual balances into the grants budget structure, supporting actual-versus-budget comparison.
  • VERIFY — validates a budget, checking its integrity and consistency before it is used or baselined.
  • START_END_PERIOD — determines the start and end GL periods applicable to a budget or award, using GL period status.
  • GET_PROJ_TXN_ACCUM — accumulates project transaction amounts (expenditure) for use in budget actuals.
  • GET_PROJ_RES_ACCUM — accumulates project resource-level amounts, associated with resource assignments.
  • GET_PROJ_ACCUM_ACTUALS — returns accumulated actual amounts from Oracle Projects for comparison with the budget.

Tables Accessed

The package reads and writes the grants budget tables GMS_BUDGET_VERSIONS and GMS_BUDGET_VERSIONS_S (versions and their sequence/translation records) and GMS_BUDGET_LINES, plus GMS_BALANCES for stored budget or actual balances. It references GMS_RESOURCE_ASSIGNMENTS and GMS_RESOURCE_ASSIGNMENTS_S — the object the searcher queried — which link budget resources to awards and projects, and which are central to resource-level accumulation.

On the Oracle Projects side it reads PA_PROJECTS, PA_PROJECTS_ALL, PA_PROJECT_TYPES, PA_TASKS, PA_RESOURCES, PA_RESOURCE_LISTS, PA_RESOURCE_LIST_MEMBERS, PA_RES_LIST_ASSIGNMENTS, PA_BUDGET_TYPES, PA_BUDGET_ENTRY_METHODS, PA_IMPLEMENTATIONS, and PA_PERIODS. GL period information is obtained from GL_PERIOD_STATUSES. These accesses supply the project, task, resource, period, and budget-type context required to map Projects data into grants budgets.

Usage Notes

GMS_BUDGET_CORE is invoked primarily from Grants Management budget forms and concurrent programs that create, copy, baseline, and verify award or project budgets, and from the Grants budget processing pipeline within the Oracle Projects integration. Because the package is classified as OTHER and is not a documented public API, custom or extension code should avoid calling it directly; supported integration typically flows through GMS_BUDGET_PUB and related published interfaces, which internally rely on this body. The related package GMS_BUDGET_UTILS and GMS_ERROR_PKG provide shared utilities and error handling, while FND_MSG_PUB and FND_MESSAGE supply message resolution. Its dependency on GMS_RESOURCE_ASSIGNMENTS_S is significant for extensions that query resource assignment data, since that table is populated in tandem with budget version processing performed by this package.