Search Results get_resource_list_id

Overview

APPS.GMS_SUMMARIZE_BUDGETS is a PL/SQL package body in the Oracle E-Business Suite Grants Management (GMS) module. Its principal business function is to summarize, aggregate, and baseline budget data held against awarded grants and funded projects, so that budget versions can be consolidated at project, task, and resource levels for reporting, inquiry, and downstream award management.

The package operates alongside Oracle Projects budgeting structures, because GMS budgets are stored in the same underlying budgeting model that Oracle Projects uses (budget entry methods, budget versions, and resource assignments). The header comment ("gmsbusub.pls 120.2") and the "Added for GMS enhancement for R12: 5583170" annotation confirm that this package was maintained to support the R12 release line, including 12.1.1 and 12.2.2. A private helper, validate_profile_bem, exists in the body to validate that the budget entry method attached to a project conforms to GMS expectations — for example, that the entry level is project level, that the burdened cost flag is set, and that the BEM is within its active date range. This helper also references the profile option GMS_ENABLE_DEBUG_MODE to control diagnostic logging.

Key Procedures and Functions

The ETRM metadata documents a single externally visible program unit:

• SUMMARIZE_BASELINED_VERSIONS — Summarizes baselined budget versions for the grants projects being processed. It is the public entry point of the package and is responsible for reading baselined budget data and producing summarized records that reflect the current baselined position of the award. Because the metadata does not expose its parameter list, the exact signature should be confirmed against the deployed source in the target instance; its purpose, however, is to drive the summarization process that supports grant budget inquiry and baseline reporting.

In addition to this documented procedure, the package body contains the private procedure validate_profile_bem, which validates the project's budget entry method. It returns an error message code to the caller and is used internally before summarization proceeds, ensuring that the project is configured with a valid, active BEM before budget figures are aggregated.

Tables Accessed

The package reads and writes the following documented tables (accessed through APPS synonyms):

• GMS_BUDGET_VERSIONS and GMS_BUDGET_LINES — the Grants Management budget version and budget line tables that hold the award budget data being summarized.
• GMS_RESOURCE_ASSIGNMENTS — resource-level assignments associated with grant budgets.
• PA_BUDGET_VERSIONS and PA_BUDGET_ENTRY_METHODS — the Oracle Projects budget versions and the budget entry method definitions consulted by validate_profile_bem.
• PA_PROJECTS_ALL, PA_TASKS, and PA_IMPLEMENTATIONS — project, task, and implementation context used to resolve the projects being summarized.
• PA_RESOURCE_LIST_MEMBERS — resource list membership, which is directly relevant to the user's search term get_resource_list_id; this table supplies resource list identifiers used when resolving resource-based budget data.
• FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — profile option definitions and values, used to evaluate GMS_ENABLE_DEBUG_MODE and other runtime settings.
• DUAL and PLITBLM — standard single-row query and the PL/SQL table/index-by structures used for internal processing.

Usage Notes

GMS_SUMMARIZE_BUDGETS is an internal Grants Management utility rather than a form-level or user-facing API. It is typically invoked from other Grants Management packages — the metadata records that it is referenced by two other packages — most likely during award budget baseline processing, budget summarization for inquiry, or reporting flows. Custom code that calls this package must ensure the target project has a valid, active budget entry method; otherwise validate_profile_bem will reject the project. Because the package treats get_resource_list_id style logic through PA_RESOURCE_LIST_MEMBERS, callers working with resource list-based budgets should verify resource list configuration before invocation. Administrators should also set the GMS_ENABLE_DEBUG_MODE profile option when troubleshooting, since the package only emits debug output when that profile is enabled.