Search Results gms_burden_components_u1

Overview

GMS.GMS_BURDEN_COMPONENTS is a transactional table in the Oracle E-Business Suite Grants Management (GMS) schema. It stores the burden amounts, broken out by burden component, for each raw expenditure item that is picked up during the revenue generation or billing process. In practical terms, whenever award-related expenditures flow through burdening, this table records the indirect cost applied to each underlying transaction, attributed to a specific burden cost code and event type.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE of 10, indicating a design oriented toward frequent inserts and moderate update activity typical of transactional staging. Its documented status is VALID, and it carries FND Design Data registration under GMS.GMS_BURDEN_COMPONENTS.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as satellite-leaning. This is a heuristic suggestion rather than a documented designation. The classification is supported by the presence of a composite unique key and a foreign key to PA_EXPENDITURE_ITEMS_ALL via EXPENDITURE_ITEM_ID, which positions the table as descriptive context hanging off the raw expenditure item hub rather than a standalone entity in its own right. The heavy dependency on surrogate identifiers (EXPENDITURE_ITEM_ID, AWARD_PROJECT_ID, REQUEST_ID) reinforces the satellite interpretation.

Key Information Stored

The table documents 19 physical columns. The most significant include:

• EXPENDITURE_ITEM_ID — unique identifier of the expenditure item processed for billing or revenue. This is the primary link back to PA_EXPENDITURE_ITEMS_ALL and forms the historical anchor for each burden row.
• AWARD_PROJECT_ID — unique identifier of the award project. Together with the other key columns, this scopes burden amounts to a specific award.
• BURDEN_COST_CODE — the burden or indirect cost code applied. This determines which indirect pool or component the amount belongs to.
• BURDEN_EXP_TYPE — the expenditure type mapped to the burden cost code, providing a descriptive cross-reference to expenditure classification.
• EVENT_TYPE — indicates whether the row relates to a revenue generation event ("Revenue") or a billing event ("Invoice"). This is central to distinguishing revenue versus invoice processing usage.
• EVENT_NUM — unique identifier of the expenditure item processed for billing or revenue, aligning the burden row to the event header.
• AMOUNT — the burden amount itself. This is the primary measure.
• ACTUAL_PROJECT_ID and ACTUAL_TASK_ID — identify the project and task against which the raw transaction was originally recorded, which may differ from the award project context.
• REVENUE_ACCUMULATED — supports accumulated revenue calculations and appears in multiple non-unique indexes, indicating frequent filtering.
• ADL_LINE_NUM, RESOURCE_LIST_MEMBER_ID, EXPENDITURE_ORG_ID, REQUEST_ID — supporting attribution and concurrency columns, with REQUEST_ID participating directly in the unique key.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who audit columns.

The business-key candidate is the unique index GMS_BURDEN_COMPONENTS_U1, defined on (AWARD_PROJECT_ID, BURDEN_COST_CODE, EVENT_TYPE, EXPENDITURE_ITEM_ID, ADL_LINE_NUM, REQUEST_ID). There is no single-column surrogate primary key documented; the natural uniqueness is composite, which is characteristic of satellite-style tables keyed on the parent hub plus qualifiers. The non-unique indexes (_N1 through _N10) support query access paths on EXPENDITURE_ITEM_ID, EVENT_TYPE, BURDEN_COST_CODE, AWARD_PROJECT_ID, REQUEST_ID, EVENT_NUM, and REVENUE_ACCUMULATED.

Common Use Cases and Queries

Typical usage centers on burden reconciliation, indirect cost reporting, and audit tracing of revenue versus invoice events. A common pattern joins burden components back to the raw expenditure item and to the award project:

• Burden amount by award and cost code — aggregate AMOUNT grouped by AWARD_PROJECT_ID and BURDEN_COST_CODE, filtered by EVENT_TYPE to separate revenue from invoice scenarios.
• Expenditure drill-down — join EXPENDITURE_ITEM_ID to PA_EXPENDITURE_ITEMS_ALL to retrieve the source transaction context for each burden row, using index GMS_BURDEN_COMPONENTS_N1.
• Event reconciliation — use EVENT_NUM and EVENT_TYPE to match burden components to the triggering billing or revenue event, checking that AMOUNT totals agree.
• Revenue accumulation review — filter on REVENUE_ACCUMULATED (supported by _N4 and _N10) to audit accumulated revenue treatment.

Because the unique key includes REQUEST_ID, concurrent processing runs can be isolated cleanly, and this column is a practical filter for tracing a specific burdening request.

Related Objects

• PA_EXPENDITURE_ITEMS_ALL — referenced via EXPENDITURE_ITEM_ID; the parent raw transaction table and the primary join target.
• GMS award and project tables — referenced through AWARD_PROJECT_ID to resolve the award context of each burden row.
• PA project and task tables — referenced through ACTUAL_PROJECT_ID and ACTUAL_TASK_ID for original transaction attribution.
• GMS burden and event processing programs — the concurrent processes that populate REQUEST_ID rows during revenue and billing runs.
• GMS_BURDEN_COMPONENTS_U1 — the composite unique index enforcing business-key uniqueness.
• Non-unique indexes _N1 through _N10 — supporting access paths for reporting and reconciliation queries.

Together these objects position GMS_BURDEN_COMPONENTS as the descriptive burden detail layer sitting downstream of raw project expenditures and upstream of GMS billing and revenue reporting.