Results for “indirect_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGW.IGW_AWARD_BUDGETS is a base table in the Oracle E-Business Suite Grants Proposal (IGW) module that stores budget information associated with awards and their underlying proposals. Within the ETRM documentation for Oracle EBS 12.1.1 and 12.2.2, it is described simply as holding "information about award budgets," functioning as the transactional store for budgeted amounts, expenditure classifications, and period-level distribution. The table is owned by the IGW schema and is marked VALID.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling context, meaning it carries its own surrogate key and does not appear, on the documented evidence, to be absorbed into a dependent child table. A Data Vault design would typically suggest treating such a table as a satellite anchored to an award or proposal hub, with its foreign key to IGW_INSTALLMENTS represented as a link. This is a modeling suggestion only, derived from the documented FK structure.

Key Information Stored

The table contains 19 documented physical columns. The most significant are:

• AWARD_BUDGET_ID — the surrogate primary key, enforced by IGW_AWARD_BUDGETS_PK. It is also exposed as a unique business-key candidate through IGW_AWARD_BUDGETS_U1.
• PROPOSAL_INSTALLMENT_ID — the foreign key pointing to IGW_INSTALLMENTS, tying the budget record to a specific installment or scheduled funding event.
• BUDGET_PERIOD_ID — identifies the budget period the amount applies to.
• BUDGET_AMOUNT — the budgeted monetary value for the record.
• EXPENDITURE_TYPE_CAT and EXPENDITURE_CATEGORY_FLAG — classify the expenditure type and its category, driving reporting and indirect cost treatment.
• INDIRECT_FLAG — indicates whether the amount is an indirect (facilities and administrative) cost component.
• PROJECT_ID and TASK_ID — link the budget line to a project and task in Oracle Projects.
• PERIOD_NAME, START_DATE, END_DATE — define the accounting period and effective date range of the budget.
• TRANSFERRED_FLAG — records whether the budget has been transferred to the project/award side.
• RECORD_VERSION_NUMBER — supports optimistic locking and concurrency control.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

The surrogate key AWARD_BUDGET_ID should be distinguished from any natural business identifier; the metadata documents no separate business key beyond the unique index on this column.

Common Use Cases and Queries

Typical reporting scenarios include listing budgets by award, aggregating direct versus indirect amounts per project, and reconciling proposal budgets against transferred award budgets.

Budget totals per proposal installment:

SELECT proposal_installment_id, SUM(budget_amount)
FROM   igw_award_budgets
GROUP  BY proposal_installment_id;

Indirect cost analysis:

SELECT project_id, task_id, period_name, budget_amount
FROM   igw_award_budgets
WHERE  indirect_flag = 'Y'
AND    transferred_flag = 'Y';

Joining to installments to view scheduled funding:

SELECT b.award_budget_id, b.budget_amount, i.*
FROM   igw_award_budgets b,
       igw_installments   i
WHERE  b.proposal_installment_id = i.installment_id;

Related Objects

• IGW_INSTALLMENTS — referenced via IGW_AWARD_BUDGETS.PROPOSAL_INSTALLMENT_ID = IGW_INSTALLMENTS.INSTALLMENT_ID; the principal documented parent relationship.
• IGW_AWARD_BUDGETS_PK / IGW_AWARD_BUDGETS_U1 — the primary key constraint and unique index on AWARD_BUDGET_ID.
• Oracle Projects (PA) tables — PROJECT_ID and TASK_ID typically resolve to PA_PROJECTS_ALL and PA_TASKS.
• IGW award and proposal tables — award headers and proposal definitions that own the budget records contextually.
• AP/GL period tables — PERIOD_NAME aligns with GL accounting periods for reporting reconciliation.