Results for “jtf_ih_activities_vl”

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

Overview

JTF_IH_ACTIVITIES_VL is an Oracle E-Business Suite database view owned by the APPS schema and defined within the JTF - CRM Foundation product family. It exposes the interaction history activities of the CRM Interaction History module in a denormalized, presentation-ready form. Where the underlying transactional table JTF_IH_ACTIVITIES stores raw activity records, this view joins those records to the surrounding interaction context, party identity, resource, media item, lookup, and reference data needed to render a meaningful activity row. In Oracle EBS 12.1.1 and 12.2.2, the object is documented as VALID. Its practical role is twofold: it supports CRM reporting and inquiry screens that list call activities, and it provides a stable, joined interface for custom reporting, extracts, and integration routines that must not query the base tables directly.

Underlying Base Objects

The view is constructed primarily from JTF_IH_ACTIVITIES (aliased ACT), which supplies the core activity columns, and JTF_IH_INTERACTIONS (INT), which contributes the owning interaction's resource, handler, and party identifiers. HZ_PARTIES (HZ) provides the party name, while HZ_CUST_ACCOUNTS supplies the account number. JTF_IH_MEDIA_ITEMS (MEDIA) adds the media direction and media item attributes that describe the channel of the activity. Descriptive, translated lookups are drawn from JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, JTF_IH_REASONS_TL, JTF_IH_ACTIONS_TL, and JTF_IH_ACTION_ITEMS_TL. FND_APPLICATION_VL supplies the application short name and name, and additional object-function metadata comes from JTF_OBJECTS_B and JTF_TASKS_B. Resource details are resolved through JTF_RS_RESOURCE_EXTNS_VL. The view therefore spans both transactional and reference data, which explains its breadth and the volume of joined columns it exposes.

Key Columns

• ACTIVITY_ID / INTERACTION_ID — Primary activity key and the parent interaction to which the activity belongs; the anchor for joins back to base tables.
• ROW_ID — The ROWID of the underlying JTF_IH_ACTIVITIES row, used for row-level addressing.
• START_DATE_TIME / END_DATE_TIME / DURATION — Activity scheduling and elapsed-time attributes.
• PARTY_NAME / PARTY_ID / CUST_ACCOUNT_ID / ACCOUNT_NUMBER — The party and customer account associated with the interaction.
• RESOURCE_ID / RESOURCE_NAME / HANDLER_ID — The CRM resource who performed or handled the activity.
• DIRECTION / MEDIA_DATA / MEDIA_ITEM_REF / MEDIA_ITEM_TYPE / MEDIADIRTYPE — The channel and direction of the activity, including the concatenated media direction and type.
• OUTCOME_CODE / OUT_DESC, RESULT_CODE / RSL_DESC, REASON_CODE / REA_DESC — Translated outcome, result, and reason values.
• ACTION / ACTION_ITEM / ACTITM — Action and action item identifiers with their translated descriptions.
• APPLICATION_SHORT_NAME / APPLICATION_NAME — The owning application of the activity.
• OBJECT_TYPE / OBJECT_ID / OBJECT_FUNCTION / OBJECT_PARAMETERS — The source object reference for the activity.
• SOURCE_CODE / SOURCE_CODE_ID, ROLE, ACTIVE, DESCRIPTION, SCRIPT_TRANS_ID — Additional context and lifecycle attributes.
• BULK_WRITER_CODE / BULK_BATCH_TYPE / BULK_BATCH_ID / BULK_INTERACTION_ID — Bulk interaction processing identifiers.

Common Use Cases and Queries

Typical scenarios include listing all activities for a customer, reporting activity volumes by resource or channel, and extracting interaction history for analytics or archival. Because the view already resolves the party, resource, media, and translated lookup descriptions, most queries need no additional joins.

SELECT activity_id, interaction_id, party_name, resource_name,
       start_date_time, duration, outcome_code, out_desc,
       direction, media_item_type
FROM   apps.jtf_ih_activities_vl
WHERE  interaction_id = :p_interaction_id
ORDER  BY start_date_time;

SELECT resource_name, direction, COUNT(*) activity_count
FROM   apps.jtf_ih_activities_vl
WHERE  start_date_time BETWEEN :p_from AND :p_to
GROUP  BY resource_name, direction
ORDER  BY activity_count DESC;

In both patterns the view serves as a reporting layer over the CRM Foundation interaction history model, allowing consumers to avoid direct dependency on JTF_IH_ACTIVITIES and its satellite tables.