Results for “igw_prop_questions”

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

Overview

The IGW_PROP_QUESTIONS table is a core transactional object within the Oracle E-Business Suite Grants Proposal (IGW) module. It stores the captured answers to structured questions posed against a grant proposal, forming the qualitative response layer of the proposal record. In EBS 12.1.1 and 12.2.2, this table is owned by the IGW schema and is documented as VALID in the ETRM data dictionary, with twelve physical columns defined.

From a dimensional modeling perspective, the metadata suggests this object behaves as a link table. It resolves a many-to-many style association between a proposal and a question definition, carrying descriptive payload columns (ANSWER, EXPLANATION, review and audit attributes) that would typically be modeled as satellite content around that link. This classification is a heuristic mined from the foreign-key structure and should be treated as a modeling suggestion rather than a documented architectural mandate.

Key Information Stored

The table is keyed by the composite primary key IGW_PROP_QUESTIONS_PK on (PROPOSAL_ID, QUESTION_NUMBER). A separate unique index, IGW_PROP_QUESTIONS_U1, covers the same two columns, confirming them as the business-key candidates. A surrogate identifier, PROP_QUESTION_ID, is also present.

• PROPOSAL_ID — foreign key to IGW_PROPOSALS_ALL; identifies the proposal that owns the answer.
• QUESTION_NUMBER — foreign key to IGW_QUESTIONS; identifies the specific question being answered.
• ANSWER — the response value captured for the question.
• EXPLANATION — supporting narrative or justification text accompanying the answer.
• REVIEW_DATE — date the response was reviewed.
• PROP_QUESTION_ID — surrogate identifier column.
• RECORD_VERSION_NUMBER — optimistic locking / concurrency column.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

Reporting on proposal responses is the primary use case: reviewers, grant administrators, and compliance teams extract answers alongside proposal and question context. A typical join pattern combines the answer with its proposal and question definition:

• Listing all answers for a proposal: SELECT * FROM IGW_PROP_QUESTIONS WHERE PROPOSAL_ID = :id.
• Resolving question text: join IGW_PROP_QUESTIONS to IGW_QUESTIONS on QUESTION_NUMBER.
• Resolving proposal context: join to IGW_PROPOSALS_ALL on PROPOSAL_ID.
• Audit and change tracking: filter on LAST_UPDATE_DATE to find responses modified within a period.
• Completeness checks: count answered questions per proposal to detect missing responses.

Because the answer payload is free-form (ANSWER and EXPLANATION), downstream integrations frequently read this table to populate external grant management or reporting systems.

Related Objects

The following objects are directly related through documented foreign keys or the primary key structure:

• IGW_PROPOSALS_ALL — referenced by IGW_PROP_QUESTIONS.PROPOSAL_ID; the parent proposal record.
• IGW_QUESTIONS — referenced by IGW_PROP_QUESTIONS.QUESTION_NUMBER; the question definition.
• IGW_PROP_QUESTIONS_PK / IGW_PROP_QUESTIONS_U1 — primary and unique indexes enforcing proposal/question uniqueness.

Together these objects constitute the question-and-answer framework within the Grants Proposal module, allowing responses to be reliably associated with both their originating proposal and their defining question.