Search Results gms_task_budgets2_v




Overview
Explore in AI Chat

Overview

The view GMS_TASK_BUDGETS2_V is an Oracle E-Business Suite Grants Accounting (GMS) reporting object owned by the APPS schema. It presents task-level and award-level budget data drawn from Grants Accounting budget versions and Oracle Projects task structures, exposing a consolidated picture of budgeted amounts by budget version, project, award, and task. In EBS 12.1.1 and 12.2.2 this view functions primarily as a data source for Grants Accounting budget enquiry, reporting, and integration against project tasks. It allows callers to retrieve budget figures associated with a specific funding award alongside the Projects task hierarchy, removing the need to join budget lines, resource assignments, and tasks independently.

Underlying Base Objects

The view is defined over the following documented objects:

  • GMS_BUDGET_VERSIONS — the driving table for budget version, project, award, budget type, version number, and status.
  • GMS_BUDGET_LINES — supplies the monetary amounts (raw cost, burdened cost, revenue) and quantities per resource assignment.
  • GMS_RESOURCE_ASSIGNMENTS — links budget lines to tasks and carries the TRACK_AS_LABOR_FLAG used to determine quantity aggregation.
  • PA_TASKS — provides task ID, task number, task name, parent task, and top task identifiers for the Projects task hierarchy.
  • GMS_BUDGET_UTILS — a package whose GET_ENTRY_LEVEL_CODE function determines whether budget entry is performed at project level or at task level.

The view is a UNION ALL of several branches. When the entry level code is not P, task-level rows are produced by joining budget versions to tasks. When the entry level is P, a single project-level row is produced with zeroed task identifiers. Additional branches aggregate budget lines to their lowest or top-level tasks, returning summed raw cost, burdened cost, revenue, and labor-tracked quantities. This design allows a single query to return both detailed task budgets and rolled-up top-task totals.

Key Columns

Common Use Cases and Queries

Typical scenarios include retrieving all task budgets for an award, reporting budgeted cost and revenue by task, and comparing budget versions. A representative query:

  • SELECT BUDGET_VERSION_ID, PROJECT_ID, AWARD_ID, TASK_NUMBER, TASK_NAME, RAW_COST, BURDENED_COST, REVENUE FROM APPS.GMS_TASK_BUDGETS2_V WHERE AWARD_ID = :p_award_id AND BUDGET_STATUS_CODE = 'W';
  • Aggregation by award: SELECT AWARD_ID, SUM(RAW_COST), SUM(BURDENED_COST) FROM APPS.GMS_TASK_BUDGETS2_V GROUP BY AWARD_ID;

Because the object is a view, it should be queried rather than modified, and callers should expect task identifiers to be zero or null when budget entry is performed at project level.