Search Results percent_charged




Overview

IGW_BUDGET_PERSONNEL_V is an Oracle E-Business Suite view owned by the APPS schema and defined in the Grants Management (IGW) module, which is part of the Oracle ETRM/OCM application family. The view presents budget personnel detail information captured against proposals, versions, budget periods, and line items. In practice it functions as a thin projection over a single underlying base table rather than as a join-based consolidation, exposing the personnel-level budgeting attributes that Oracle Grants Management uses to record how labor effort and salary are allocated across a proposal's budget structure. For reporting and integration purposes, it provides a stable, read-only interface through which budget personnel rows can be queried without requiring direct access to the base table, and it is frequently referenced by concurrent programs, BI Publisher reports, and custom extracts that need proposal budget labor data at the person level. Because the view does not restrict rows and applies no WHERE clause, all personnel detail records are visible, including current and historical version data distinguished by VERSION_ID.

Underlying Base Objects

The view is defined over a single base object: IGW_BUDGET_PERSONNEL_DETAILS. No additional joins, aggregations, or derived expressions are present in the view text; every column exposed is a direct passthrough of the corresponding base table column, and the only transformation applied is column selection and the renaming of the base table to the view's name in the FROM clause. This one-to-one relationship means the view's cardinality, key structure, and row-level semantics are identical to those of IGW_BUDGET_PERSONNEL_DETAILS. The primary key of the base table is BUDGET_PERSONNEL_DETAIL_ID, and the view inherits that uniqueness. Foreign key relationships maintained on the base table — to proposal, version, budget period, line item, and person entities — carry through implicitly, allowing the view to be joined to IGW_PROPOSALS, IGW_PROPOSAL_VERSIONS, IGW_BUDGET_PERIODS, and per-person HR or FND objects in reporting queries.

Key Columns

Common Use Cases and Queries

Typical usage centers on proposal budget labor reporting: identifying effort allocations, cost sharing, and salary by person or period. A representative query retrieving effort for a proposal is:

SELECT person_id, budget_period_id, start_date, end_date,
       percent_effort, percent_charged, salary_requested
FROM   apps.igw_budget_personnel_v
WHERE  proposal_id = :p_proposal_id
AND    version_id  = :p_version_id
ORDER BY person_id, start_date;

Because the view maps directly to IGW_BUDGET_PERSONNEL_DETAILS, any predicate valid on the base table is valid here, and no join overhead is introduced. Analysts commonly aggregate percent_effort to validate total committed effort per period, or join to person and proposal tables for descriptive reporting.