Search Results diff_amount




Overview
Explore in AI Chat

Overview

GMS_RXI_BURDEN_VARIANCE_SUM_V is a reporting view in the Oracle EBS Grants Accounting (GMS) module. Its role is to summarise burden variance at the level of award, project, and task, aggregating the underlying transaction-level detail produced by the burden variance process. In the Oracle EBS 12.1.1 and 12.2.2 releases, Grants Accounting supports award and project burdening for sponsored research, and this view provides the consolidated totals that are used in RXI (Research Extensions / information discovery) reporting against burden variance.

The view is derived from GMS_RXI_BURDEN_VARIANCE_V, a lower-level burden variance view, joined to PA_PROJECTS_ALL, GMS_AWARDS_ALL, and PA_TASKS. It exposes one row per combination of award, project, and task, with aggregated burden amounts that allow users to compare the burden that was actually charged against the burden that should have been applied. This makes it useful for reconciliation, audit, and grants compliance reporting.

Underlying Base Objects

The view is defined over four object types, referenced within an inline subquery:

Aggregation is performed by award, project, and task, and the outer query applies a status decode and a variance-presence flag. The joins are on AWARD_ID, PROJECT_ID, and TASK_ID, ensuring that burden variance detail is linked consistently across the award, project, and task entities.

Key Columns

  • AWARD_NUMBER, PROJECT_NUMBER, TASK_NUMBER — the descriptive identifiers for the award, project, and task represented in the row.
  • PROJECT_ID, TASK_ID, AWARD_ID — the surrogate keys used to join and identify each record.
  • STATUS — the award status, returned from GMS_AWARDS_ALL.
  • STATUS_FLAG — derived as DECODE(STATUS, 'CLOSED', 'N', 'Y'), indicating whether the award is still active for reporting purposes.
  • END_DATE_ACTIVE — the award end date used in effectivity checks.
  • REP_VARIANCE — derived as DECODE(NVL(DIFF_AMOUNT,0),0,'N','Y'), flagging whether a non-zero variance exists and therefore whether the row should be reported as a true variance.
  • BTC_TOTAL — the total burden cost element amount in the base currency.
  • ADJ_AMOUNT — the adjustment amount applied to the burden variance.
  • BURDEN_SHOULD_BE — the burden amount that should have been charged, i.e. the calculated expected burden total.
  • DIFF_AMOUNT — the difference between the burden actually charged and BURDEN_SHOULD_BE.

Common Use Cases and Queries

This view is typically used for grants burden reconciliation reporting. A common requirement is to list all awards where a burden variance exists, filtering out zero-variance rows and closed awards:

SELECT award_number, project_number, task_number, btc_total, adj_amount, burden_should_be, diff_amount FROM gms_rxi_burden_variance_sum_v WHERE rep_variance = 'Y' AND status_flag = 'Y' ORDER BY award_number, project_number, task_number;

A second scenario is summing burden variance by award for a period-end reconciliation:

SELECT award_number, SUM(btc_total) btc, SUM(burden_should_be) should_be, SUM(diff_amount) variance FROM gms_rxi_burden_variance_sum_v GROUP BY award_number;

A third scenario is identifying tasks whose adjusted burden exceeds the expected burden, supporting audit sampling. Because the view already aggregates detail, users should avoid re-aggregating by task without including all key columns, and should account for the DECODE flags when filtering.

Note: The ETRM metadata records this view as "Not implemented in this database" in the supplied documentation, and no base objects are formally documented. The definitions above are therefore derived from the view text provided and from standard Oracle EBS Grants Accounting semantics.