Search Results get_proj_budget_amount

Overview

GMS_BUDGET_UTILS is a PL/SQL utility package in the APPS schema that supports the Oracle E-Business Suite Grants Management (GMS) budgeting subsystem. It provides the shared, low-level building blocks used by the higher-level budget processing packages — most notably GMS_BUDGET_CORE and GMS_BUDGET_PUB — and by a set of Grants Management views including GMS_RES_V, GMS_RESG_V, GMS_TASK_BAL_V, GMS_TASK_BUDGETS_V, GMS_TASK_BUDGETS2_V, and GMS_TASK_V. The package centralizes common lookups, validations, and amount-derivation logic so that budget entry, baselining, and reporting functions behave consistently across the application.

The package is classified as an OTHER API rather than a public interface, indicating that it is intended primarily for internal consumption by other GMS and Oracle Projects components rather than for direct third-party integration. It carries a VALID status and is owned by APPS, and it is referenced by nine other packages in the environment.

Key Procedures and Functions

The documented metadata lists 25 procedures and functions, of which the following are named. They fall into three broad categories.

• Version resolution: GET_DRAFT_VERSION_ID, GET_BASELINED_VERSION_ID, and GET_ORIGINAL_VERSION_ID return the appropriate budget version identifiers for a given budget, enabling callers to target the draft, baselined, or original version without hardcoding status logic.
• Configuration and code lookups: GET_BUDGET_AMOUNT_CODE, GET_DEFAULT_RESOURCE_LIST_ID, GET_DEFAULT_ENTRY_METHOD_CODE, GET_BUDGET_TYPE_CODE, GET_BUDGET_ENTRY_METHOD_CODE, GET_CHANGE_REASON_CODE, and SET_ENTRY_LEVEL_CODE supply defaulted or configured codes used when constructing and validating budget records.
• Validation and calculation: CHECK_CURRENCY_UOM, CHECK_PROJ_BUDGET_EXISTS, CHECK_TASK_BUDGET_EXISTS, CHECK_RESOURCE_MEMBER_LEVEL, CHECK_OVERLAPPING_DATES, and VERIFY_BUDGET_RULES perform existence, currency/unit-of-measure, hierarchy-level, and date-overlap checks. GET_PROJ_BUDGET_AMOUNT, GET_TASK_BUDGET_AMOUNT, GET_PROJECT_TASK_TOTALS, and GET_VALID_PERIOD_DATES derive budget amounts and valid date ranges for projects and tasks.

Tables Accessed

GMS_BUDGET_UTILS reads and writes through APPS synonyms across both Grants and Oracle Projects tables. Budget and award context is drawn from GMS_AWARDS, GMS_AWARDS_ALL, GMS_BUDGET_VERSIONS, GMS_BUDGET_LINES, and GMS_RESOURCE_ASSIGNMENTS. Project and task structure, budget types, entry methods, and resource list membership are sourced from PA_PROJECTS, PA_PROJECT_TYPES, PA_TASKS, PA_BUDGET_TYPES, PA_BUDGET_ENTRY_METHODS, and PA_RESOURCE_LIST_MEMBERS. DUAL is used for single-row lookups. These tables support the package's core responsibilities: resolving versions, defaulting codes, validating budget rules, and computing project and task budget totals.

Usage Notes

Because it is an internal utility package, GMS_BUDGET_UTILS is not typically invoked directly from Oracle Forms or from concurrent program parameters by end users. It is called from within the Grants Management budget entry and baselining flows, and its functions are exposed through the GMS_TASK_BUDGETS_V and related views used for reporting and inquiry. Custom code should prefer the public entry points in GMS_BUDGET_PUB rather than calling GMS_BUDGET_UTILS directly, since the utility signatures and behavior are implementation details subject to change between releases. When troubleshooting budget behavior in Oracle EBS 12.1.1 or 12.2.2, this package is a useful reference for understanding how draft, baselined, and original versions are distinguished and how budget amounts are validated.