Results for “cost_sharing_amount”

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

Overview

IGW_BUDGET_PERIODS is a table in the IGW (Grants Proposal) product module of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. It stores information on budget periods for a budget version within a proposal. In the grants management lifecycle, a proposal's budget is normally divided into distinct time-bound periods — typically annual or fiscal-year segments — each carrying its own cost, indirect cost, cost-sharing, and income figures. IGW_BUDGET_PERIODS is the parent record for those period-level amounts, serving as the reference point against which budget line details and calendar-based distribution amounts are organized.

The documented primary key, IGW_BUDGET_PERIODS_PK, is a composite of PROPOSAL_ID, VERSION_ID, and BUDGET_PERIOD_ID. The same three columns form the documented unique index IGW_BUDGET_PERIODS_U1, so the table's business key and its unique index are identical. Applying a heuristic Data Vault classification mined from the foreign-key structure, this table is hub-leaning rather than a transaction or link entity: it defines the identity of a budget period, while the tables beneath it carry the transactional detail. The table is owned by the IGW schema and comprises 19 documented columns, including standard Oracle WHO audit columns and a RECORD_VERSION_NUMBER for optimistic concurrency control.

Key Information Stored

The following columns represent the most significant attributes documented for this table:

• PROPOSAL_ID, VERSION_ID, BUDGET_PERIOD_ID — the composite primary key and business key. PROPOSAL_ID and VERSION_ID identify which budget version the period belongs to; BUDGET_PERIOD_ID uniquely identifies the period within that version.
• START_DATE, END_DATE — the effective date range of the budget period, defining the time window over which period-level costs are accumulated.
• TOTAL_COST — the total cost for the budget period, including direct and indirect components.
• TOTAL_DIRECT_COST and TOTAL_INDIRECT_COST — the decomposed direct and indirect (facilities and administrative) cost portions of the period budget.
• COST_SHARING_AMOUNT — the amount contributed by the institution or other parties as cost sharing for the period.
• UNDERRECOVERY_AMOUNT — the portion of indirect cost not recovered, recorded at period level.
• TOTAL_COST_LIMIT — the ceiling imposed on total costs for the period, used in validation and budget-checking logic.
• PROGRAM_INCOME and PROGRAM_INCOME_SOURCE — program income earned during the period and an indicator of its source.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, RECORD_VERSION_NUMBER — standard audit and concurrency columns maintained for all IGW transactional data.

Note that these 19 columns are physical attributes only; the table itself is a structural parent, and the period-level cost detail that drives its totals resides in the child tables described below.

Common Use Cases and Queries

The table is principally used for budget period reporting, period roll-forward and comparison, and cost-limit enforcement in the Grants Proposal module. Typical queries join to IGW_BUDGETS to confirm version context and to IGW_BUDGET_DETAILS to reconcile period totals against line items.

A representative query to list all periods for a given proposal version:

• SELECT budget_period_id, start_date, end_date, total_cost, total_direct_cost, total_indirect_cost FROM igw_budget_periods WHERE proposal_id = :p_proposal AND version_id = :p_version ORDER BY start_date;

A reconciliation pattern comparing period totals to aggregated detail:

• SELECT p.budget_period_id, p.total_cost, SUM(d.amount) detail_cost FROM igw_budget_periods p, igw_budget_details d WHERE p.proposal_id = d.proposal_id AND p.version_id = d.version_id AND p.budget_period_id = d.budget_period_id AND p.proposal_id = :p_proposal GROUP BY p.budget_period_id, p.total_cost;

Where period amounts are distributed across a calendar, IGW_BUDGET_DETAILS_CAL_AMTS is the correct join target instead of IGW_BUDGET_DETAILS. Cost-sharing and underrecovery reporting also draw directly from this table, since those figures are stored at period level rather than derived from line detail.

Related Objects

The documented foreign-key relationships establish the following dependencies:

• IGW_BUDGETS — the parent table. IGW_BUDGET_PERIODS.PROPOSAL_ID and VERSION_ID reference the budget version record.
• IGW_BUDGET_DETAILS — child detail table. It joins back on PROPOSAL_ID, VERSION_ID, and BUDGET_PERIOD_ID and holds the individual budget lines belonging to each period.
• IGW_BUDGET_DETAILS_CAL_AMTS — child table holding calendar-distributed detail amounts, joined on the same three columns, used for time-phased reporting.
• IGW_REPORT_BUDGET_BASE_RATE — reporting table referencing budget period identifiers, joined on PROPOSAL_ID, VERSION_ID, and BUDGET_PERIOD_ID.

Together these objects form the budget period hierarchy within the Grants Proposal module, with IGW_BUDGET_PERIODS acting as the structural hub between the budget version header and its period-level detail.