Search Results gms_burden_components




Overview
Explore in AI Chat

Overview

GMS_BURDEN_COMPONENTS is a transactional table in the GMS (Grants Accounting) product schema of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. The table stores the individual burden components that are generated when billing events are processed against awarded projects. Each row represents one burden cost line associated with an expenditure item, capturing the burden cost code applied, the burden expense type, and the calculated burden amount that will be passed to billing and revenue recognition. Because burden represents indirect cost recovery — the overhead, fringe, and administrative rates applied on top of direct costs — this table is central to the indirect cost calculations that flow through sponsored project billing.

From a dimensional modeling perspective, the mined foreign-key structure classifies GMS_BURDEN_COMPONENTS as satellite-leaning. This heuristic suggests the table functions primarily as an extension of a core transactional entity, attached through its foreign key to PA_EXPENDITURE_ITEMS_ALL, rather than acting as an independent hub or as a resolving link between multiple business entities. The burden detail is therefore best modeled as dependent attributes hanging off the expenditure item grain.

Key Information Stored

The table contains 19 documented columns. The most operationally significant include:

The documented unique index, GMS_BURDEN_COMPONENTS_U1, spans AWARD_PROJECT_ID, BURDEN_COST_CODE, EVENT_TYPE, EXPENDITURE_ITEM_ID, ADL_LINE_NUM, and REQUEST_ID. No dedicated surrogate primary key column is documented; the unique index acts as the business-key candidate and enforces uniqueness at the component level. The true grain is the combination of expenditure item, burden cost code, event type, award distribution line, and request.

Common Use Cases and Queries

Typical usage centers on auditing and reconciling burden calculations for sponsored projects, validating indirect cost recovery during billing, and investigating discrepancies between direct and burdened amounts on an award.

A common query joins burden components back to expenditure items to reconstruct the full direct-plus-indirect cost picture for an award:

  • Reconcile burden amounts by award: SELECT b.award_project_id, b.burden_cost_code, b.burden_exp_type, SUM(b.amount) FROM gms_burden_components b WHERE b.award_project_id = :award GROUP BY b.award_project_id, b.burden_cost_code, b.burden_exp_type;
  • Trace a burden line to its direct cost: SELECT e.expenditure_item_id, e.expenditure_type, b.burden_cost_code, b.amount FROM pa_expenditure_items_all e JOIN gms_burden_components b ON b.expenditure_item_id = e.expenditure_item_id WHERE e.project_id = :project;
  • Investigate a billing event: filter by EVENT_NUM and EVENT_TYPE to list all burden components generated for that event.
  • Audit concurrent processing: group by REQUEST_ID to identify rows created by a specific burden generation run.

These patterns support grants accounting reporting, indirect cost rate validation, and reconciliation of billing event extracts.

Related Objects

The most significant related object is the foreign-key parent, PA_EXPENDITURE_ITEMS_ALL, joined on EXPENDITURE_ITEM_ID; this is the direct cost detail from which burden components derive. Award and project context is provided through AWARD_PROJECT_ID (GMS_AWARDS / PA_PROJECTS), ACTUAL_PROJECT_ID and ACTUAL_TASK_ID (PA_PROJECTS_ALL, PA_TASKS), and EXPENDITURE_ORG_ID (HR_ALL_ORGANIZATION_UNITS). Billing event processing links to the GMS billing event tables that consume these burden rows. The BURDEN_COST_CODE and BURDEN_EXP_TYPE reference the burden setup tables (burden cost codes and expenditure types). Finally, RESOURCE_LIST_MEMBER_ID links to the resource list setup used for rate derivation, and REQUEST_ID relates to FND_CONCURRENT_REQUESTS for the generating process.