Results for “question_number”

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

Overview

IGW_QUESTIONS is a foundational configuration and reference table within the Oracle E-Business Suite Grants Proposal (IGW) module. It stores the definitions of questions that are presented to users when capturing information about individuals, proposals, and organizations. In the Grants Proposal workflow, these questions drive structured data collection at the proposal, person, and organization levels, supporting eligibility determination, compliance checks, and grants-specific business rules.

The table resides in the IGW schema and holds a status of VALID in Oracle EBS 12.1.1 and 12.2.2. It is the central hub from which all question assignments are derived. A heuristic Data Vault classification of this object suggests a hub-leaning role: the table functions as a master list of question definitions, with dependent relationship tables acting as satellites or links that bind questions to specific business entities. This hub role reflects the table's position as the single source of truth for question identity, keyed by QUESTION_NUMBER.

Key Information Stored

The physical schema documented for this table contains 13 columns. The most significant columns are:

• QUESTION_NUMBER — The primary key (IGW_QUESTIONS_PK) and the business-key candidate (unique index IGW_QUESTIONS_U1). This surrogate identifier uniquely identifies each question and is the column referenced by every foreign-key relationship in the model.
• APPLIES_TO — Indicates the entity scope for the question, distinguishing whether it applies to individuals, proposals, or organizations. This drives which assignment table the question joins to.
• EXPLANATION_FOR_YES_FLAG — Controls whether an explanatory note is required or displayed when the user answers "Yes" to the question.
• EXPLANATION_FOR_NO_FLAG — Controls whether an explanatory note is required or displayed when the user answers "No".
• DATE_FOR_YES_FLAG — Governs whether a date value must be captured when the answer is "Yes".
• DATE_FOR_NO_FLAG — Governs whether a date value must be captured when the answer is "No".
• START_DATE_ACTIVE — The date from which the question becomes effective for use in the application.
• END_DATE_ACTIVE — The date after which the question is no longer active.

The remaining audit columns—LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN—provide the standard Oracle EBS who-did-what and when tracking required for transactional and configuration tables. The translation table IGW_QUESTIONS_TL supplies the actual question text and descriptions, keeping the base IGW_QUESTIONS table language-independent.

Common Use Cases and Queries

Typical reporting and integration scenarios include identifying the active question set for a given entity scope, validating completeness of answers, and auditing configuration changes. A representative query to retrieve active proposal questions is:

• SELECT q.QUESTION_NUMBER, t.QUESTION_TEXT FROM IGW_QUESTIONS q, IGW_QUESTIONS_TL t WHERE q.QUESTION_NUMBER = t.QUESTION_NUMBER AND q.APPLIES_TO = 'PROPOSAL' AND SYSDATE BETWEEN q.START_DATE_ACTIVE AND NVL(q.END_DATE_ACTIVE, SYSDATE + 1);
• Joining to IGW_PROP_QUESTIONS to report which questions are enabled for a specific proposal, or to IGW_ORG_QUESTIONS and IGW_PROP_PERSON_QUESTIONS for organization- and person-level reporting.
• Auditing inactive or expired questions using START_DATE_ACTIVE and END_DATE_ACTIVE filters.
• Determining follow-up capture requirements (explanation and date flags) to validate that responses stored in dependent tables include the mandated narrative or date values.

Related Objects

The table's relationships are defined by four child tables that reference QUESTION_NUMBER. These are the most significant related objects:

• IGW_ORG_QUESTIONS — Assigns questions to organizations; joins on IGW_ORG_QUESTIONS.QUESTION_NUMBER = IGW_QUESTIONS.QUESTION_NUMBER.
• IGW_PROP_QUESTIONS — Assigns questions to proposals; joins on IGW_PROP_QUESTIONS.QUESTION_NUMBER = IGW_QUESTIONS.QUESTION_NUMBER.
• IGW_PROP_PERSON_QUESTIONS — Assigns questions to proposal personnel; joins on IGW_PROP_PERSON_QUESTIONS.QUESTION_NUMBER = IGW_QUESTIONS.QUESTION_NUMBER.
• IGW_QUESTIONS_TL — Stores translatable question text and description; joins on IGW_QUESTIONS_TL.QUESTION_NUMBER = IGW_QUESTIONS.QUESTION_NUMBER.

These four relationships define the complete documented dependency surface of IGW_QUESTIONS. Together they allow the same question definition to be reused across organizations, proposals, and persons while preserving a normalized, centrally governed question catalog.