Results for “calculation_base”

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

Overview

IGWBV_GRANT_PRPSL_BDGT_PERSON is a read-only view owned by the APPS schema within the Oracle E-Business Suite Grants Proposal (IGW) module. It exposes personnel-related budget line data associated with grant proposals, joining proposal header information to budget person assignments so that report writers, concurrent programs, and integration extracts can retrieve personnel budgeting records without navigating the underlying normalized table relationships individually.

The view is defined with the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting purposes. No DML operations can be issued against it, which aligns with its role as an ETRM-reported view used to feed Oracle Business Intelligence, Grants accounting reports, and custom extracts within the Grants Proposal workflow. The view is registered as VALID in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2 environments that include the IGW product.

Underlying Base Objects

The view is defined over two documented base objects:

• IGW_BUDGET_PERSONS (aliased BUD_PERS) — the primary transactional table holding budget person assignments, including version, effective dating, and calculation basis information.
• IGW_PROPOSALS_ALL (aliased PR) — the proposals master table, supplying the proposal number and proposal identifier used to associate personnel budget records with their parent proposal.

The join condition is PR.PROPOSAL_ID = BUD_PERS.PROPOSAL_ID, establishing a one-to-many relationship in which each proposal can carry multiple budget person rows. Documented ETRM metadata lists no other referenced base objects, so the view remains a straightforward two-table join with no aggregations, groupings, or function-based derivations beyond a lookup descriptor column.

Key Columns

The view projects the following columns:

• PROPOSAL_NUMBER — the human-readable proposal identifier from IGW_PROPOSALS_ALL.
• PROPOSAL_ID — the internal surrogate key of the proposal, useful for joins back to other IGW proposal views.
• VERSION_ID / BUDGET_VERSION_ID — identifies the budget version to which the personnel assignment belongs.
• PERSON_ID — the party identifier for the person whose effort is budgeted against the proposal.
• EFFECTIVE_DATE — the date the personnel budget row becomes effective.
• CALCULATION_BASE — indicates the basis on which the person's budget contribution is calculated.
• "_LA:BUD_PERS.APPOINTMENT_TYPE_CODE:IGW_LOOKUPS_V:IGW_APPOINTMENT_TYPE:MEANING" — a descriptive flexfield-style lookup column that resolves the appointment type code against the IGW_APPOINTMENT_TYPE lookup to return the display meaning.
• AUDIT COLUMNS — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY, carrying the standard Oracle who-column lineage.

Common Use Cases and Queries

The view supports budget personnel reporting for grant proposals, including appointment type breakdowns, effective-dated personnel rosters, and audit reconciliation.

Sample query listing budgeted personnel for a proposal:

• SELECT proposal_number, person_id, effective_date, calculation_base
• FROM apps.igwbv_grant_prpsl_bdgt_person
• WHERE proposal_number = :p_proposal_number;

Sample query aggregating effort by appointment type using the lookup descriptor column:

• SELECT proposal_number, "_LA:APPOINTMENT_TYPE", COUNT(person_id) headcount
• FROM apps.igwbv_grant_prpsl_bdgt_person
• GROUP BY proposal_number, "_LA:APPOINTMENT_TYPE";

Because the view is read-only and unaggregated, it is well suited as a source in OBIEE subject areas, Discoverer workbooks, and custom PL/SQL extracts, while any maintenance of the underlying personnel budget data must be performed against IGW_BUDGET_PERSONS through the standard Grants Proposal application forms.