Search Results burdenable_cost




Overview

GMS_RXI_EXP_DETAILS_V is a reporting view in the Oracle EBS Grants Accounting (GMS) module that consolidates expenditure, award, and burden (indirect cost) information into a single denormalized result set. It is primarily used to support proposal and award financial reporting, cost reconciliation, and burdenable cost analysis across sponsored projects. The view joins award master data, project and task structures, expenditure items, cost distribution lines, and indirect cost compilation logic to produce a complete picture of raw cost, burdenable cost, and calculated burden (indirect) cost for each expenditure transaction.

Because indirect costing in Grants Accounting requires alignment between expenditure types, cost bases, compiled multiplier sets, and indirect rate schedule revisions, this view encapsulates that complex relationship. It exposes both the raw amount distributed to a project and the burdenable portion of that amount, as well as the compiled multiplier and the resulting burden cost amount. As documented, the view is not implemented in the reference database, meaning it is provided for reporting definition but may not exist in every environment.

Underlying Base Objects

The view is defined over a substantial set of base tables, spanning Grants and Projects schemas:

The joins constrain results to active award distributions (ADL_STATUS = 'A') and indirect cost bases, ensuring only valid burden calculations are reflected.

Key Columns

Common Use Cases and Queries

The view supports burdenable cost analysis, indirect cost reconciliation, and award expenditure reporting. A typical query retrieves burdenable cost and burden cost by award:

  • SELECT award_number, project_number, task_number, expenditure_type, raw_cost, burdenable_cost, idc_multiplier, burden_cost FROM gms_rxi_exp_details_v WHERE award_number = :p_award;
  • Comparing RAW_COST against BURDENABLE_COST to identify unallowable or non-burdenable portions.
  • Aggregating BURDEN_COST by EXPENDITURE_ORG or EXPENDITURE_TYPE for indirect cost reporting.
  • Filtering on STATUS_FLAG = 'Y' to restrict results to open awards.

Because the view is not implemented in the documented database, DBAs should verify its existence before referencing it in custom reports or integrations.