Results for “get_entry_level_code”

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

Overview

GMS_BUDGET_UTILS is the core budget utility package body for the Oracle EBS Grants Management (GMS) module. It centralizes the logic used to locate, validate, and manipulate award and project budget data stored in the GMS budgeting tables, and it exposes that logic as a reusable PL/SQL API rather than duplicating it across the forms, concurrent programs, and interfaces that touch budgets. In Oracle EBS 12.1.1 and 12.2.2 the package is owned by APPS and is classified as an OTHER API. It is referenced by nine other packages, which confirms its role as a shared service layer for grants budget processing.

Key Procedures and Functions

The package exposes twenty-five documented procedures and functions, which fall into several functional groups:

• Version resolution: GET_DRAFT_VERSION_ID, GET_BASELINED_VERSION_ID, and GET_ORIGINAL_VERSION_ID retrieve the appropriate budget version identifier for a given project, award, and budget type, distinguishing working, baselined, and original versions. GET_DRAFT_VERSION_ID, for example, selects from GMS_BUDGET_VERSIONS where the budget status is 'W' or 'S' and raises GMS_BU_CORE_NO_VERSION_ID when no row exists.
• Entry method and type lookup: GET_DEFAULT_ENTRY_METHOD_CODE, GET_BUDGET_ENTRY_METHOD_CODE, GET_DEFAULT_RESOURCE_LIST_ID, GET_BUDGET_TYPE_CODE, GET_BUDGET_AMOUNT_CODE, GET_CHANGE_REASON_CODE, and SET_ENTRY_LEVEL_CODE resolve the entry method, resource list, budget type, amount code, change reason, and entry level values used by budget entry screens. These are the routines most closely related to the user search term "check_entry_method_flags", which concerns validation of entry method flag settings during budget entry.
• Existence and validation checks: CHECK_PROJ_BUDGET_EXISTS, CHECK_TASK_BUDGET_EXISTS, CHECK_RESOURCE_MEMBER_LEVEL, CHECK_OVERLAPPING_DATES, CHECK_CURRENCY_UOM, and VERIFY_BUDGET_RULES validate that budgets exist, that resource members are at the correct level, that date ranges do not overlap, that currency and unit of measure combinations are consistent, and that budget business rules are satisfied.
• Amount and date retrieval: GET_PROJ_BUDGET_AMOUNT, GET_TASK_BUDGET_AMOUNT, GET_PROJECT_TASK_TOTALS, and GET_VALID_PERIOD_DATES return aggregated budget amounts at project and task level and determine valid period boundaries, supporting reporting and allocation logic.

Tables Accessed

The package reads and, where applicable, writes budget and project setup data through APPS synonyms:

• GMS_BUDGET_VERSIONS, GMS_BUDGET_LINES: version metadata, budget amounts, and line-level detail.
• GMS_AWARDS and GMS_AWARDS_ALL: award context used to scope budget lookups.
• GMS_RESOURCE_ASSIGNMENTS: resource assignment and member-level validation.
• PA_PROJECTS, PA_TASKS, PA_PROJECT_TYPES: project and task structure and project type rules.
• PA_BUDGET_ENTRY_METHODS, PA_BUDGET_TYPES: entry method and budget type definitions.
• PA_RESOURCE_LIST_MEMBERS: resource list membership for default and validation logic.
• DUAL: used for scalar computations and function returns.

Usage Notes

GMS_BUDGET_UTILS is invoked primarily from the Grants Management budget entry forms and from concurrent programs that create, baseline, or validate budgets. The nine packages that reference it call it to reuse version resolution, entry method lookup, and validation logic rather than querying GMS tables directly. Custom code extending grants budgeting should call these APIs in preference to direct table access, because the package centralizes error handling through GMS_ERROR_PKG (for example, GMS_BU_CORE_NO_VERSION_ID and GMS_UNEXPECTED_ERROR) and honors the GMS_ENABLE_DEBUG_MODE profile option for diagnostic logging. The debug flag is read once at package initialization, so the profile setting must be in place before the session begins.