Search Results igw_budget_personnel_details




Overview
Explore in AI Chat

Overview

The IGW_BUDGET_PERSONNEL_DETAILS table is a core data object within the Oracle E-Business Suite (EBS) Grants Proposal (IGW) module. It functions as a detailed transactional table that stores granular information for personnel costs attached to specific budget lines in a grant proposal. Its primary role is to capture the financial and appointment details for individuals (e.g., Principal Investigators, research staff) whose salaries, wages, or benefits are being requested as part of a proposal's budget. This table is essential for building, tracking, and reporting on the personnel expenditure components of a research grant throughout the proposal lifecycle in EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to link personnel data to budget lines and to support detailed calculations. Its primary key is BUDGET_PERSONNEL_DETAIL_ID, which uniquely identifies each personnel detail record. The most critical foreign key columns establish its relationships: LINE_ITEM_ID links the detail to a specific budget line item in the IGW_BUDGET_DETAILS table, while the composite foreign key (PROPOSAL_ID, VERSION_ID, PERSON_ID, APPOINTMENT_TYPE_CODE) links it to the master personnel record defined in the IGW_BUDGET_PERSONS table. Other significant columns typically include fields for calculated or entered amounts (e.g., salary request, fringe benefits, cost sharing), percentage of effort, and period of performance details, enabling precise costing for each individual's contribution to the project.

Common Use Cases and Queries

This table is central to personnel budget analysis and reporting. Common use cases include generating detailed budget justification reports that break down salary requests by individual, calculating total personnel costs for a specific budget version, and auditing effort commitments. A typical query might join this table to IGW_BUDGET_PERSONS and IGW_BUDGET_DETAILS to produce a summary report.

  • Sample Query Pattern: Selecting personnel details for a specific proposal budget to calculate total salary requests.
SELECT bpd.person_id, bp.full_name, bpd.appointment_type_code,
       SUM(bpd.salary_request) total_salary
FROM igw_budget_personnel_details bpd,
     igw_budget_persons bp
WHERE bpd.proposal_id = :p_proposal_id
  AND bpd.version_id = :p_version_id
  AND bpd.proposal_id = bp.proposal_id
  AND bpd.person_id = bp.person_id
GROUP BY bpd.person_id, bp.full_name, bpd.appointment_type_code;

Related Objects

IGW_BUDGET_PERSONNEL_DETAILS is a child table within a well-defined hierarchy in the Grants Proposal schema. Its most direct relationships, as documented in the ETRM, are:

  • IGW_BUDGET_DETAILS: The parent table for budget line items. The foreign key on LINE_ITEM_ID enforces that every personnel detail must belong to a valid budget line.
  • IGW_BUDGET_PERSONS: The master table for persons associated with a proposal. The composite foreign key ensures personnel details reference a valid, defined individual and appointment type.
  • IGW_BUDGET_PERSONNEL_CAL_AMTS: A likely child table that stores calculated or breakdown amounts (e.g., by period) for a given personnel detail, linked via BUDGET_PERSONNEL_DETAIL_ID.