Search Results igw_budget_persons




Overview
Explore in AI Chat

Overview

The IGW_BUDGET_PERSONS table is a core data structure within the Oracle E-Business Suite (EBS) Grants Proposal module, designated as IGW. Its primary function is to store detailed budgeting information for personnel associated with grant proposals. This table acts as a junction, linking high-level budget data with specific personnel details to facilitate the calculation and management of salary and compensation costs within a proposal's financial plan. It is critical to note that the ETRM metadata explicitly classifies the IGW - Grants Proposal module as "Obsolete." Consequently, this table and its associated functionality are part of a legacy codebase that is no longer under active development, though it may persist in existing implementations for backward compatibility.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies each personnel budget record. The key columns are PROPOSAL_ID and VERSION_ID, linking to the parent budget, PARTY_ID (which likely identifies the individual), and APPOINTMENT_TYPE_CODE (defining the nature of their appointment, such as full-time or part-time). While the specific non-key columns are not detailed in the provided excerpt, the table's description indicates it holds "budgeting information about personnel." This typically encompasses data points such as budgeted salary rates, percentage of effort committed to the proposal, calculated salary costs, fringe benefit rates, and associated cost calculations for the specified appointment period. The table serves as the authoritative source for personnel-related cost allocations within a proposal budget version.

Common Use Cases and Queries

The primary use case involves generating detailed budget reports for grant proposals, specifically the personnel cost components. Administrators and principal investigators would query this table to review, audit, and summarize salary allocations. A common reporting pattern is to join this table with personnel master data and budget headers to produce a comprehensive view. For example, a query to list all budgeted personnel for a specific proposal version would follow this pattern:

  • SELECT bp.proposal_id, bp.version_id, bp.party_id, bp.appointment_type_code, pp.full_name, b.budget_total FROM igw_budget_persons bp JOIN igw_prop_persons pp ON bp.proposal_id = pp.proposal_id AND bp.person_id = pp.person_id JOIN igw_budgets b ON bp.proposal_id = b.proposal_id AND bp.version_id = b.version_id WHERE bp.proposal_id = :p_prop_id AND bp.version_id = :p_ver_id;

Given the module's obsolete status, direct operational use in new customizations is discouraged. Queries are typically executed for historical data analysis, data migration to successor systems, or supporting legacy reporting requirements.

Related Objects

The IGW_BUDGET_PERSONS table is centrally connected within the Grants Proposal schema, as evidenced by its foreign key relationships. It is a child of the IGW_BUDGETS table, ensuring every personnel budget record is tied to a valid parent budget version via PROPOSAL_ID and VERSION_ID. It also references the IGW_PROP_PERSONS table through PROPOSAL_ID and PERSON_ID, validating the budgeted individual against the list of personnel associated with the proposal. Furthermore, it serves as a parent table to IGW_BUDGET_PERSONNEL_DETAILS, which likely holds more granular, period-specific cost breakdowns (e.g., monthly or quarterly figures) for each personnel budget line. The join for this relationship uses all four primary key columns: PROPOSAL_ID, VERSION_ID, PERSON_ID, and APPOINTMENT_TYPE_CODE.