Results for “reason_required”

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

Overview

JTF_IH_REASONS_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the JTF – CRM Foundation product family and forms part of the Interaction History (IH) infrastructure used by Oracle TeleService, iSupport, and related CRM modules. The view consolidates the language-independent attributes stored in the JTF_IH_REASONS_B base table with the language-dependent, translated attributes stored in JTF_IH_REASONS_TL. Its fundamental purpose is to present reason codes and their descriptions in the session's current language, so that application screens, concurrent programs, and integration interfaces retrieve a single, denormalized row per reason without having to perform the base/translation join themselves.

Because the view filters the translation table on USERENV('LANG'), it is language-aware at query time. This makes it the preferred access point for any read-only consumer of reason data—whether an OA Framework page, a report, a BI Publisher data template, or a custom PL/SQL routine—that must display end-user-facing text rather than internal identifiers. The view is documented as VALID in ETRM metadata for 12.2.2 and is equally present in 12.1.1.

Underlying Base Objects

The view is defined over two synonyms that resolve to the underlying CRM Foundation tables:

• JTF_IH_REASONS_B — the base table holding non-translatable columns, including the primary key REASON_ID, the object version number, standard WHO audit columns, and the functional flags REASON_REQUIRED, VERSATILITY_CODE, GENERATE_PUBLIC_CALLBACK, GENERATE_PRIVATE_CALLBACK, and ACTIVE. It is aliased as B.
• JTF_IH_REASONS_TL — the translation table holding language-specific columns REASON_CODE, SHORT_DESCRIPTION, and LONG_DESCRIPTION, keyed by REASON_ID and LANGUAGE. It is aliased as T.

The two are joined on B.REASON_ID = T.REASON_ID, with an additional predicate T.LANGUAGE = USERENV('LANG') that restricts output to the current session language. The view also surfaces B.ROWID as ROW_ID, which allows downstream code to identify the physical base row for update-style processing when required.

Key Columns

• ROW_ID — the ROWID of the base table row, exposed for row identification.
• REASON_ID — the primary key and foreign key linking base and translation records; used in all joins to interaction, callback, and note entities.
• OBJECT_VERSION_NUMBER — supports optimistic locking in the underlying framework.
• REASON_CODE — the translated, user-visible code that identifies the reason.
• SHORT_DESCRIPTION / LONG_DESCRIPTION — translated display text for list-of-values and detail regions.
• REASON_REQUIRED — flag indicating whether a reason must be supplied for the associated interaction action.
• VERSATILITY_CODE — controls the contexts in which the reason may be applied.
• GENERATE_PUBLIC_CALLBACK / GENERATE_PRIVATE_CALLBACK — flags governing callback generation behavior.
• ACTIVE — enables or disables the reason for new use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include populating reason list-of-values on interaction logging pages, driving reports on callback and escalation reasons, and restricting validation to active reasons. Because the view already resolves the current language, queries are concise:

SELECT reason_id, reason_code, short_description
FROM apps.jtf_ih_reasons_vl
WHERE active = 'Y'
ORDER BY short_description;

To retrieve only reasons that mandate entry on an interaction:

SELECT reason_id, reason_code, short_description
FROM apps.jtf_ih_reasons_vl
WHERE active = 'Y'
AND reason_required = 'Y';

To join reason text onto interaction history records, application code typically joins REASON_ID from the interaction table to this view, avoiding a manual join to the _TL table and eliminating duplicate-language filtering logic. For integration interfaces, the view provides a stable, translated contract that insulates external systems from the B/TL table split, while ROW_ID and OBJECT_VERSION_NUMBER remain available where the framework requires row-level identification or version checking.