Search Results jtf_ih_activities_v




Overview
Explore in AI Chat

Overview

JTF_IH_ACTIVITIES_V is an APPS-owned database view within the JTF – CRM Foundation product family. It is documented with a VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2 and is registered in the E-Business Suite Tables and Views Repository (ETRM). The view presents interaction activity records sourced from the JTF_IH_ACTIVITIES table, joined with translated action item descriptions drawn from JTF_IH_ACTION_ITEMS_TL. Its stated purpose is to support report generation over interaction activity data, making it a convenient read-only interface for extracting CRM interaction history without exposing consumers to the underlying join logic or the multi-language translation table.

The column DOC_SOURCE_OBJECT_NAME is one of the fields exposed directly from the base activity table and is frequently referenced when correlating interaction activities back to the source object that generated them.

Underlying Base Objects

The view is defined over two documented base objects, each referenced through a synonym in the APPS schema:

  • JTF_IH_ACTIVITIES — the primary table holding interaction activity rows. Every column in the view except ACTION_ITEM originates from this table, aliased as ACT.
  • JTF_IH_ACTION_ITEMS_TL — the translation table for action items, aliased as ITM. It is joined on ACTION_ITEM_ID and filtered by ITM.LANGUAGE = USERENV('LANG'), ensuring that the action item text is returned in the session's current language.

The ROW_ID column is supplied as ACT.ROWID, providing a pseudo-column identifier that allows consumers to locate the underlying activity row when the view is used in certain update or correlation scenarios. Because the join is driven by ACTION_ITEM_ID and constrained by language, the view is effectively an inner join over the action item translation, so an activity is returned only when a matching translated action item exists for the current language.

Key Columns

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also exposed.

Common Use Cases and Queries

The view is typically used to report on interaction activity volumes, outcomes, and durations, and to correlate activities with their originating source objects. A representative query filters by customer account and date range:

  • SELECT activity_id, doc_source_object_name, action_item, start_date_time, duration FROM jtf_ih_activities_v WHERE cust_account_id = :acct AND start_date_time >= :from_date;
  • Reporting on activities by source: SELECT doc_source_object_name, COUNT(*) FROM jtf_ih_activities_v GROUP BY doc_source_object_name;
  • Joining to other interaction views on INTERACTION_ID to build interaction history extracts.

Because the ACTION_ITEM text is resolved per session language, reports render action item descriptions correctly for the running user's locale. All access is read-only, and the view should be treated as a reporting and integration interface rather than a transaction entry point.