Results for “budget_amount”

50+ results




Overview
Explore in AI Chat

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

Overview

GMS_STATUS_ACCUM_PROJECT_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. It presents grant award and project financial status data in an aggregated, project-level form. The view consolidates revenue, budget, cost, and commitment balances into a single row per award and project combination, making it suited to inquiry screens, grant status reporting, and downstream integration extracts that require accumulated totals rather than transactional detail.

The view is documented with a status of VALID and supports Oracle EBS releases 12.1.1 and 12.2.2. Its principal design characteristic is the pivot from a lower-level base view that holds individual status accumulation lines into a summarized result set. Because the columns exposed by the view include TOTAL_REVENUE, the object is frequently referenced by users and developers searching for revenue figures at the award/project level.

Underlying Base Objects

Per the documented ETRM metadata, GMS_STATUS_ACCUM_PROJECT_V is defined exclusively over one referenced base object:

The base object is itself a view, not a table. This layering means the final aggregation logic of GMS_STATUS_ACCUM_PROJECT_V is applied on top of whatever joins and filters the base view applies to the underlying Grants Accounting transaction and budget tables. The view text supplied in the documentation shows a straightforward grouping pattern:

Because grouping is keyed on the full project identity set, each distinct award/project pairing yields exactly one aggregate row. Consumers should therefore treat the view as a summary layer and query the base view directly when line-level accumulation detail is required.

Key Columns

  • AWARD_ID — Identifier of the grant award to which the accumulated amounts belong.
  • PROJECT_ID — Identifier of the project associated with the award; part of the grouping key.
  • PROJECT_NUMBER — User-facing project number, carried through the grouping for reporting convenience.
  • PROJECT_NAME — Descriptive project name, likewise grouped and exposed for display.
  • TOTAL_REVENUE — Summed revenue recognized against the award/project combination; the column most frequently cited in searches for grant revenue totals.
  • BUDGET_AMOUNT — Summed budgeted amount for the project.
  • ACTUAL_COST — Summed actual costs incurred.
  • REQUISITION_AMOUNT — Summed requisition commitments.
  • PURCHASE_ORDER_AMOUNT — Summed purchase order commitments.
  • SUPPLIER_INVOICE_AMOUNT — Summed supplier invoice amounts.
  • MANUAL_ENCUMBRANCE_AMOUNT — Summed manually entered encumbrances.

Together the commitment columns (requisition, purchase order, supplier invoice, manual encumbrance) support budget-versus-commitment and budget-versus-actual analysis alongside revenue.

Common Use Cases and Queries

Typical uses include grant portfolio dashboards, award status inquiries, and extracts feeding data warehouses. A simple project-level revenue query is shown below.

  • SELECT award_id, project_number, project_name, total_revenue FROM apps.gms_status_accum_project_v WHERE award_id = :award_id;
  • SELECT project_number, total_revenue, budget_amount, actual_cost FROM apps.gms_status_accum_project_v WHERE budget_amount > 0 ORDER BY project_number;
  • SELECT award_id, SUM(total_revenue) revenue, SUM(actual_cost) cost FROM apps.gms_status_accum_project_v GROUP BY award_id;

Because aggregation already occurs within the view, additional SUM operations at a higher grain (for example, by award only) are valid and commonly used. Filters on AWARD_ID or PROJECT_ID typically give the best performance, as these columns participate in the view's internal grouping.