Search Results gms_commitment_burden_v




Overview
Explore in AI Chat

Overview

The GMS_COMMITMENT_BURDEN_V view is a reporting object owned by the APPS schema in Oracle E-Business Suite, belonging to the GMS – Grants Accounting product family. It presents commitment (encumbrance) and burdened cost information for grants-funded transactions, combining obligations recorded against awards with their associated indirect cost (burden) components. The view is defined as a UNION ALL of two branches: a first branch drawing raw encumbered amounts from GMS_COMMITMENT_ENCUMBERED_V, and a second branch computing burdened cost by multiplying burdenable raw cost by the applicable compiled multiplier from PA_COMPILED_MULTIPLIERS. Both branches are aggregated by grouping keys such as document type, transaction source, commitment number, project, task, award, expenditure type, expenditure item date, organization, vendor, unit of measure, unit price, and GL date. Within the Grants Accounting module, this view supports burdened commitment reporting, award and project fund analysis, and integration with purchasing and project costing sub-ledgers.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view references the following base objects:

  • GMS_COMMITMENT_ENCUMBERED_V (VIEW) – the primary source of encumbered commitment line data, providing document type, transaction source, commitment number, project/task/award identifiers, expenditure type, expenditure item date, organization, vendor, unit of measure, unit price, period, burdenable raw cost, and indirect compiled set identifiers.
  • PA_COMPILED_MULTIPLIERS (SYNONYM) – supplies the compiled multiplier applied to burdenable raw cost to derive the burdened amount per indirect cost code and cost base.
  • PA_COST_BASE_EXP_TYPES (SYNONYM) – restricts eligible base expenditure types, filtered on COST_BASE_TYPE = 'INDIRECT COST'.
  • PA_IND_COST_CODES (SYNONYM) – joins indirect cost codes to compiled multipliers.
  • PA_IND_COMPILED_SETS (SYNONYM) – validates the organization, cost base, and rate schedule revision context.
  • PA_IND_RATE_SCH_REVISIONS (SYNONYM) – links the cost plus structure to the applicable rate schedule revision.
  • PA_CMT_UTILS (PACKAGE), GMS_BUDGET_BALANCE (PACKAGE), and PO_INTG_DOCUMENT_FUNDS_GRP (PACKAGE) – supporting programmatic objects documented as referenced by the view’s defining logic.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting burdened commitments by award and expenditure type, reconciling commitment versus budget balances, and analyzing burdenable versus burdened amounts for a project/organization/period combination. The EXPENDITURE_ITEM_DATE column is a frequent filter or grouping key, particularly for period-based commitment roll-forward reporting.

SELECT award_id,
       project_id,
       task_id,
       expenditure_type,
       expenditure_item_date,
       SUM(acct_raw_cost)      raw_cost,
       SUM(acct_burdened_cost) burdened_cost
  FROM apps.gms_commitment_burden_v
 WHERE award_id = :p_award_id
   AND expenditure_item_date BETWEEN :p_start AND :p_end
 GROUP BY award_id, project_id, task_id,
          expenditure_type, expenditure_item_date
 ORDER BY expenditure_item_date, expenditure_type;

A second pattern reconciles commitment totals per document to GL dates, joining the view to purchasing or project costing data by CMT_NUMBER. Because the view is an aggregated UNION ALL, queries should apply consistent filters to both branches to avoid double counting; the second branch returns zero quantity and raw cost, contributing only burdened cost. Analysts should also confirm that IND_COMPILED_SET_ID is populated and that BURDENABLE_RAW_COST is non-zero, since these conditions gate inclusion in the burdened-cost branch.