Search Results delete_draft_budget

Overview

The APPS.GMS_BUDGET_PUB package body is a public PL/SQL API that manages award and project budget processing within the Oracle E-Business Suite Grants Management (GMS) module. Its primary business purpose is to provide a controlled, callable interface for creating, validating, updating, submitting, baselining, and deleting award budgets and budget lines. The package encapsulates the logic required to keep the GMS_BUDGET_VERSIONS, GMS_BUDGET_LINES, and related funding and balance tables consistent throughout the budget lifecycle.

Because the package is classified as a PUB (public) API, it is intended for direct invocation by other Oracle EBS components, forms, concurrent programs, and customer extensions. This classification signals that the interface is supported and stable across releases, distinguishing it from private internal packages that may change without notice. The header comment (gmsmbupb.pls 120.10) confirms it is a long-standing, versioned component in the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. Five are trivial helper accessors that return missing-value and boolean constants used as sentinels in API calls: G_PA_MISS_NUM, G_PA_MISS_CHAR, G_PA_MISS_DATE, G_GMS_TRUE, and G_GMS_FALSE. These mirror Oracle's conventional missing-value pattern and allow callers to pass explicit "not supplied" indicators.

The remaining eleven procedures implement the budget workflow:

• CREATE_DRAFT_BUDGET — creates a new draft budget version for an award or project.
• ADD_BUDGET_LINE — adds an individual line to an existing budget.
• UPDATE_BUDGET — modifies header-level budget attributes.
• UPDATE_BUDGET_LINE — modifies attributes of an existing budget line.
• VALIDATE_BUDGET — performs validation checks on a budget before submission or baselining.
• SUBMIT_BUDG_CONC_PROCESS — submits the budget to a concurrent process for processing.
• SUBMIT_BASELINE_BUDGET — submits a request to baseline a budget.
• BASELINE_BUDGET — performs the baseline action that freezes an approved budget.
• DELETE_DRAFT_BUDGET — removes a draft budget and its associated detail. This is the procedure associated with the searched term "delete_draft_budget". It is typically invoked when a user discards an unsubmitted draft, and it must respect validity rules that prevent deletion of baselined or submitted budgets.
• DELETE_BUDGET_LINE — removes an individual budget line from a draft budget.
• SUMMERIZE_PROJECT_TOTALS — aggregates project funding and budget totals; the name reflects its internal spelling and it is used to refresh summary figures.

Each transactional procedure follows the standard ETRM error-handling convention, returning x_err_code, x_err_stage, and x_err_stack OUT parameters, and raising GMS_UTILITY-style exceptions on failure.

Tables Accessed

The package reads and writes a range of GMS and PA tables through APPS synonyms. Budget data resides in GMS_BUDGET_VERSIONS and GMS_BUDGET_LINES (with GMS_BUDGET_VERSIONS_S for sequence or surrogate handling). Funding and balance figures come from GMS_BALANCES, GMS_SUMMARY_PROJECT_FUNDINGS, GMS_INSTALLMENTS, and GMS_RESOURCE_ASSIGNMENTS (plus its _S companion). Award context is sourced from GMS_AWARDS and GMS_AWARDS_ALL. Budgetary control and packet processing touch GMS_BUDGETARY_CONTROLS and GMS_BC_PACKETS. Notifications generated during the workflow use GMS_NOTIFICATIONS. Profile values controlling debug behavior and defaults are read from FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES. The convert_projnum_to_id logic confirms cross-referencing to PA_PROJECTS for project number resolution.

Usage Notes

GMS_BUDGET_PUB is normally invoked from the Grants Management budget entry forms and from the concurrent programs that submit, validate, and baseline budgets. Custom integrations that need to programmatically create or remove budgets — for example, bulk loading awards or synchronizing budgets from external systems — should call the public procedures rather than issuing direct DML against the underlying GMS tables, because the API enforces validation, error stacking, and referential consistency. The DELETE_DRAFT_BUDGET procedure is the supported entry point for removing draft versions; callers must supply the standard error OUT parameters and should treat any non-zero x_err_code as a failure requiring review of x_err_stack. Debug output can be enabled by setting the GMS_ENABLE_DEBUG_MODE profile option to 'Y', which causes the package to emit log messages. The package is referenced by six other packages, so changes to its behavior can cascade across the GMS budget and award flows.