Search Results proposal_role_code




Overview
Explore in AI Chat

Overview

IGW_PRPO_PERSON_DETAILS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Grants Proposal (IGW) module. Its purpose, as documented in the ETRM metadata, is to display details about personnel who are included in budget lines for a proposal. The view consolidates person identity data, proposal role assignment, budget category classification, budget period information, and effort/compensation attributes into a single queryable structure.

The view is primarily intended to support reporting and extraction of personnel-level budget detail — commonly used by grants administrators, principal investigators, and reporting tools that need a flattened representation of who is funded, in what role, on which budget lines, and at what level of effort. Because "appointment_type" was the term the user searched on, the most relevant column is APPOINTMENT_TYPE, which is derived directly from IGW_BUDGET_PERSONS.APPOINTMENT_TYPE_CODE. In the Grants Proposal model, appointment type codes are numeric and are used to convert percent effort into person-months (for example, a 9-month academic appointment versus a 12-month calendar appointment versus a summer appointment), so this column is central to any effort or salary calculation.

Underlying Base Objects

The view is defined over several IGW and HRMS base objects. Per the documented view text, the following objects are referenced:

  • IGW_BUDGETS (PB) — the proposal budget header, filtered by FINAL_VERSION_FLAG = 'Y'.
  • IGW_BUDGET_CATEGORY_V (IBC) — budget category and category code for the proposal.
  • IGW_BUDGET_PERSONNEL_DETAILS (PBPD) — period type, effort, salary requested, and line item detail.
  • IGW_BUDGET_PERSONS (PBP) — person-level budget data including APPOINTMENT_TYPE_CODE, calculation base (base salary), person and party identifiers.
  • PER_PEOPLE_X (PPX) — person name attributes (last, first, middle names).
  • IGW_PROP_PERSONS (PPP) — proposal role assignment.

The joins link proposal, version, line item, person, and appointment type code across these tables. A UNION combines two similar query blocks so that multiple budget periods and person sequences are reported together.

Key Columns

Common Use Cases and Queries

Typical uses include extracting personnel line items for a proposal budget for a given final version, listing effort and person-months by appointment type, and producing reports that reconcile role, period type, and salary. A representative query:

SELECT proposal_id,
       line_item_id,
       first_name || ' ' || last_name  AS person_name,
       proposal_role,
       period_type,
       appointment_type,
       base_salary,
       percent_effort,
       person_months,
       salary_requested
FROM   apps.igw_prpo_person_details_v
WHERE  proposal_id = :p_proposal_id
ORDER  BY person_name, period_type;

To analyze effort distribution by appointment type:

SELECT appointment_type,
       COUNT(*)              AS person_lines,
       SUM(person_months)    AS total_person_months,
       SUM(salary_requested) AS total_salary
FROM   apps.igw_prpo_person_details_v
WHERE  proposal_id = :p_proposal_id
GROUP  BY appointment_type;

Because the view filters to final-version budgets through IGW_BUDGETS, queries automatically restrict to the authoritative budget without additional version filtering. The APPOINTMENT_TYPE and PERSON_MONTHS columns make the view especially useful for effort reporting and personnel-line extracts where appointment type must be surfaced explicitly.