Search Results science_code




Overview
Explore in AI Chat

Overview

IGWFV_GRANT_PROPOSAL_KEYWORD is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It exposes grant proposal records together with their associated science code keywords, providing a flattened, read-only reporting surface for the Grants Accounting / Oracle Grants Management (IGW) module. The view is registered in the FND Design Data repository under the design data name IGW.IGWFV_GRANT_PROPOSAL_KEYWORD, which confirms it is a seeded, released object rather than a customer extension. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and the underlying definition is unchanged across those releases.

The view presents one row per proposal-to-science-code association. Because a single proposal may carry multiple science codes, the view can return multiple rows for the same PROPOSAL_ID. This denormalised shape makes it convenient for ad hoc reporting, Discoverer workbooks, and BI Publisher data models where a direct join to base grant tables would otherwise be required.

Underlying Base Objects

The view is defined over three documented base objects in the APPS schema:

  • IGW_PROPOSALS_ALL — the master proposal header table. It supplies PROPOSALNUMBER, PROPOSAL_ID, DESCRIPTION, and the standard WHO audit columns.
  • IGW_PROP_SCIENCE_CODES — the intersection table linking proposals to science codes.
  • IGW_SCIENCE_CODES — the science code reference table that resolves the code value and its description.

The join path is proposal header to intersection table by PROPOSAL_ID, then to the science code reference table by science code. No database object references IGWFV_GRANT_PROPOSAL_KEYWORD, so it functions purely as a terminal reporting view and carries no downstream dependency risk. Because it is a view, no data is stored; all values are derived at query time from the base tables, and any change to a proposal's science codes is reflected immediately.

Key Columns

  • PROPOSALNUMBER (VARCHAR2, 30) — the user-visible proposal identifier used in grant applications and award documentation.
  • PROPOSAL_ID (NUMBER, 15) — the internal surrogate primary key for the proposal, used for joins to other IGW tables.
  • SCIENCE_CODE (VARCHAR2, 15) — the science code value. This is the column matched when a user searches on "science_code", and it corresponds to the code held in IGW_SCIENCE_CODES.
  • DESCRIPTION (VARCHAR2, 250) — the descriptive text associated with the science code, providing the human-readable meaning of the code.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard Oracle WHO audit columns inherited from the base records for change tracking and attribution.

Common Use Cases and Queries

Typical uses include listing the science codes assigned to a proposal, searching for proposals by science code, and feeding keyword data into extracts. The following query returns all keywords for a given proposal:

SELECT proposalnumber, science_code, description
FROM   apps.igwfv_grant_proposal_keyword
WHERE  proposal_id = :p_proposal_id;

To locate proposals carrying a specific science code — the pattern implied by the "science_code" search — use:

SELECT proposalnumber, proposal_id, description
FROM   apps.igwfv_grant_proposal_keyword
WHERE  science_code = :p_science_code
ORDER  BY proposalnumber;

Because the view is a BIS reporting object, it is suitable for read-only access from custom reports, BI Publisher templates, and OBIEE repositories. It should not be used as a target for DML; inserts and updates must be performed against the underlying IGW_PROP_PROPOSALS and IGW_PROP_SCIENCE_CODES tables. When extracting large volumes, note the one-to-many cardinality between proposals and science codes and apply DISTINCT or aggregation where a single row per proposal is required.