Results for “jtf_ih_interactions_vl”

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

Overview

JTF_IH_INTERACTIONS_VL is a CRM Foundation (JTF) view owned by the APPS schema that presents a denormalized, reporting-ready projection of interaction records stored in the Interaction History (IH) subsystem. The view consolidates the core interaction entity with its associated outcome, result, and reason reference data, plus the involved party, resource, customer account, handler application, and activity context. Its "_VL" suffix indicates a "value list" style view that joins translated (_TL) lookup tables for short descriptions, so each row exposes both a code and a language-resolved description for outcome, result, and reason.

Because it flattens multiple parent-child relationships into a single SELECT, the view is well suited for ad-hoc reporting, BI Publisher extracts, Discoverer workbooks, and integration interfaces that need a one-row-per-interaction picture. It is the standard object referenced when end users search for columns such as rsl_desc, which is the language-dependent short description of the interaction result.

Underlying Base Objects

The view is defined over the following documented objects:

• JTF_IH_INTERACTIONS – driving table holding one row per interaction.
• JTF_IH_ACTIVITIES – activity context, joined with an outer (+) operator to the interaction.
• HZ_PARTIES – party name for the interaction's party.
• HZ_CUST_ACCOUNTS – customer account number, outer-joined through the activity.
• JTF_RS_RESOURCE_EXTNS_VL – resource name for the interaction owner.
• FND_APPLICATION_VL – application name and short name of the handler.
• JTF_IH_OUTCOMES_TL – outcome code and short description (outer-joined, language filtered).
• JTF_IH_RESULTS_TL – result code and short description (source of RSL_DESC).
• JTF_IH_REASONS_TL – reason code and short description.

All referenced objects are synonyms or views in the APPS schema, so the joins ultimately resolve to the underlying JTF and HZ base tables. The result, outcome, and reason joins use outer joins with a language predicate, meaning an interaction is returned even when its lookup description is missing in the session language.

Key Columns

• INTERACTION_ID, ROW_ID – primary identifier and row identifier.
• PARTY_ID, PARTY_NAME – party and its name.
• RESOURCE_ID, RESOURCE_NAME – owning resource.
• HANDLER_ID, APPLICATION_SHORT_NAME, APPLICATION_NAME – handler application.
• CUST_ACCOUNT_ID, ACCOUNT_NUMBER – related customer account.
• START_DATE_TIME, END_DATE_TIME, DURATION – timing metrics.
• OUTCOME_CODE, OUT_DESC – outcome lookup.
• RESULT_CODE, RSL_DESC – result lookup; RSL_DESC is the searched column.
• REASON_CODE, REA_DESC – reason lookup.
• METHOD_CODE, SOURCE_CODE, OBJECT_TYPE, BULK_* columns – method, source, and bulk-interaction attributes.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1..15 – flexfield descriptive columns.

Common Use Cases and Queries

Typical use is producing interaction-history reports that require the result description alongside the interaction and its owner.

• Interaction outcome analysis by result and reason.
• Resource productivity reporting using duration columns.
• Customer-facing extracts joining party and account data.
• Integration feeds needing code plus language-resolved descriptions.

Sample SQL:

• SELECT interaction_id, party_name, resource_name, start_date_time, result_code, rsl_desc FROM jtf_ih_interactions_vl WHERE rsl_desc IS NOT NULL;
• SELECT result_code, rsl_desc, COUNT(*) FROM jtf_ih_interactions_vl GROUP BY result_code, rsl_desc ORDER BY 3 DESC;
• SELECT i.interaction_id, i.rsl_desc, a.account_number FROM jtf_ih_interactions_vl i WHERE i.start_date_time >= :p_from_date;