Search Results gms_rxi_burden_variance

Overview

GMS_RXI_BURDEN_VAR_RUNID_V is a reporting view in the Oracle E-Business Suite Grants Accounting (GMS) module, delivered as part of the Grants expenditure and burdening infrastructure. The view consolidates burden variance information for sponsored awards, exposing the relationship between awards, projects, tasks, and the expenditure organizations that generated the underlying raw costs. Its principal role is to support reconciliation of burden calculated against burden that should have been applied, surfacing any variance between the two figures at the request, award, project, and task level. In ETRM 12.1.1 and 12.2.2 the view is documented as not implemented in a standard database, meaning it is a reference or supplementary object that may appear in certain patched environments or Grants installations where variance reporting against a specific run identifier is required. The view is read-only by design; it aggregates transactional burden variance rows and joins them to descriptive master data to yield a report-ready result set.

Underlying Base Objects

The view is defined as a join across several core EBS tables and one Grants-specific variance object:

• GMS_RXI_BURDEN_VARIANCE VAR — the driving table, holding expenditure type, request, source, and burden amount columns per award/project/task.
• PA_PROJECTS_ALL P — the Projects master, supplying PROJECT_NUMBER via SEGMENT1 and PROJECT_ID.
• GMS_AWARDS_ALL A — the Awards master, supplying AWARD_NUMBER, AWARD_ID, STATUS, and END_DATE_ACTIVE.
• PA_TASKS T — the Tasks table, supplying TASK_NUMBER and TASK_ID.
• HR_ORGANIZATION_UNITS O — the organization definition, supplying the expenditure organization name via O.NAME.

The joins are enforced on AWARD_ID, PROJECT_ID, and TASK_ID, with an additional filter that VAR.SOURCE_ID be greater than zero and that VAR.SOURCE_ORG_ID equal O.ORGANIZATION_ID. This structure ties each variance row to the organization that originated the expenditure.

Key Columns

• AWARD_NUMBER, PROJECT_NUMBER, TASK_NUMBER — descriptive identifiers for the sponsored award, its funded project, and associated task.
• AWARD_ID, PROJECT_ID, TASK_ID — surrogate keys used to join back to base tables or other Grants views.
• STATUS, STATUS_FLAG — award status, with STATUS_FLAG derived so a CLOSED award yields 'N' and all other statuses yield 'Y'.
• END_DATE_ACTIVE — the active end date of the award.
• EXPENDITURE_ORG — the name of the expenditure organization from HR_ORGANIZATION_UNITS, the field most relevant to the user's search for "expenditure_org".
• EXPENDITURE_TYPE — the expenditure category to which the burden variance pertains.
• REQUEST_ID, SOURCE_ID — the burden run and source transaction identifiers used to trace the variance back to its origin.
• REP_VARIANCE — a flag decoding DIFF_AMOUNT to 'Y' when a non-zero variance exists and 'N' otherwise.
• BTC_TOTAL, ADJ_AMOUNT, BURDEN_TOTAL (BURDEN_SHOULD_BE), DIFF_AMOUNT, RAW_COST — the quantitative columns: burden total from cost, adjustment amount, expected burden, variance, and raw cost respectively.

Common Use Cases and Queries

Typical usage centers on burden variance reporting and expenditure organization analysis for sponsored awards. Analysts filter on REP_VARIANCE = 'Y' to isolate awards where applied burden differs from expected burden, then group by EXPENDITURE_ORG to identify which organizations drive the variances.

SELECT expenditure_org,
       expenditure_type,
       award_number,
       project_number,
       task_number,
       burden_should_be,
       adj_amount,
       diff_amount,
       raw_cost
  FROM gms_rxi_burden_var_runid_v
 WHERE rep_variance = 'Y'
   AND status_flag = 'Y'
 ORDER BY expenditure_org, award_number;

Because the view is documented as not implemented in the standard database, a query against it may raise ORA-00942 unless the object has been created by a Grants patch or custom implementation. In such environments the SELECT text supplied in the ETRM metadata can be used to construct an equivalent query directly against GMS_RXI_BURDEN_VARIANCE and its joined base tables, preserving the same column aliases so downstream reports remain compatible.