Search Results jtf_ih_results_tl




Overview
Explore in AI Chat

Overview

The JTF_IH_RESULTS_TL table is a core data object within the Oracle E-Business Suite (EBS) CRM Foundation layer, specifically part of the Interaction History (IH) module. Its primary role is to store translated, language-specific descriptions for "Results" entities. In the context of Oracle EBS CRM, a "Result" typically defines the outcome or disposition of a customer interaction, such as a service request, a call, or a marketing activity. This table enables the multilingual support (NLS) required for global deployments, allowing result descriptions to be displayed in a user's preferred language. It functions as the translation child table to the base data table, JTF_IH_RESULTS_B, which holds the language-independent attributes.

Key Information Stored

The table's structure is characteristic of an EBS translation table. The critical columns, as defined by its primary key (JTF_IH_RESULTS_TL_PK), are RESULT_ID and LANGUAGE. The RESULT_ID is a foreign key that links each translated row to its corresponding master record in JTF_IH_RESULTS_B. The LANGUAGE column holds the language code (e.g., 'US' for American English, 'KO' for Korean) for the translation. The most significant data column, though not explicitly listed in the brief metadata but standard for TL tables, is typically named RESULT or DESCRIPTION. This column stores the actual translated text for the result name or description. Additional standard columns include SOURCE_LANG (indicating the original language of the master record), CREATION_DATE, and LAST_UPDATE_DATE for auditing.

Common Use Cases and Queries

The primary use case is the dynamic presentation of localized result codes within any user-facing CRM application component, such as the Service Request or TeleService forms. When a user with a non-base language preference queries or selects a result, the application joins to this table to retrieve the appropriate description. A common reporting query would join the base and translation tables to produce a list of all results with their descriptions in a specific language. For example:

  • SELECT b.RESULT_CODE, tl.RESULT FROM JTF_IH_RESULTS_B b, JTF_IH_RESULTS_TL tl WHERE b.RESULT_ID = tl.RESULT_ID AND tl.LANGUAGE = USERENV('LANG');

Another critical scenario involves data migration or setup, where administrators must populate this table with translated values for each installed language after defining the base results in JTF_IH_RESULTS_B.

Related Objects

The most direct and essential relationship for JTF_IH_RESULTS_TL is with its parent base table, JTF_IH_RESULTS_B, via the foreign key constraint on the RESULT_ID column. The JTF_IH_RESULTS_B table itself is central to the Interaction History results framework and is likely referenced by numerous application tables that track interaction outcomes, such as those in the Service Requests (CS) or TeleSales modules. While not specified in the metadata, related views may exist, such as JTF_IH_RESULTS_VL (a "View Latest" version that automatically selects translations based on the current session language), which is a standard EBS pattern for exposing translated data to applications and reports.