Results for “period_beginning_date”

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

Overview

The APPS.IGW_PRPO_ROLES_DETAILS_V view is a reporting object within the Oracle E-Business Suite Grants Proposal (IGW) module. It is defined in the APPS schema with a VALID status in both 12.1.1 and 12.2.2 releases. Its stated purpose is to display summary information about personnel included in budget lines, aggregating personnel data by proposal role and budget category so that grant administrators, principal investigators, and reporting users can quickly review salary and effort commitments associated with a proposal's budget.

Rather than exposing raw transactional detail, the view consolidates the personnel records of an approved, final-version proposal budget. It computes counts of persons, sums base salary and requested salary, and derives person-months from appointment type and percent effort. This makes it a convenience layer for Grants Proposal reporting, typically consumed through concurrent report programs, Oracle Discoverer/BI Publisher worksheets, or custom SQL used to populate grant submission and effort certification reports.

Underlying Base Objects

The view is built from the following documented sources:

• IGW_BUDGETS (PB) — provides the proposal/version header, restricted to FINAL_VERSION_FLAG = 'Y'.
• IGW_BUDGET_CATEGORY_V (IBC) — budget category and budget period identifiers mapped to line items.
• IGW_BUDGET_PERSONNEL_DETAILS (PBPD) — per-line personnel detail, including start/end dates, percent effort, and salary requested.
• IGW_BUDGET_PERSONS (PBP) — personnel appointment types, calculation base, and party identification.
• PER_PEOPLE_X (PPX) and IGW_PROP_PERSONS (PPP) — person party and proposal role assignment sources.

The joins link proposal and version identifiers consistently across the budget, category, personnel detail, persons, and proposal-persons tables, so only personnel tied to the final budget version of a proposal are returned. Because the object is a view, no independent storage exists; all data is derived at query time from the underlying IGW and PER tables.

Key Columns

• NO_OF_PERSONS — count of personnel records within the aggregated grouping.
• PROPOSAL_ROLE_CODE / PROPOSAL_ROLE — the coded role and its descriptive form; role code 'AM' is decoded to 'PRINCIPAL INVESTIGATOR', and other codes are resolved through IGW_REPORT_PROCESSING.GET_PROPOSAL_ROLE.
• BASE_SALARY — sum of the calculation base across qualifying personnel records.
• BUDGET_CATEGORY_CODE — the budget category to which the aggregated personnel costs belong.
• PERIOD_BEGINNING_DATE / PERIOD_END_DATE — the start and end of the budget period for the personnel detail.
• PERSON_MONTHS — derived as the sum of appointment type code multiplied by percent effort divided by 100.
• SALARY_REQUESTED — sum of salary requested for the grouped personnel detail.
• PROPOSAL_ID / BUDGET_PERIOD_ID — identifiers linking the result back to the proposal and its budget period.

Common Use Cases and Queries

Typical uses include personnel cost summaries for grant proposals, effort distribution review, and role-based salary reporting. A basic query filtering for one proposal returns roles and aggregated salary:

• SELECT proposal_role, no_of_persons, base_salary, salary_requested, person_months FROM apps.igw_prpo_roles_details_v WHERE proposal_id = :p_proposal_id ORDER BY proposal_role;
• Grouping by budget period for multi-year proposals: SELECT budget_period_id, budget_category_code, SUM(salary_requested) FROM apps.igw_prpo_roles_details_v WHERE proposal_id = :p_proposal_id GROUP BY budget_period_id, budget_category_code;
• Identifying principal investigator commitments: SELECT * FROM apps.igw_prpo_roles_details_v WHERE proposal_role_code = 'AM';

Because the view is read-only and pre-aggregated, it is safe for concurrent reporting and requires no write privileges. Queries should always be schema-qualified with APPS and bound by PROPOSAL_ID to avoid full scans of the underlying IGW tables.