Search Results igw_questions_tl




Overview
Explore in AI Chat

Overview

The IGW_QUESTIONS_TL table is a translation table within the Oracle E-Business Suite (EBS) Grants Proposal module (IGW). Its primary role is to provide multiple language support for the textual data associated with proposal questions. It stores translated versions of question prompts, help text, or other descriptive content that originates from its parent table, IGW_QUESTIONS. This design is a standard Oracle application architecture pattern, where a base table (suffix '_B') holds language-independent data and a corresponding translation table (suffix '_TL') holds the language-specific textual attributes. It is critical to note that the provided ETRM metadata explicitly states this module is marked as "Obsolete" and that the table is "Not implemented in this database," indicating it may not be present or actively used in standard deployments of EBS 12.1.1 or 12.2.2.

Key Information Stored

The table's structure is designed to associate a base record with its language-specific translations. The most critical columns, as indicated by the primary key definition, are QUESTION_NUMBER and LANGUAGE. The QUESTION_NUMBER column is the foreign key linking each translation row back to a specific record in the IGW_QUESTIONS base table. The LANGUAGE column identifies the language code (e.g., 'US' for American English, 'F' for French) for the translated text. While the specific content columns are not detailed in the provided metadata, typical translation tables in EBS include columns such as QUESTION_TEXT, DESCRIPTION, HELP_TEXT, or SOURCE_LANG. These would hold the actual translated strings and potentially track the source language of the original data.

Common Use Cases and Queries

In a functional environment, this table would be accessed to render proposal question interfaces in a user's preferred language. All queries would join to the IGW_QUESTIONS base table. A standard pattern for retrieving a question and its translation for a specific language would be:

  • SELECT q.question_number, tl.question_text, tl.language FROM igw_questions q, igw_questions_tl tl WHERE q.question_number = tl.question_number AND tl.language = USERENV('LANG');

Reporting use cases would involve aggregating or auditing translated content across different languages. However, given the object's obsolete status and non-implementation note, direct operational or reporting use against this specific table in a live EBS instance is highly unlikely.

Related Objects

The table has a documented, singular foreign key relationship, making it a child of the IGW_QUESTIONS base table. The relationship is defined as follows:

  • Foreign Key to IGW_QUESTIONS: The IGW_QUESTIONS_TL.QUESTION_NUMBER column references the primary key of the IGW_QUESTIONS table. This enforces that every translation record must correspond to a valid, existing question. There is no indication of other tables having foreign keys pointing to IGW_QUESTIONS_TL. As a translation table, it is intrinsically dependent on its parent table for all non-textual attributes and the core record definition.