Search Results gms_task_budgets_v




Overview
Explore in AI Chat

Overview

GMS_TASK_BUDGETS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS – Grants Accounting product family. The ETRM metadata classifies the object as a VIEW with VALID status and annotates its description simply as "Retrofitted," indicating that the object was carried forward into the 12.1.1 / 12.2.2 code line to preserve backward compatibility for existing integrations, concurrent programs, and custom reports that reference the legacy name.

Functionally, the view exposes task-level budget amounts for grant-funded projects. It presents one row per combination of budget version, project, award, task, and budget attribute set, with cost, burdened cost, revenue, and quantity totals aggregated to the task level. Because it is a view rather than a table, it carries no storage of its own; all data is derived at runtime from its underlying objects. This makes it suitable for ad hoc reporting, Discoverer workbooks, OBIEE/BI Publisher extracts, and grant budget inquiry screens that must reconcile budgeted amounts against actual expenditures at the task granularity.

Underlying Base Objects

The documented dependency chain for GMS_TASK_BUDGETS_V is layered. The outermost view is defined over GMS_TASK_BUDGETS2_V, which supplies the detailed budget rows that are then aggregated. The definition also references two PL/SQL packages: GMS_BUDGET_UTILS and PA_TASK_UTILS. The former provides Grants Accounting budget utility functions used in deriving budget attributes, while the latter exposes PA_TASK_UTILS.SORT_ORDER_TREE_WALK, a hierarchical helper that generates a sortable ordering path for a task within its parent-child structure.

Specifically, the view selects from GMS_TASK_BUDGETS2_V and applies GROUP BY over BUDGET_VERSION_ID, PROJECT_ID, AWARD_ID, BUDGET_TYPE_CODE, VERSION_NUMBER, BUDGET_STATUS_CODE, TASK_ID, TASK_NUMBER, TASK_NAME, and PARENT_TASK_ID. The SORT_ORDER column is populated via PA_TASK_UTILS.SORT_ORDER_TREE_WALK(PARENT_TASK_ID, TASK_NUMBER), producing a deterministic tree-walk sequence suitable for ordered display of tasks. The four numeric measures — RAW_COST_TOTAL, BURDENED_COST_TOTAL, REVENUE_TOTAL, and QUANTITY_TOTAL — are each wrapped in SUM() to collapse lower-level detail into a single task-level figure.

Key Columns

  • BUDGET_VERSION_ID — Identifier of the budget version to which the task amounts belong; the primary grouping key for version-specific reporting.
  • PROJECT_ID — Project (and, for grant contexts, award project) that owns the task budget.
  • AWARD_ID — Award associated with the budget version, linking the row to the grant award record.
  • BUDGET_TYPE_CODE — Classifies the budget (for example, cost versus revenue basis) so distinct budget categories remain separable.
  • VERSION_NUMBER — Human-readable version sequence within the budget type.
  • BUDGET_STATUS_CODE — Lifecycle status of the budget version (such as working, submitted, or baseline).
  • TASK_ID / TASK_NUMBER / TASK_NAME — Task identifiers and descriptive attributes for the row.
  • PARENT_TASK_ID — Parent task in the task hierarchy, enabling rollup analysis.
  • SORT_ORDER — Tree-walk sort sequence derived from PA_TASK_UTILS, used to present tasks in hierarchical display order.
  • RAW_COST_TOTAL — Summed raw (unburdened) cost budgeted for the task.
  • BURDENED_COST_TOTAL — Summed burdened cost budgeted for the task.
  • REVENUE_TOTAL — Summed revenue budgeted for the task.
  • QUANTITY_TOTAL — Summed quantity budgeted for the task.

Common Use Cases and Queries

Typical usage centres on retrieving the budgeted cost and revenue position for each task under a given budget version. A representative query returning task-level budgeted amounts in display order is:

SELECT task_number, task_name, raw_cost_total, burdened_cost_total, revenue_total, quantity_total FROM apps.gms_task_budgets_v WHERE project_id = :p_project_id AND budget_version_id = :p_version_id ORDER BY sort_order;

Because SORT_ORDER is precomputed by PA_TASK_UTILS.SORT_ORDER_TREE_WALK, no CONNECT BY clause is required for ordered hierarchical output, though a recursive query against PARENT_TASK_ID can still be used where parent-level rollups are needed. Variance reporting compares BURDENED_COST_TOTAL from this view against actual cost from grants expenditure views, keyed on PROJECT_ID and TASK_ID. Revenue-versus-cost analysis selects both REVENUE_TOTAL and BURDENED_COST_TOTAL and filters on BUDGET_STATUS_CODE to restrict results to a baseline or approved version. Extracts for external reporting or data warehousing typically project the full column list grouped by AWARD_ID for sponsor-level summarization. Analysts should note that the view returns aggregated, task-level figures only; drill-down to the underlying detail requires querying GMS_TASK_BUDGETS2_V directly.