Results for “salary_requested”

36 results




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

Overview

The IGW_BUDGET_PERSONNEL_DETAILS table resides in the IGW schema, which supports the Oracle E-Business Suite Grants Proposal (IGW) product. In EBS 12.1.1 and 12.2.2, this table stores the personnel detail records that are attached to an individual budget line. Whereas the parent budget line defines the funding structure and period breakdown for a proposal, IGW_BUDGET_PERSONNEL_DETAILS captures the labor dimension of that line: which person is charged to the budget, over what interval, in what capacity, and at what salary and effort levels. Because a single budget line can carry multiple personnel assignments, this table typically holds many child rows per parent line item.

From a Data Vault modeling perspective, the documented foreign-key topology suggests a satellite-leaning classification. The table carries descriptive and quantitative attributes (dates, percentages, salary amounts) that describe a business entity rather than acting as a pure hub or a pure relationship link, although it also resolves associations between budget lines, persons, and proposal versions. Practitioners designing downstream warehouses should treat it as an attribute-bearing detail table whose grain is one personnel assignment per budget line.

Key Information Stored

The physical schema documents 23 columns. The most significant are:

Common Use Cases and Queries

Typical reporting scenarios include reconstructing a proposal's labor budget by period, tracking cost-sharing commitments, and reconciling calculated amounts against requested amounts. A frequent query joins the detail rows to their parent line and to the calculated amounts table:

  • Personnel cost-share reporting: aggregate COST_SHARING_AMOUNT and COST_SHARING_PERCENT by PROPOSAL_ID and VERSION_ID.
  • Effort distribution analysis: sum PERCENT_EFFORT by PERSON_ID across BUDGET_PERIOD_ID to validate that committed effort does not exceed 100 percent.
  • Line-level drill-down: join to IGW_BUDGET_DETAILS on LINE_ITEM_ID to present requested salary against the line's overall budgeted amount.
  • Version comparison: filter on VERSION_ID to compare personnel assumptions between successive budget versions.

Standard SQL patterns use BUDGET_PERSONNEL_DETAIL_ID as the join key to IGW_BUDGET_PERSONNEL_CAL_AMTS, and LINE_ITEM_ID or PROPOSAL_ID to reach the parent budget structures.

Related Objects

  • IGW_BUDGET_DETAILS — Parent budget line; joined via LINE_ITEM_ID.
  • IGW_BUDGET_PERSONS — Person/proposal association; joined via PROPOSAL_ID.
  • VEA_VERSIONS — Proposal version control; joined via VERSION_ID.
  • IGW_BUDGET_PERSONNEL_CAL_AMTS — Child table holding calculated amounts; joined via BUDGET_PERSONNEL_DETAIL_ID.