Results for “igw_proposals_v”

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

Overview

IGW_PROPOSALS_V is a reporting view associated with the Oracle Grants Proposal (IGW) product, a module whose functionality has been classified as obsolete. Per the documented metadata, this object carries the description "10SC Only," indicating that it was originally shipped to support the Oracle Grants Proposal application in the 10SC release lineage and is not implemented in current 12.1.1 or 12.2.2 environments. The view presents a consolidated, denormalized picture of a grant proposal record, joining the base proposal row to descriptive lookup values and to related party and organization entities so that each proposal can be reported on with human-readable names rather than raw identifiers.

Its role is essentially read-only reporting and integration. Rather than requiring consumers to reconstruct the relationships between proposals, lookups, customers, and personnel, the view exposes a pre-joined projection suitable for ad hoc queries, custom reports, and downstream extracts. Because the object is obsolete and not implemented in a 12.1.1 or 12.2.2 database, queries against it will typically fail with an invalid object error unless a custom or legacy schema still hosts it.

Underlying Base Objects

The documented base object list for this view is empty, but the view text reveals the underlying sources. The driving table is the proposal table, aliased PROP, which supplies the core proposal attributes and the ROWID used as ROW_ID. Descriptive codes are resolved through lookup joins (aliased LOOKUP1 through LOOKUP5) that translate status, type, activity, notice of opportunity, and sponsor action codes into meanings. Organization information is resolved through ORG1, providing the lead organization name, while customer tables CUST and CUST1 supply sponsor and original sponsor names. Personnel names are resolved through SGN and ADM, the signing and administrative officials respectively.

The view also invokes two PL/SQL functions: IGW_PROP.GET_PI_FULL_NAME, which derives the principal investigator's full name from the proposal ID and truncates it to 240 characters, and IGW_SECURITY.ALLOW_QUERY, which applies proposal-level security filtering based on FND_GLOBAL.USER_ID. The latter means the view is not merely a join projection but also enforces row-level access control.

Key Columns

• PROPOSAL_ID, PROPOSAL_NUMBER, PROPOSAL_TITLE, PROPOSAL_STATUS and PROPOSAL_STATUS_DESC — core identification and status of the proposal.
• LEAD_ORGANIZATION_ID and LEAD_ORGANIZATION_NAME — the organization leading the proposal.
• SPONSOR_ID, SPONSOR_NAME, FUNDING_SPONSOR_UNIT, ORIGINAL_SPONSOR_ID and ORIGINAL_SPONSOR_NAME — sponsor identity and hierarchy.
• SIGNING_OFFICIAL_ID and SIGNING_OFFICIAL_NAME — the official authorized to sign, the column family most relevant to the searched term.
• ADMIN_OFFICIAL_ID and ADMIN_OFFICIAL_NAME — the administrative official associated with the proposal.
• PI_FULL_NAME — derived principal investigator name.
• Dates including PROPOSAL_START_DATE, PROPOSAL_END_DATE, DEADLINE_DATE and LETTER_OF_INTENT_DUE_DATE.
• Award and action columns such as AWARD_NUMBER, AWARD_AMOUNT, SPONSOR_ACTION_CODE and SPONSOR_ACTION_DATE.
• Audit and descriptive-flex columns plus the security-filtering ALLOW_QUERY expression.

Common Use Cases and Queries

Typical usage centers on extracting proposals with their signing official and sponsor details, for example:

• SELECT proposal_number, proposal_title, signing_official_name FROM igw_proposals_v WHERE proposal_status_desc = 'Submitted';
• SELECT proposal_number, sponsor_name, pi_full_name, award_amount FROM igw_proposals_v;
• SELECT signing_official_name, COUNT(*) FROM igw_proposals_v GROUP BY signing_official_name;

These patterns assume the object exists in the target schema; in a documented 12.1.1 or 12.2.2 instance it does not, so the same reporting needs must be met through supported Grants objects or custom views.