Results for “igw_budget_persons”

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

Overview

IGW_BUDGET_PERSONS is a table within the Oracle E-Business Suite Grants Proposal (IGW) module, identified in the ETRM metadata as obsolete and not implemented in the current database. Its documented purpose is to hold budgeting information about personnel associated with a grant proposal. In the historical IGW data model, this table served as the operational store for per-person budget line records, capturing how an individual's effort, appointment, and cost were reflected against a specific proposal version.

From a Data Vault modeling perspective, the metadata's heuristic classification places IGW_BUDGET_PERSONS as satellite-leaning. This suggests the table is best understood as a descriptive satellite attached to a stronger business hub or link, rather than as an independent hub of business keys. Its identity is largely inherited from parent proposal and budget entities (IGW_BUDGETS and IGW_PROP_PERSONS), with budget-specific descriptive attributes layered on top. Because it is documented as obsolete in the IGW module, references to it in a 12.1.1 / 12.2.2 environment are primarily historical, migration-related, or relevant to legacy reporting.

Key Information Stored

The table carries thirteen documented columns. The most significant are the keys and descriptive budgeting attributes:

• PROPOSAL_ID — Identifies the grant proposal to which the personnel budget line belongs; a core business key component and foreign key to IGW_BUDGETS.
• VERSION_ID — Distinguishes proposal versions, allowing multiple budget iterations for the same proposal.
• PERSON_ID — The individual person associated with the budget line; also part of the foreign key to IGW_PROP_PERSONS.
• PARTY_ID — The trading community party identifier; a business-key candidate and part of the primary key.
• APPOINTMENT_TYPE_CODE — Classifies the appointment or role (for example, academic, staff, or consultant), completing the primary key and driving budget rules.
• EFFECTIVE_DATE — The date from which the budget personnel record is effective.
• CALCULATION_BASE — The basis used to calculate the personnel budget amount.
• RECORD_VERSION_NUMBER — Supports optimistic locking or version tracking of the record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each row, when, and through which login.

The surrogate primary key is IGW_BUDGET_PERSONS_PK, defined over PROPOSAL_ID, VERSION_ID, PARTY_ID, and APPOINTMENT_TYPE_CODE. A separate unique index, IGW_BUDGET_PERSONS_U1, covers the same four columns, making them the documented business-key candidates. Persistence-layer attributes such as CALCULATION_BASE, EFFECTIVE_DATE, and the audit columns are descriptive and do not participate in the unique identity.

Common Use Cases and Queries

Typical use cases center on reporting and analysis of personnel costs within a proposal budget. A common pattern joins the table to its parent budget and person records:

• Listing all budgeted personnel for a proposal version: SELECT bp.* FROM igw_budget_persons bp WHERE bp.proposal_id = :proposal_id AND bp.version_id = :version_id;
• Joining to IGW_PROP_PERSONS to resolve the person behind PERSON_ID via PROPOSAL_ID and PERSON_ID.
• Joining to IGW_BUDGET_PERSONNEL_DETAILS, which references this table on PROPOSAL_ID, VERSION_ID, PERSON_ID, and APPOINTMENT_TYPE_CODE, to obtain the detailed budgeting breakdown.
• Aggregating personnel costs by APPOINTMENT_TYPE_CODE for budget summaries or comparisons across proposal versions.
• Audit and change tracking using LAST_UPDATE_DATE, LAST_UPDATED_BY, and RECORD_VERSION_NUMBER to identify recently modified budget lines.

Related Objects

The documented foreign-key relationships establish the table's role within the IGW proposal budget hierarchy:

• IGW_BUDGETS — Parent budget entity; referenced via PROPOSAL_ID (and VERSION_ID).
• IGW_PROP_PERSONS — Proposal personnel source; referenced via PROPOSAL_ID and PERSON_ID.
• IGW_BUDGET_PERSONNEL_DETAILS — Child detail table that references IGW_BUDGET_PERSONS on PROPOSAL_ID, VERSION_ID, PERSON_ID, and APPOINTMENT_TYPE_CODE, holding the finer-grained budgeting lines.

Together these objects form the personnel budgeting cluster of the legacy Grants Proposal module. Because IGW_BUDGET_PERSONS is documented as obsolete, integration or migration work should verify actual presence against the target database before relying on it in 12.1.1 or 12.2.2 environments.