Results for “igw_questions_tl”

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

Overview

IGW_QUESTIONS_TL is a translation ("TL") table in the Oracle E-Business Suite Grants Proposal module (IGW). It stores multiple-language support data for its base table, IGW_QUESTIONS, holding the language-dependent descriptive attributes of grant proposal questions for which the untranslated, structural attributes reside in the base table. The suffix _TL follows the standard Oracle EBS multilingual convention: the base table retains language-independent columns and primary key values, while the _TL table carries the translatable text columns keyed by both the entity identifier and LANGUAGE.

In Oracle EBS 12.1.1 and 12.2.2 this is a dated construct associated with the IGW — Grants Proposal product, which the ETRM metadata records as Obsolete. The metadata explicitly notes "Not implemented in this database," meaning the object is documented in the data model but is not physically deployed in the reference instance. Analysts should therefore treat it as a legacy artifact retained for model completeness rather than an active runtime table.

The documented relationship structure classifies this object, under the heuristic Data Vault guidance in the metadata, as satellite-leaning. This is a modeling suggestion: the table behaves like a satellite because it hangs off the base entity (IGW_QUESTIONS) via a foreign key on QUESTION_NUMBER and carries descriptive, non-key attributes rather than independent identity. Its data vault anchor — the hub — is effectively IGW_QUESTIONS.

Key Information Stored

The table comprises 12 documented columns. The most significant are:

• QUESTION_NUMBER — the identifier linking each translation row to the parent record in IGW_QUESTIONS; it forms part of the composite primary key.
• LANGUAGE — the language code identifying the locale of the translated content; it completes the composite primary key.
• DESCRIPTION — the translated question text, the primary user-facing attribute.
• EXPLANATION — translated explanatory content shown alongside the question.
• POLICY — the translated policy statement associated with the question.
• REGULATION — the translated regulatory reference or text.
• SOURCE_LANG — the source language from which the translation was derived, supporting language tracking in the multilingual model.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing audit and concurrency metadata.

The surrogate primary key is IGW_QUESTIONS_TL_PK, defined on (QUESTION_NUMBER, LANGUAGE). A documented unique index, IGW_QUESTIONS_TL_U1, spans (LANGUAGE, QUESTION_NUMBER) and serves as the business-key candidate, establishing that exactly one translation may exist per question per language.

Common Use Cases and Queries

The dominant use case is multilingual presentation of grant proposal questions: retrieving the correct textual attributes for a user's session language while falling back to the source language where a translation is absent. A representative join pattern follows.

• Language-specific question retrieval: join IGW_QUESTIONS q to IGW_QUESTIONS_TL t on q.question_number = t.question_number, filtered by t.language = :session_lang.
• Translation coverage reporting: aggregate counts by LANGUAGE to detect untranslated questions (rows present in the base table but missing in a target locale).
• Source-language auditing: group by SOURCE_LANG to trace derivation chains and translation lineage.
• Change tracking: filter on LAST_UPDATE_DATE to identify translations refreshed within a period.

A fallback query commonly uses an outer join to the _TL table with a NVL against the base language row, ensuring a value is returned even when no localized translation exists.

Related Objects

• IGW_QUESTIONS — the base (hub) table; joined on IGW_QUESTIONS_TL.QUESTION_NUMBER = IGW_QUESTIONS.QUESTION_NUMBER and the declared foreign key.
• IGW_QUESTIONS_TL_PK — the composite primary key constraint on (QUESTION_NUMBER, LANGUAGE).
• IGW_QUESTIONS_TL_U1 — the unique business-key index on (LANGUAGE, QUESTION_NUMBER).

Because the metadata documents only the single parent foreign key, the related-object footprint is narrow; downstream reporting views and multilingual inquiry pages in the Grants Proposal module would reference this table only through the base question entity. Given the object's documented Obsolete status and absence from the physical database, dependency analysis should confirm actual usage in any target instance before relying on it.