Results for “result_code”

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

Overview

JTF_IH_RESULTS_TL is the translation table for Results within the Oracle EBS CRM Foundation (JTF) product family, specifically the Interaction History (IH) subsystem. In Oracle EBS 12.1.1 and 12.2.2, Interaction History stores structured outcome records produced when agents complete interactions — calls, service requests, or campaign activities — and JTF_IH_RESULTS_TL holds the language-dependent, user-facing text for those outcomes. It is a companion to the base table JTF_IH_RESULTS_B, which carries the language-independent definition, and is owned by the JTF schema with status VALID in the ETRM repository.

Based on the mined foreign-key structure, the recommended Data Vault classification for this object is satellite-leaning. It depends on JTF_IH_RESULTS_B for its identity and adds descriptive, language-scoped attributes rather than introducing new business entities or relationships of its own. This makes it a classic descriptive satellite attached to a hub-like base record, with the language column acting as the discriminator for each translated row.

Key Information Stored

The table's documented surrogate/business primary key, JTF_IH_RESULTS_TL_PK, is composed of LANGUAGE and RESULT_ID. A separate unique index, JTF_IH_RESULTS_TL_U1, spans RESULT_ID, LANGUAGE, and ZD_EDITION_NAME, confirming that edition-aware uniqueness is enforced on top of the core two-column key. The columns of primary interest include:

• RESULT_ID — foreign key to JTF_IH_RESULTS_B; identifies the parent result definition and is the join pillar for all reporting.
• LANGUAGE — the language code, combined with RESULT_ID forming the primary key and determining which translated row is returned.
• SHORT_DESCRIPTION — the translated brief label displayed in Result picklists and lookup windows.
• LONG_DESCRIPTION — the translated extended text for the result outcome, used in agent scripts and detail views.
• RESULT_CODE — the translated or language-tagged code value associated with the result.
• MEDIA_TYPE — indicates the media context (for example telephony or web) to which the translated result applies.
• SOURCE_LANG — the source language from which the row was translated, supporting multilingual maintenance.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling which operating unit or group can see the row.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J layer during concurrent updates.
• ZD_EDITION_NAME — editioning column introduced for online patching in EBS 12.2, participating in the U1 unique index.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns captured on every DML operation.

Common Use Cases and Queries

The most common scenario is resolving a stored result identifier into text for the current session language, typically by joining the translation table to the base table and filtering on the user's language. For example:

• Populating Result value sets for Interaction History entry forms, driven by SHORT_DESCRIPTION filtered by LANGUAGE.
• Extracting multilingual outcome labels for CRM dashboards and call-center analytics, joining RESULT_ID back to JTF_IH_RESULTS_B for the untranslated definition.
• Auditing translation completeness — identifying RESULT_ID values in JTF_IH_RESULTS_B that lack a row for a given LANGUAGE.
• Reporting on security scope by grouping outcomes via SECURITY_GROUP_ID in multi-org deployments.

A representative query pattern is a join between JTF_IH_RESULTS_B and JTF_IH_RESULTS_TL on RESULT_ID, with a WHERE clause on LANGUAGE and SECURITY_GROUP_ID, ordering by SHORT_DESCRIPTION so the picklist displays alphabetically for the end user.

Related Objects

• JTF_IH_RESULTS_B — the base, language-independent table; joined on RESULT_ID and the parent of the TL row.
• JTF_IH_RESULTS_TL_PK — the composite primary key index (LANGUAGE, RESULT_ID) enforcing row uniqueness.
• JTF_IH_RESULTS_TL_U1 — the edition-aware unique index (RESULT_ID, LANGUAGE, ZD_EDITION_NAME).
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for access control.
• FND_LANGUAGES — provides the valid LANGUAGE values used by the primary key.
• Interaction History outcome and activity tables that consume result identifiers when recording agent interactions.

Because the translation table is a satellite, maintenance should always be performed alongside its base table to preserve referential and linguistic integrity across 12.1.1 and 12.2.2 environments.