Results for “gms_budget_versions_draft_v”

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

Overview

The GMS_BUDGET_VERSIONS_DRAFT_V view is a Grants Accounting (GMS) dictionary object owned by the APPS schema. It is documented as a retrofitted object, indicating that its definition was ported forward across Oracle E-Business Suite releases and remains aligned with the 12.1.1 and 12.2.2 code lines. Its purpose is to expose draft-oriented budget version records for awards and projects, combining the operational columns of the underlying budget version entity with decoded lookup meanings, resource list names, and derived security, entry-method, and baseline attributes. The result is a single flat row per budget version that can be consumed directly by Oracle Forms, OAF pages, concurrent programs, and custom reports without requiring the caller to re-implement the decode logic or the Grants security model.

A distinguishing characteristic of the view is that it validates the caller's access rights per row through the GMS_SECURITY package. Both ALLOW_QUERY and ALLOW_UPDATE are invoked so that the query returns only awards the current responsibility is permitted to see, and the same row carries an update-permission indicator. This makes the view suitable both for read-only reporting and for populating a UI that must conditionally enable maintenance actions.

Underlying Base Objects

The documented base objects for the view are: GMS_BUDGET_VERSIONS (synonym), PA_BUDGET_ENTRY_METHODS (synonym), PA_BUDGET_TYPES (synonym), PA_LOOKUPS (view), PA_RESOURCE_LISTS (view), FND_PROFILE (package), PA_CROSS_BUSINESS_GRP (package), GMS_SECURITY (package), and DUAL. The central driver is GMS_BUDGET_VERSIONS, which appears twice in the definition: once aliased V for the current draft version and once aliased B for the baselined version, allowing the view to present both current and baseline quantities side by side.

Lookup meanings are resolved through multiple aliased references to PA_LOOKUPS — for budget status, change reason code, labor unit of measure (current and baseline), and related decode columns. PA_BUDGET_ENTRY_METHODS and PA_BUDGET_TYPES supply entry-method and budget-type context, while PA_RESOURCE_LISTS provides the resource list name. The security predicates are applied through GMS_SECURITY, with FND_PROFILE and PA_CROSS_BUSINESS_GRP available to support profile and cross-business-group logic inside the packaged security functions.

Key Columns

• BUDGET_VERSION_ID, PROJECT_ID, AWARD_ID — Primary identity of the budget version and its owning project and award.
• BUDGET_TYPE_CODE, VERSION_NUMBER, VERSION_NAME, DESCRIPTION — Identification and descriptive information for the version.
• BUDGET_STATUS_CODE and its MEANING — Lookup-decoded status of the draft version.
• CURRENT_FLAG, ORIGINAL_FLAG, CURRENT_ORIGINAL_FLAG, RESOURCE_ACCUMULATED_FLAG — Flags describing the version's role in the budget lifecycle.
• RESOURCE_LIST_ID, R.NAME — Resource list and its decoded name.
• BUDGET_ENTRY_METHOD_CODE and M.BUDGET_ENTRY_METHOD — Entry method used to build the budget.
• LABOR_QUANTITY, LABOR_UNIT_OF_MEASURE, RAW_COST, BURDENED_COST, REVENUE — Current draft amounts and quantities. The same columns are repeated from the baseline alias (B) with a separate BASELINED_DATE.
• BASELINED_BY_PERSON_ID, BASELINED_DATE — Who baselined the version and when.
• WF_STATUS_CODE — Workflow status of the version.
• SUBSTR(GMS_SECURITY.ALLOW_UPDATE(...)) — Derived per-row update permission indicator.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CONC_REQUEST_ID.

Common Use Cases and Queries

The view is typically consumed by GMS budget entry and award management screens, and by extract programs that require the draft budget position alongside baseline figures. A representative query lists accessible draft versions for an award:

• SELECT budget_version_id, version_number, version_name, meaning, raw_cost, burdened_cost, revenue FROM gms_budget_versions_draft_v WHERE award_id = :award_id ORDER BY version_number DESC;
• SELECT budget_version_id, baselined_date, labor_quantity FROM gms_budget_versions_draft_v WHERE current_flag = 'Y' AND budget_status_code = 'DRAFT';
• SELECT budget_version_id, SUBSTR(GMS_SECURITY.ALLOW_UPDATE(...),1,1) ... is embedded by the view itself; joining to GMS_BUDGET_VERSIONS on BUDGET_VERSION_ID is standard when full column access is required.

Because security is enforced inside the view, report authors should avoid substituting GMS_BUDGET_VERSIONS directly when row-level award access matters. Filtering on PROJECT_ID, AWARD_ID, or BUDGET_STATUS_CODE preserves the security predicate while narrowing the result set.