Results for “jtf_ih_interactions_only_vl”

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

Overview

JTF_IH_INTERACTIONS_ONLY_VL is an APPS-owned view within the JTF (CRM Foundation) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name denotes "Interactions Only," signalling that the view projects the interaction entity in isolation, without forcing a join to the surrounding activity and contact scaffolding that defines the base JTF_IH_INTERACTIONS table. The "_VL" suffix indicates a value-set or language-dependent view that resolves translated descriptive columns (outcome, result, and reason short descriptions) using the session language.

In practice, the view serves as the canonical, denormalized read model for interaction records. It exposes a flat, report-ready structure that combines interaction header data with party names, resource names, application names, outcome codes and descriptions, result codes and descriptions, and reason codes and descriptions. Because the descriptive columns are translated at runtime, the same view returns language-appropriate text for each user session, which makes it suitable for multilingual reporting and for integration endpoints that must emit human-readable labels rather than raw IDs. It is widely referenced by CRM dashboards, telephony and contact-center reporting extracts, and by custom concurrent programs that summarize agent activity.

Underlying Base Objects

The view is defined over a fixed set of base physical objects, documented as follows:

• JTF_IH_INTERACTIONS (synonym) — the primary interaction fact table, aliased INT in the view text and supplying the interaction ID, timestamps, duration, and attribute columns.
• JTF_IH_ACTIVITIES (synonym) — aliased ACT, joined on INTERACTION_ID, and supplying the CUST_ACCOUNT_ID linkage.
• HZ_PARTIES (synonym) — aliased HZ, joined on PARTY_ID to resolve PARTY_NAME.
• HZ_CUST_ACCOUNTS (synonym) — referenced in the view's join path to relate the interaction to a customer account.
• JTF_RS_RESOURCE_EXTNS_VL (view) — aliased RSC, joined on RESOURCE_ID to provide RESOURCE_NAME.
• FND_APPLICATION_VL (view) — aliased APP, joined on APPLICATION_ID to expose APPLICATION_NAME and APPLICATION_SHORT_NAME.
• JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, and JTF_IH_REASONS_TL (synonyms) — the translated lookup tables that resolve OUTCOME_CODE, RESULT_CODE, and REASON_CODE alongside their short descriptions.

The translation joins (OUT, RSL, REA) carry the predicate LANGUAGE = USERENV('LANG'), while the result join is an outer join, allowing interactions with no recorded RESULT_ID to remain visible.

Key Columns

Interaction identity and audit columns (INTERACTION_ID, ROW_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) mirror the base table. Party and resource context is exposed through PARTY_ID/PARTY_NAME and RESOURCE_ID/RESOURCE_NAME. Application context is provided by HANDLER_ID, APPLICATION_NAME, and APPLICATION_SHORT_NAME.

Timing and effort columns include START_DATE_TIME, END_DATE_TIME, DURATION, PRODUCTIVE_TIME_AMOUNT, NON_PRODUCTIVE_TIME_AMOUNT, PREVIEW_TIME_AMOUNT, WRAP_UP_TIME_AMOUNT, and INTER_INTERACTION_DURATION. Classification columns include METHOD_CODE, SOURCE_CODE, SOURCE_CODE_ID, REFERENCE_FORM, SCRIPT_ID, OBJECT_ID, OBJECT_TYPE, and OBJECT_VERSION_NUMBER. The user's searched term, REA_DESC, is the alias for REA.SHORT_DESCRIPTION — the translated reason description joined from JTF_IH_REASONS_TL via REASON_ID, appearing alongside REASON_CODE, OUT_DESC, and RSL_DESC. Bulk-processing columns (BULK_WRITER_CODE, BULK_BATCH_TYPE, BULK_BATCH_ID, BULK_INTERACTION_ID) support high-volume interaction loads.

Common Use Cases and Queries

Typical queries retrieve interactions by resource, party, or time window, and surface the translated reason text for analysis. The following example returns reason descriptions for a given resource during a period:

SELECT interaction_id, start_date_time, party_name,
       resource_name, outcome_code, result_code,
       reason_code, rea_desc
FROM   apps.jtf_ih_interactions_only_vl
WHERE  resource_id = :p_resource_id
AND    start_date_time BETWEEN :p_from AND :p_to
ORDER  BY start_date_time;

Because REA_DESC is already translated, no additional lookup to JTF_IH_REASONS_TL is required, simplifying both ad-hoc reporting and extract programs. Other common uses include aggregating productive and non-productive time per agent, summarizing interactions by outcome or result code, and exposing customer-linked interactions through CUST_ACCOUNT_ID. Query performance benefits from filtering on indexed columns such as INTERACTION_ID, PARTY_ID, RESOURCE_ID, and START_DATE_TIME.