Results for “jtf_ih_outcomes_vl”

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

Overview

JTF_IH_OUTCOMES_VL is a translated (multi-language) view owned by the APPS schema within the JTF – CRM Foundation product family. It exposes outcome definitions used by Interaction History and the broader Interaction Tracking (IH) framework in Oracle E-Business Suite 12.1.1 and 12.2.2. An "outcome" represents the result or disposition of a customer interaction — for example, a call, visit, or service request — and drives follow-up behavior such as scoring, callback generation, and result capture. The _VL suffix indicates that the view joins the base table (_B) to the translation table (_TL) and filters the translation rows to the session language via USERENV('LANG'). This view is the standard read interface for Forms, OAF pages, concurrent programs, and custom reporting that must display outcome codes and descriptions in the user's own language, while remaining insulated from the physical split between language-independent and translated columns.

Underlying Base Objects

The view is defined over two documented base objects: JTF_IH_OUTCOMES_B (the base, language-independent table) and JTF_IH_OUTCOMES_TL (the translation table), both referenced through the APPS synonyms. The join predicate is B.OUTCOME_ID = T.OUTCOME_ID AND T.LANGUAGE = USERENV('LANG'). The _B table supplies the outcome identifier, operational flags, scoring, and audit columns; the _TL table supplies the language-dependent text — OUTCOME_CODE, SHORT_DESCRIPTION, and LONG_DESCRIPTION. Because the join is on the current session language, only one translation row per outcome is returned, and outcomes lacking a translation in that language are excluded. The view text also exposes B.ROWID as ROW_ID, a legacy construct retained for backward compatibility with older Forms-based code that expects a row identifier.

Key Columns

• OUTCOME_ID — Primary key of the outcome; used as the foreign key from interaction records.
• OUTCOME_CODE — Translated code identifying the outcome, sourced from _TL.
• SHORT_DESCRIPTION / LONG_DESCRIPTION — Translated descriptive text from _TL.
• RESULT_REQUIRED — Indicates whether a result value must be captured when the outcome is selected.
• VERSATILITY_CODE — Classifies the outcome's applicability across interaction channels or media.
• GENERATE_PUBLIC_CALLBACK / GENERATE_PRIVATE_CALLBACK — Control whether selecting the outcome triggers a public or private callback activity.
• SCORE — Numeric weighting applied to the outcome, typically for lead or interaction scoring.
• POSITIVE_OUTCOME_FLAG — Marks the outcome as positive or negative for reporting and qualification logic.
• ACTIVE — Enables or disables the outcome for selection in the UI.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER (used for optimistic locking in OAF).

Common Use Cases and Queries

Typical requirements include populating outcome lovs on interaction capture pages, extracting outcome reference data for reporting or data warehousing, and validating callback generation rules. A basic list of active outcomes for the current session language is:

SELECT outcome_id, outcome_code, short_description, score, positive_outcome_flag
FROM apps.jtf_ih_outcomes_vl
WHERE active = 'Y'
ORDER BY outcome_code;

To audit callback configuration:

SELECT outcome_code, generate_public_callback, generate_private_callback, result_required
FROM apps.jtf_ih_outcomes_vl
WHERE generate_public_callback = 'Y' OR generate_private_callback = 'Y';

For multilingual reporting, join the view to _TL directly, or query JTF_IH_OUTCOMES_TL with a specific LANGUAGE to compare translations across installations. Because the view depends on USERENV('LANG'), reports executed in a different session language may return different description text; concurrent programs should therefore set the language explicitly. All columns should be qualified with APPS if the querying schema does not own the synonym.