Search Results budget_category_code




Overview
Explore in AI Chat

Overview

IGW_PRPO_ROLES_DETAILS_V is a public synonym view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Grants Management module (the IGW product short name) and, within that module, to the Proposal Roles and Personnel sub-entity used by the Oracle Grants Proposal (PRPO) application. The view surfaces the attributes that describe a proposal role line as it is recorded against a proposal and its associated budget period: role identity, headcount, salary basis, requested salary, person-months, and the date range over which the role is funded.

The object is not a transactional reporting view over live data. Its defining SQL statement selects literal values and constants from the Oracle DUAL table. Consequently the view always returns exactly one synthetic row regardless of the caller, the operating unit, or the contents of any Grants table. This construction is typical of Oracle ETRM "documented view" stubs that preserve the interface and column list of a legacy or internal view while suppressing the proprietary join logic from the published documentation set.

Underlying Base Objects

The ETRM metadata for this view is explicit: the only referenced object is DUAL, the built-in one-row, one-column dictionary table supplied by the Oracle database. No base tables or additional views are documented as dependencies for this object.

In a functioning Grants Management implementation, a proposal role details view would normally draw on the Grants proposal role schema, such as IGW_PROP_ROLE_DETAILS and its parent proposal and budget period entities. The metadata provided here records none of those dependencies, and the DUAL-based view text corroborates that no such joins exist in the documented definition. The structure of the projection nevertheless mirrors the column layout a caller would expect from the proposal role details entity.

The column names in the projection map directly to the business attributes of a proposal role line: PROPOSAL_ID and BUDGET_PERIOD_ID identify the proposal and funding period; PROPOSAL_ROLE_CODE and PROPOSAL_ROLE name the role; NO_OF_PERSONS and PERSON_MONTHS quantify effort; BASE_SALARY and SALARY_REQUESTED carry the compensation figures; BUDGET_CATEGORY_CODE classifies the expenditure; and PERIOD_BEGINNING_DATE and PERIOD_END_DATE bound the role's active dates.

Key Columns

  • NO_OF_PERSONS — Number of persons assigned to the proposal role. Returned as the constant 1.
  • PROPOSAL_ROLE_CODE — Code identifying the role, for example the code value behind a role such as Principal Investigator or Co-Investigator. Returned as the literal 'PROPOSAL_ROLE_CODE'.
  • PROPOSAL_ROLE — Descriptive name of the role. Returned as the literal 'PROPOSAL_ROLE'.
  • BASE_SALARY — Base salary used as the calculation basis for the role. Returned as the constant 1000.
  • BUDGET_CATEGORY_CODE — Budget category to which the role cost is charged. Returned as the literal 'BUDGET_CATEGORY_CODE'.
  • PERIOD_BEGINNING_DATE — Start date of the budget period for which the role is funded. Returned as TO_DATE('01-01-00','DD:MM:YY').
  • PERIOD_END_DATE — End date of the budget period for which the role is funded. Returned as TO_DATE('31-01-10','DD:MM:YY').
  • PERSON_MONTHS — Effort expressed in person-months. Returned as the constant 1.
  • SALARY_REQUESTED — Salary amount requested for the role. Returned as the constant 1000.
  • PROPOSAL_ID — Identifier of the parent proposal. Returned as the constant 1.
  • BUDGET_PERIOD_ID — Identifier of the budget period. Returned as the constant 1.

Common Use Cases and Queries

Because the view returns constants, it is used for interface validation, column-name discovery, and report layout prototyping rather than for operational reporting against live Grants data. A caller investigating the term proposal_role_code, the query that located this object, will typically inspect the view definition and structure as shown below.

  • Column discovery — SELECT * FROM apps.igw_prpo_roles_details_v; returns the single synthetic row documenting the column list.
  • Role line inspection — SELECT proposal_id, proposal_role_code, proposal_role, salary_requested FROM apps.igw_prpo_roles_details_v; demonstrates the projection without touching live proposal data.
  • Date formatting checks — SELECT period_beginning_date, period_end_date FROM apps.igw_prpo_roles_details_v; exercises the date literals as rendered by the view text.
  • Definition review — Querying DBA_VIEWS or ALL_VIEWS for the object confirms the DUAL-based SELECT statement and the APPS ownership.

For production reporting on proposal roles, personnel, and salary requests, the live Grants tables such as IGW_PROP_ROLE_DETAILS should be queried directly, as this view is intended only to document the public interface.