Search Results budget_status_code




Overview
Explore in AI Chat

Overview

APPS.GMS_TASK_BUDGETS_V is a reporting view in the Oracle E-Business Suite Grants Management (GMS) module. It exposes task-level budget information for awards and projects, aggregating cost, revenue, and quantity measures by budget version and task. The view is designed to support budget inquiry, reporting, and integration scenarios where consumers require summarized budget figures organized by the task hierarchy rather than at the transaction detail level.

Because grants budgets in Oracle EBS are typically captured at multiple levels — project, award, and task — this view consolidates lower-level budget lines into a single row per task within each budget version. It is frequently used to answer questions such as "what is the budgeted raw cost for each task on this award?" and to drive user-facing pages and reports that display budgets alongside task numbers and task names. The inclusion of TASK_NUMBER makes the view particularly useful when users search on the human-readable task identifier rather than internal TASK_ID values.

Underlying Base Objects

The view is defined over the following documented base objects:

  • GMS_TASK_BUDGETS2_V (VIEW) — the immediate source of rows. This is the detail-oriented view that supplies budget version, project, award, task, and measure columns that GMS_TASK_BUDGETS_V then aggregates.
  • PA_TASK_UTILS (PACKAGE) — invoked through PA_TASK_UTILS.SORT_ORDER_TREE_WALK(PARENT_TASK_ID, TASK_NUMBER) to produce the SORT_ORDER column, which orders tasks in the correct hierarchical tree sequence.
  • GMS_BUDGET_UTILS (PACKAGE) — referenced as a base object supporting budget processing utilities; functionally related to the budget version and status logic surfaced by the view.

The defining SELECT joins no tables directly; instead it groups the rows returned by GMS_TASK_BUDGETS2_V using GROUP BY over the descriptive columns and applies SUM to the measure columns. This structure means the view inherits all filtering and security behavior of the underlying view while presenting a rolled-up result set.

Key Columns

  • BUDGET_VERSION_ID — identifier for the specific budget version.
  • PROJECT_ID / AWARD_ID — the project and award to which the budget belongs.
  • BUDGET_TYPE_CODE — the classification of the budget (for example, cost or revenue budget type).
  • VERSION_NUMBER — the version sequence for the budget.
  • BUDGET_STATUS_CODE — the workflow status of the budget version.
  • TASK_ID / TASK_NUMBER / TASK_NAME — internal task identifier, user-visible task number, and description.
  • PARENT_TASK_ID — parent task reference; used together with TASK_NUMBER to compute SORT_ORDER.
  • SORT_ORDER — derived ordering key returned by PA_TASK_UTILS.SORT_ORDER_TREE_WALK, enabling hierarchical display.
  • RAW_COST_TOTAL / BURDENED_COST_TOTAL / REVENUE_TOTAL / QUANTITY_TOTAL — summed budget amounts and quantities per task.

Common Use Cases and Queries

Typical usage includes budget inquiry screens, award-level budget reports, and extracts that feed downstream costing or reporting. A common query filters by award and orders by the derived sort order so tasks appear in hierarchy sequence:

  • SELECT task_number, task_name, raw_cost_total, burdened_cost_total FROM apps.gms_task_budgets_v WHERE award_id = :award_id AND budget_status_code = 'B' ORDER BY sort_order;
  • Aggregating revenue across tasks for a given project and budget version.
  • Joining to PA_TASKS on TASK_ID to enrich output with additional task attributes.

Because the view performs GROUP BY and SUM, consumers should not expect row-level budget line detail; GMS_TASK_BUDGETS2_V should be queried instead when breakdown granularity is required.