Results for “bud_pers”

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

Overview

IGWBV_GRANT_PRPSL_BDGT_PERSON is a read-only Oracle EBS view in the APPS schema that presents person-level budget allocation data associated with grant proposals. It belongs to the Oracle Grants Accounting (IGW) product family and serves as a denormalized reporting and integration surface that joins proposal header information to the individual persons whose effort, salary, or cost is budgeted against a proposal version. The view is defined with a WITH READ ONLY clause, meaning it is strictly a query object: no DML is permitted against it, and all maintenance must be performed on the underlying base tables.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view addresses a recurring reporting requirement in grants management — retrieving the human resource dimension of a proposal budget without requiring the report author to know the internal foreign-key relationships between the proposal and budget-person entities. It is exposed under the APPS schema, which makes it available to standard EBS responsibilities, concurrent programs, and any integration layer that queries the applications database with APPS-level synonyms.

Underlying Base Objects

The view is defined over exactly two base objects, joined on the proposal identifier:

• IGW_PROPOSALS_ALL (aliased PR) — the master proposal table in Oracle Grants Accounting, supplying the proposal number and proposal identifier.
• IGW_BUDGET_PERSONS (aliased BUD_PERS) — the budget person detail table, supplying version, effective dating, calculation basis, and person identity.

The join condition is a simple equijoin: PR.PROPOSAL_ID = BUD_PERS.PROPOSAL_ID. This produces one row for each budget-person record across all proposal versions that share a given proposal, so a proposal with multiple versions and multiple budgeted persons yields a Cartesian-style expansion of rows. The documented ETRM metadata lists no additional referenced base objects, so the two tables above constitute the complete data lineage for the view.

Key Columns

• PROPOSAL_NUMBER — the user-visible identifier of the grant proposal, sourced from IGW_PROPOSALS_ALL.
• PROPOSAL_ID — the internal surrogate key linking proposal and budget-person records.
• VERSION_ID — identifies the specific budget or proposal version to which the person record belongs.
• PERSON_ID — the party/person identifier referencing the HR or resource person budgeted on the proposal.
• EFFECTIVE_DATE — the date from which the budget-person record is effective, supporting date-tracked analysis.
• CALCULATION_BASE — the basis on which the person's budgeted amount is calculated, such as salary, effort percentage, or a defined cost base.
• APPOINTMENT_TYPE_CODE — exposed indirectly (see the note below) as a descriptive lookup value for the person's appointment type.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY provide standard EBS audit trail information.

One column is not returned as a literal value. The literal string '_LA:BUD_PERS.APPOINTMENT_TYPE_CODE:IGW_LOOKUPS_V:IGW_APPOINTMENT_TYPE:MEANING' is an EBS descriptive-flexfield/LOV directive token. It instructs the reporting framework to resolve the appointment type code against the IGW_LOOKUPS_V view filtered to the IGW_APPOINTMENT_TYPE lookup type and to display the lookup MEANING. Report consumers should therefore treat that position as the appointment type description at runtime.

Common Use Cases and Queries

Typical scenarios include proposal budget-person listings, effort and appointment-type analysis across proposal versions, and data extracts feeding downstream costing or grant reporting. The view is equally suitable for ad hoc SQL through a tool such as SQL*Plus or Toad, and for embedded use in Oracle Reports, BI Publisher, or OAF-based pages.

A basic listing for a single proposal is:

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

To analyze budgeting by appointment type and version, grouping on the resolved lookup and version identifier is common:

• SELECT version_id, appointment_type_code, COUNT(*) person_count FROM apps.igwbv_grant_prpsl_bdgt_person GROUP BY version_id, appointment_type_code;

For auditing recently changed person budget records, filter on the audit columns:

• SELECT proposal_number, version_id, person_id, last_update_date, last_updated_by FROM apps.igwbv_grant_prpsl_bdgt_person WHERE last_update_date >= :since_date;

Because the view is read-only and performs no aggregation, filtering by PROPOSAL_ID before joining to large downstream result sets is recommended for performance on high-volume grants implementations.