Search Results per_details

Overview

The view APPS.IGWFV_GRNT_PRPSL_BDGT_PERS_AMT is a read-only reporting construct within the Oracle E-Business Suite Grants Management (formerly Oracle Grants Accounting / Oracle ETRM) module. The "FV" infix identifies it as a foreign or formatted view intended for inquiry and reporting rather than transactional processing. It presents personnel budget amounts calculated for grant proposals, joining calculated amount records to their governing personnel detail, proposal header, and rate definitions. In releases 12.1.1 and 12.2.2 the view remains a denormalized, query-friendly window into the proposal personnel budgeting subsystem.

The view is defined WITH READ ONLY, meaning it exposes no DML path; consumers use it strictly for SELECT-based extraction and downstream reporting or integration. It is commonly surfaced through Oracle Grants Management proposal and budget inquiry screens, and is a natural source for custom reports, Discoverer workbooks, and outbound interfaces that require calculated personnel cost and cost-sharing figures.

Underlying Base Objects

The view is defined over six base tables joined on their respective surrogate keys:

• IGW_BUDGET_PERSONNEL_CAL_AMTS (CAL_AMTS) — the driving table, holding calculated cost, cost-sharing, and the rate-application flag for each personnel budget line.
• IGW_BUDGET_PERSONNEL_DETAILS (PER_DETAILS) — personnel detail rows linked via BUDGET_PERSONNEL_DETAIL_ID, supplying VERSION_ID, BUDGET_PERIOD_ID, LINE_ITEM_ID, PERSON_ID, and PROPOSAL_ID.
• IGW_PROPOSALS_ALL (PR) — the proposal header, joined on PROPOSAL_ID, supplying PROPOSAL_NUMBER.
• PER_ALL_PEOPLE_F (PAPF) — the HR person record, joined on PERSON_ID, supplying FULL_NAME.
• IGW_RATE_CLASSES (CLASS) — joined on RATE_CLASS_ID, supplying the rate-class DESCRIPTION.
• IGW_RATE_TYPES (TYPE) — joined on RATE_TYPE_ID, supplying the rate-type DESCRIPTION.

No base objects beyond these are documented in the ETRM metadata. The joins are equijoins on primary keys, and the read-only clause prevents any modification through the view.

Key Columns

• PROPOSAL_NUMBER / PROPOSAL_ID — identifies the parent grant proposal.
• VERSION_ID — the proposal version against which the amount is calculated.
• FULL_NAME / PERSON_ID — the person whose personnel budget amount is being reported.
• BUDGET_PERIOD_ID / LINE_ITEM_ID — the budget period and line item context.
• BUDGET_PERSONNEL_DETAIL_ID — the personnel detail key linking calculation to person.
• DESCRIPTION (from CLASS and TYPE) — rate-class and rate-type descriptions.
• RATE_CLASS_ID / RATE_TYPE_ID — rate classification keys.
• APPLY_RATE_FLAG — indicates whether the rate was applied to the calculation.
• CALCULATED_COST — the computed personnel cost.
• CALCULATED_COST_SHARING — the computed cost-sharing amount.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.

Common Use Cases and Queries

Typical scenarios include personnel budget reporting, cost-share analysis, and rate application audits.

• Listing all calculated personnel amounts for a proposal:

SELECT proposal_number, full_name, budget_period_id,
       calculated_cost, calculated_cost_sharing
FROM   apps.igwfv_grnt_prpsl_bdgt_pers_amt
WHERE  proposal_number = :p_proposal_number;

• Auditing rate application across personnel lines:

SELECT proposal_number, full_name, description,
       apply_rate_flag, calculated_cost
FROM   apps.igwfv_grnt_prpsl_bdgt_pers_amt
WHERE  apply_rate_flag = 'Y';

• Aggregating cost and cost-sharing by proposal for integration:

SELECT proposal_id, SUM(calculated_cost) cost,
       SUM(calculated_cost_sharing) cost_share
FROM   apps.igwfv_grnt_prpsl_bdgt_pers_amt
GROUP  BY proposal_id;

Because the view is read-only, it is safe for concurrent reporting and extraction workloads without risk of altering underlying grant proposal budgeting data.