Results for “igw_report_budget_seed”

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

Overview

The IGW.IGW_REPORT_BUDGET_SEED table is a reference and setup table within the Oracle E-Business Suite IGW – Grants Proposal module. It stores seed data that defines the sponsor budget hierarchy, providing the baseline mapping between proposal form numbers and the budget categories used when sponsors or institutions report proposal budgets. It functions as configuration data that supports budget reporting structures during proposal creation and submission in both EBS 12.1.1 and 12.2.2.

Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as standalone, with no foreign key dependencies to other tables. This suggests it behaves as an independent reference or lookup entity rather than a hub, link, or satellite within a dimensional or Data Vault model. Its design supports stable, reusable seed records that are not tightly coupled to other transactional tables through enforced referential constraints.

Key Information Stored

The table contains seven documented columns and is keyed by the composite primary key IGW_REPORT_BUDGET_SEED, defined over PROPOSAL_FORM_NUMBER, BUDGET_CATEGORY_CODE, PROPOSAL_BUDGET_CATEGORY, and PROPOSAL_BUDGET_CATEGORY_CODE. A unique index, IGW_REPORT_BUDGET_SEED_U1, covers the business-key candidate combination of PROPOSAL_FORM_NUMBER, PROPOSAL_BUDGET_CATEGORY, PROPOSAL_BUDGET_CATEGORY_CODE, and BUDGET_CATEGORY_CODE — reaffirming that these four attributes together uniquely identify a seed record.

• PROPOSAL_FORM_NUMBER – Identifies the proposal form or sponsor form context to which the seed budget hierarchy applies.
• BUDGET_CATEGORY_CODE – The internal EBS code for the budget category being seeded.
• PROPOSAL_BUDGET_CATEGORY – The descriptive proposal-level budget category name used in reporting.
• PROPOSAL_BUDGET_CATEGORY_CODE – The code associated with the proposal budget category, used in mappings and reporting logic.
• DETAILS_REQUIRED_FLAG – Indicates whether additional detail must be captured for the category.
• FRINGE_FLAG – Indicates whether the category is treated as a fringe benefit component.
• SEED_DATA_FLAG – Marks whether the row is seeded system data versus user-maintained data, supporting upgrade and patching behavior.

Common Use Cases and Queries

This table is typically queried to validate or report on the sponsor budget hierarchy configuration for a given proposal form. Common scenarios include verifying which categories are fringe-bearing, checking which require additional detail, and confirming which records are delivered as seed data versus created by users.

• Listing the budget hierarchy for a proposal form:

  SELECT proposal_form_number,
         proposal_budget_category,
         proposal_budget_category_code,
         budget_category_code,
         fringe_flag,
         details_required_flag
  FROM   igw.igw_report_budget_seed
  WHERE  proposal_form_number = :form_number
  ORDER BY proposal_budget_category;

• Identifying fringe categories:

  SELECT * FROM igw.igw_report_budget_seed
  WHERE  fringe_flag = 'Y';

• Separating seeded versus user-maintained records:

  SELECT seed_data_flag, COUNT(*)
  FROM   igw.igw_report_budget_seed
  GROUP BY seed_data_flag;

Reporting use cases include auditing sponsor form configuration prior to submission, validating budget category mappings during upgrades across 12.1.1 and 12.2.2, and supporting troubleshooting when a proposal budget does not display the expected hierarchy.

Related Objects

The metadata classifies this table as standalone, meaning no enforced foreign keys exist to related objects. The most significant dependencies are therefore logical rather than physical and typically involve:

• IGW_PROPOSAL_BUDGETS – aligns budget lines by PROPOSAL_FORM_NUMBER and BUDGET_CATEGORY_CODE.
• IGW_BUDGET_CATEGORIES – the master definition referenced by BUDGET_CATEGORY_CODE.
• IGW_PROPOSAL_FORMS – supplies PROPOSAL_FORM_NUMBER context.
• IGW_PROPOSALS – proposal header linking to form and budget data.
• IGW_SPONSOR_BUDGETS – sponsor-level budget configuration sharing category codes.
• The Grants Proposal budget entry and reporting APIs, which consume these seed mappings during proposal budget generation.