Results for “gms_budg_cont_setup”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMS_BUDG_CONT_SETUP is an Oracle Application Object Library PL/SQL package body owned by the APPS schema, classified under the OTHER API category. It is a member of the Grants Management (GMS) product family and serves as a server-side utility for establishing and maintaining budgetary control records associated with awards, tasks, and resource lists. Within Oracle EBS 12.1.1 and 12.2.2, budgetary controls determine how expenditures against an award are validated and whether funds checks are enforced at the award, task, or resource level. This package encapsulates the setup logic required to generate those control rows consistently, insulating callers from the underlying table structures in GMS_BUDGETARY_CONTROLS and GMS_BUDGETARY_CONTROLS_S.

The package body carries a VALID status in the ETRM repository and depends on several standard EBS components, including FND_GLOBAL for session context, FND_PROFILE for profile option retrieval, GMS_AWARDS, GMS_ERROR_PKG, and Public synonyms such as DUAL and STANDARD. It is referenced by two other database objects and does not itself reference any object outside the documented dependency list.

Key Procedures and Functions

The package body exposes three documented program units:

• INSERT_REC — Performs the low-level insert of a budgetary control record. It is the workhorse routine that writes a single row into the budgetary controls schema, applying the values supplied by its caller and any session-derived defaults. Because it is not intended for direct external invocation, it abstracts the column-level details of the underlying tables.
• CREATE_RECORDS — Drives the creation of one or more budgetary control records in bulk. It coordinates the setup activity, determining which award, task, and resource list combinations require control rows and then delegating the actual inserts, typically to INSERT_REC.
• BUD_CTRL_CREATE — The primary entry point for budgetary control creation. It encapsulates the end-to-end setup process, evaluates the applicable entry method and resource list definitions, and generates the control configuration required for subsequent funds checking against the award.

Parameter lists are not reproduced here, as the documented metadata does not enumerate them; callers should inspect the package specification for exact signatures.

Tables Accessed

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

• GMS_BUDGETARY_CONTROLS and GMS_BUDGETARY_CONTROLS_S — the base and translation tables that store the budgetary control definitions created by this package.
• GMS_AWARDS — supplies award attributes required to scope budgetary controls to the correct award.
• PA_BUDGET_ENTRY_METHODS — provides the valid budget entry methods that govern how budgets are entered and validated.
• PA_RESOURCE_LIST_MEMBERS — identifies the resources included in a resource list, which drives control granularity.
• PA_TASKS — supplies task structure information so controls can be attached at the appropriate task level.
• DUAL — used for single-row queries and expression evaluation.

Usage Notes

GMS_BUDG_CONT_SETUP is not a public, customer-facing API in the same sense as the GMS_AWARD_PUB or GMS_BUDGET_PUB packages. It is invoked internally by Grants Management setup flows, most commonly when an award is configured for budgetary control or when the control structure must be regenerated after changes to awards, tasks, or resource lists. Integration points include the Grants Management forms that capture award and budgetary control setup, and concurrent or batch processes that create controls for multiple awards. The package relies on FND_GLOBAL for session identity and FND_PROFILE for configuration context, so it must be executed within an initialized EBS session. Custom code should not call INSERT_REC directly; where programmatic creation is required, BUD_CTRL_CREATE is the appropriate documented entry point. The absence of documented parameters and the internal nature of INSERT_REC reinforce that this package is intended for framework-level use rather than direct customer extension.