Results for “igw_org_questions”

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

Overview

IGW_ORG_QUESTIONS is a transactional table in the Oracle E-Business Suite Grants Proposal module (product code IGW). It stores the recorded answers to defined questions that pertain to a specific organization within the grants proposal process. The table functions as the intersection between organizations and the questionnaire definitions maintained by the application, capturing the response an organization has provided for each applicable question.

Within the ETRM 12.1.1 documentation the object is explicitly flagged as Obsolete, and the implementation notes state that it is "Not implemented in this database." This is a significant caveat: although the table is documented with a full physical schema, it is not present in the standard delivered instance and should not be assumed to exist in a production environment without verification. The product line it belongs to, IGW - Grants Proposal, was superseded by later grants functionality, which explains the obsolete status.

From a dimensional or Data Vault modeling perspective, the object is classified heuristically as satellite-leaning. Its composite primary key identifies a single answer context, while the descriptive attributes (the answer itself, explanation text, and review metadata) are non-key payload, consistent with a satellite structure. The heuristic classification is a modeling suggestion rather than a documented Oracle design decision.

Key Information Stored

The table contains ten documented columns. The most important are:

• ORGANIZATION_ID — Identifies the organization whose question responses are recorded. This is one of the two components of the primary key and is a foreign key to HR_ALL_ORGANIZATION_UNITS.
• QUESTION_NUMBER — Identifies the specific questionnaire item being answered. This is the second primary key component and is a foreign key to IGW_QUESTIONS.
• ANSWER — The response value captured for the organization and question combination.
• EXPLANATION — Free-text elaboration or rationale accompanying the answer.
• REVIEW_DATE — The date the response was reviewed, supporting audit and approval tracking.
• LAST_UPDATE_DATE — Standard EBS audit column recording the most recent modification timestamp.
• LAST_UPDATED_BY — The user who last modified the record.
• CREATION_DATE — The timestamp when the answer row was first created.
• CREATED_BY — The user who created the answer row.
• LAST_UPDATE_LOGIN — The login session identifier associated with the last update, used for EBS audit lineage.

The surrogate primary key is the composite IGW_ORG_YNQ_PK on (ORGANIZATION_ID, QUESTION_NUMBER). The unique index IGW_ORG_YNQ_U1 on the same two columns represents the business-key candidate, enforcing that only one answer exists per organization per question.

Common Use Cases and Queries

Typical use cases centre on questionnaire completeness reporting and organization-level compliance analysis. A common query retrieves all answers for a given organization, joined to the question definitions for readable prompts:

• Organization answer profile — SELECT q.answer, q.explanation, qn.prompt FROM igw_org_questions q, igw_questions qn WHERE q.question_number = qn.question_number AND q.organization_id = :org_id.
• Missing-answer detection — Compare the set of questions in IGW_QUESTIONS against those present in IGW_ORG_QUESTIONS for an organization to identify unanswered items.
• Review-status reporting — Filter on REVIEW_DATE to find responses that have not yet been reviewed, supporting approval workflows.
• Audit tracing — Use LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN to reconstruct which users changed responses and when.

Because the product is obsolete, these queries should be validated against the live instance before relying on them for reporting.

Related Objects

The following objects have documented relationships with IGW_ORG_QUESTIONS:

• IGW_QUESTIONS — Parent definition table for questionnaire items; joined via QUESTION_NUMBER.
• HR_ALL_ORGANIZATION_UNITS — Organization master; joined via ORGANIZATION_ID.
• IGW_REPORT_Q_EXPLANATION — Child/reporting table that references this table through (ORGANIZATION_ID, QUESTION_NUMBER) as a composite foreign key, indicating downstream reporting or explanation storage keyed to the same answer context.
• IGW_ORG_YNQ_PK — Primary key constraint defining the answer grain.
• IGW_ORG_YNQ_U1 — Unique index enforcing the business rule of one answer per organization and question.

These relationships confirm the table's role as the answer-level satellite sitting between the organization hub (HR_ALL_ORGANIZATION_UNITS) and the question definition hub (IGW_QUESTIONS), with dependent reporting downstream in IGW_REPORT_Q_EXPLANATION.