Results for “igw_prpo_yn_responses_v”

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

Overview

IGW_PRPO_YN_RESPONSES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGW (Grants Proposal) product family. Its purpose is to consolidate the yes/no answers captured against proposal, organization, and person-level questions into a single, uniformly structured result set. The view presents each question response in a normalized form, decoding internal numeric answer codes into readable indicator values and exposing the associated explanation text and review date. Because grant proposals require applicants to attest to a range of eligibility, compliance, and certification statements concerning the institution, the project, and named individuals, this view provides a convenient integration and reporting surface for that questionnaire data without requiring consumers to query three separate base tables and reconcile their differing structures.

The view is documented as VALID and is oriented toward reporting rather than transactional processing. Consumers typically use it to audit which questions were answered, to verify reviewer attention via the review date, and to feed downstream extracts or interfaces that need a consolidated question-and-answer record across all applicability levels.

Underlying Base Objects

The view is defined as a three-way UNION ALL-style composite over the following IGW tables, joined to IGW_PROPOSALS where required:

• IGW_PROP_QUESTIONS — proposal-level question responses, projected with QUESTION_APPLIES_TO = 'P'.
• IGW_ORG_QUESTIONS joined to IGW_PROPOSALS on ORGANIZATION_ID = SUBMITTING_ORGANIZATION_ID — organization-level responses, projected with QUESTION_APPLIES_TO = 'O'.
• IGW_PROP_PERSON_QUESTIONS — person-level responses, projected with QUESTION_APPLIES_TO = 'I', carrying both PERSON_ID and PARTY_ID.

Each branch filters out unanswered questions using the predicate ANSWER <> 3, so only definitive responses are surfaced. The union aligns the three sources by populating the shared columns and supplying TO_NUMBER(NULL) placeholders for the columns that do not apply to a given branch.

Key Columns

• PROPOSAL_ID — identifier of the grant proposal to which the response belongs.
• ORGANIZATION_ID — populated only for organization-level ('O') responses.
• PERSON_ID and PERSON_PARTY_ID — populated only for individual-level ('I') responses.
• QUESTION_APPLIES_TO — discriminator indicating whether the row applies to the Proposal ('P'), Organization ('O'), or Individual ('I').
• QUESTION_NUMBER — the question identifier within its source set.
• RESPONSE — the decoded answer, where internal code '1' is rendered as 'Y' and '2' as 'N'.
• EXPLANATION — free-text detail supplied by the respondent.
• REVIEW_DATE — the date the response was reviewed, which is the column most frequently targeted when users search on "review_date" to audit reviewer activity or track turnaround.

Common Use Cases and Queries

Typical uses include compliance reporting, reviewer workload analysis, and interfaces that export questionnaire data. A common query filters and orders by the review date to identify recently reviewed responses across all applicability levels:

• SELECT proposal_id, question_applies_to, question_number, response, review_date FROM igw_prpo_yn_responses_v WHERE review_date IS NOT NULL AND review_date >= :p_from_date ORDER BY review_date DESC;
• SELECT question_applies_to, COUNT(*) FROM igw_prpo_yn_responses_v WHERE proposal_id = :p_proposal_id GROUP BY question_applies_to;
• SELECT person_id, question_number, response, explanation FROM igw_prpo_yn_responses_v WHERE question_applies_to = 'I' AND proposal_id = :p_proposal_id;

Because the view resides in APPS, queries should be executed with the appropriate MO or responsibility context and grantees on the underlying IGW tables.