Search Results applies_to




Overview
Explore in AI Chat

Overview

IGW_PRPO_YN_RESPONSES_V is a reporting view in the Oracle E-Business Suite Grants Management (IGW) schema. Its purpose is to consolidate Yes/No questionnaire responses collected during the pre-proposal and proposal lifecycle into a single, uniformly structured result set. The view normalizes three distinct sources of answers — proposal-level, organization-level, and person-level questions — into one common format, tagging each row with an applies_to discriminator of 'P', 'O', or 'I' respectively.

In the EBS 12.1.1 and 12.2.2 code lines this object is exposed under the APPS schema and is typically consumed by Grants Management forms, OAF pages, and downstream reporting or integration routines that need a flattened picture of qualification questions. Because the view filters on ANSWER <> 3, it deliberately excludes unanswered questions and returns only affirmative (Y) or negative (N) responses. This makes it well suited to decision-support reporting, compliance checks, and extraction feeds.

Underlying Base Objects

The view text is defined as a three-way UNION over the following documented base tables:

All three branches enforce the same filter predicate ANSWER <> 3, ensuring consistency. The ETRM metadata lists no additional referenced base objects beyond these three tables and the join to IGW_PROPOSALS.

Key Columns

  • PROPOSAL_ID — identifier of the proposal to which the response belongs; present in all three branches and the primary correlation key.
  • APPLIES_TO — literal discriminator: 'P' (proposal), 'O' (organization), 'I' (person/party). This is the column users search for when filtering by response scope.
  • QUESTION_NUMBER — the ordinal/number of the qualification question answered.
  • RESPONSE — decoded value: 'Y' when ANSWER = '1', 'N' when ANSWER = '2'. Because the predicate excludes 3, no other values appear.
  • EXPLANATION — free-text justification supplied with the answer.
  • REVIEW_DATE — timestamp indicating when the response was last reviewed.
  • ORGANIZATION_ID / PERSON_ID / PARTY_ID (PERSON_PARTY_ID) — context identifiers returned only by the branch relevant to the row; the other positional columns are populated with TO_NUMBER(NULL).

Common Use Cases and Queries

Typical consumption includes proposal qualification dashboards, compliance auditing of Yes/No answers, and extraction of responses for integration into external grant systems. A representative query filtering by scope is:

  • SELECT PROPOSAL_ID, APPLIES_TO, QUESTION_NUMBER, RESPONSE, EXPLANATION FROM APPS.IGW_PRPO_YN_RESPONSES_V WHERE PROPOSAL_ID = :p_proposal_id ORDER BY APPLIES_TO, QUESTION_NUMBER;
  • SELECT APPLIES_TO, RESPONSE, COUNT(*) FROM APPS.IGW_PRPO_YN_RESPONSES_V GROUP BY APPLIES_TO, RESPONSE;
  • SELECT PROPOSAL_ID, QUESTION_NUMBER, EXPLANATION FROM APPS.IGW_PRPO_YN_RESPONSES_V WHERE RESPONSE = 'N' AND REVIEW_DATE > SYSDATE - 30;

Because the view resolves organization identity through IGW_PROPOSALS.SUBMITTING_ORGANIZATION_ID, joins back to proposal and organization tables should key on PROPOSAL_ID to avoid duplication across the unioned branches.