Search Results gms_client_extn_budget

Overview

GMS_CLIENT_EXTN_BUDGET is a public client extension package in the Oracle Grants Accounting (GMS) module. Its purpose is to let implementers override or augment certain budget validations that the standard Grants budgeting engine would otherwise enforce unconditionally. Because Grants Accounting budgets are subject to strict institutional controls — particularly around award and project dates — the standard validation logic can be overly rigid for legitimate business scenarios. This extension package provides a supported, upgrade-safe hook through which customers can relax or replace those checks without modifying Oracle-owned code.

The package is registered as an active public API with a compatibility rating of S (supported), and it is scoped to the GMS_AWARD business entity. Its lifecycle status confirms it remains the sanctioned extension point at the 12.1.1 and 12.2.2 releases. The reference document cited in the metadata is the Oracle Grants Accounting User's Guide (120gmsug.pdf), and the source header identifies the shipped version as 120.4.

Key Procedures and Functions

• Calc_Raw_Cost — Computes the raw (unburdened) cost for a budget line, returning the value through an output parameter along with error code and error message outputs. It receives budget version, project, task, resource list member, resource list, resource, date range, period name, quantity, and product code context, allowing a client extension to substitute custom raw-cost derivation logic.
• Calc_Burdened_Cost — Derives the burdened cost from a supplied raw cost value, again within full budgeting context. Because the raw cost is an input here, the procedure is intended to apply custom burdening rules or rate treatments that differ from standard burden schedules.
• Verify_Budget_Rules — The principal validation entry point. It accepts a draft budget version, a mark-as-original indicator, the triggering event, project, budget type, resource list, project type class, creating user, and calling module. Through its output parameters it reports a warnings-only flag, an error message count, an error code, and an error message, permitting the extension to either permit, warn on, or reject a budget submission.
• Override_Inst_Date_Validation — A dedicated procedure, introduced against a specific bug reference, that controls whether the installation-date (institution date) validation is bypassed. This is the object most commonly sought when a budget is rejected because line or transaction dates fall outside the award's installation date window.

Tables Accessed

The packaged metadata does not enumerate base tables accessed directly, as the extension reads its context through parameters rather than its own SQL. In practice the procedures are driven by the caller — principally the Grants budgeting engine — which supplies values originating from the budget version, project, task, resource list, and award tables. Client implementations of these procedures frequently query GMS_AWARD, the project and task definitions, and resource list tables to support their custom logic. No APPS synonyms are documented for direct table references.

Usage Notes

This package is not invoked directly by end users. It is a specification intended to be replaced by a customer-owned body in the APPS schema, following the standard client-extension pattern: the shipped package spec remains intact while the body is reimplemented. The budgeting engine calls Verify_Budget_Rules during budget validation and Calc_Raw_Cost/Calc_Burdened_Cost during budget line processing; Override_Inst_Date_Validation is consulted when the installation-date check is evaluated.

Typical invocation therefore occurs through Grants Accounting budget entry forms and the related budgeting concurrent programs, and the package may also be called from custom code submitted as part of award or budget automation. Two other packages depend on GMS_CLIENT_EXTN_BUDGET, so any replacement body must preserve the documented signatures exactly. The source header references version 120.4, and the presence of bug-referenced procedures indicates the interface has been extended over time to expose additional validation overrides.