Results for “icx_questions_tl”

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

Overview

ICX_QUESTIONS_TL is the translation table for ICX_QUESTIONS, owned by the ICX schema in Oracle E-Business Suite. It is a core component of the Oracle iProcurement module, storing language-specific (translated) text for the questions defined in the base ICX_QUESTIONS table. In EBS 12.1.1 and 12.2.2, iProcurement uses these question definitions to support sourcing rules, requisition self-service questionnaires, supplier qualification surveys, and other setup-driven prompts presented to end users. The "_TL" suffix confirms that this is a multi-language companion table, meaning each base question row may have one or more translated rows keyed by LANGUAGE.

Per the heuristic Data Vault classification mined from the underlying key structure, ICX_QUESTIONS_TL is best modeled as a satellite. The business key (QUESTION_CODE) is inherited from the parent question entity, and the localized attributes (QUESTION, SOURCE_LANG) plus standard audit columns are descriptive context. A satellite designation is a modeling suggestion only; the physical object is a standard Oracle EBS translation table.

Key Information Stored

The table contains 9 documented columns. The most significant are:

• QUESTION_CODE — Part of the composite primary key (ICX_QUESTIONS_TL_PK) and the unique index ICX_QUESTIONS_TL_U1. It is the business key that ties each translation row back to the base ICX_QUESTIONS record.
• LANGUAGE — The remaining component of the composite PK and unique index. It identifies the language of the translated text (typically using Oracle's NLS language codes, e.g., US for American English).
• QUESTION — The translated question prompt displayed to users in the given language. This is the attribute carried by the satellite.
• SOURCE_LANG — The language from which the translation originated, used by the NLS translation maintenance process.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created or last modified the translation row, when, and from which login session.

Note that the surrogate primary key is not a synthetic sequence; the primary key ICX_QUESTIONS_TL_PK is the composite (QUESTION_CODE, LANGUAGE), which is also enforced by unique index ICX_QUESTIONS_TL_U1. There is no separate numeric surrogate identifier documented.

Common Use Cases and Queries

Typical uses include verifying that translations exist for all active questions, auditing incomplete localization, and joining translated prompts to setup or runtime questionnaire data. For example, to list all questions available in a specific language:

SELECT question_code, question FROM icx.icx_questions_tl WHERE language = 'US';

To detect base questions that are missing translations in a target language, an outer join against ICX_QUESTIONS is used:

SELECT q.question_code FROM icx.icx_questions q LEFT JOIN icx.icx_questions_tl tl ON q.question_code = tl.question_code AND tl.language = 'FR' WHERE tl.question_code IS NULL;

Reporting scenarios include building multi-language setup inventories, troubleshooting prompted questions showing untranslated or default text, and generating localized requisition or survey questionnaires. Because audit columns are present, change-tracking reports can be filtered on LAST_UPDATE_DATE for a given LANGUAGE to identify recent translation activity.

Related Objects

The following are the most significant related objects, joined on the columns indicated:

• ICX_QUESTIONS — The base question table; join on QUESTION_CODE. It supplies the untranslated definition and is the parent of this translation table.
• ICX_QUESTIONS_TL_PK — The composite primary key constraint on (QUESTION_CODE, LANGUAGE).
• ICX_QUESTIONS_TL_U1 — The unique index backing the business-key candidate on (QUESTION_CODE, LANGUAGE).
• iProcurement setup and questionnaire components that reference question definitions by QUESTION_CODE, consuming the translated QUESTION text at runtime.
• NLS translation maintenance utilities and the Oracle Applications Translation (or FND messaging / language) infrastructure, which populate SOURCE_LANG and LANGUAGE from the installed NLS language set.

Because the heuristic classification is standalone, no additional foreign-key satellites or links are required beyond the relationship to ICX_QUESTIONS.