Search Results csc_activities_v




Overview
Explore in AI Chat

Overview

CSC_ACTIVITIES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the Customer Care (CSC) product family. Its documented purpose is to expose activities associated with an interaction, drawing its core rows from JTF_IH_ACTIVITIES. The view is part of the Interaction History (JTF_IH) data model and presents a denormalized, human-readable projection of an activity record, resolving foreign keys to interaction, media, outcome, result, reason, action, action item, task, customer account, and object definition data.

Because the view is registered as VALID in the ETRM metadata for both 12.1.1 and 12.2.2, it can be treated as a stable interface for custom reports, concurrent programs, OAF/ADF-based pages, and outbound integrations that need to describe who an interaction was with, through which media it occurred, and what the outcome was. Notably, the view text includes MEDIA.MEDIA_DATA, which corresponds directly to the "media_data" search term: this column carries the payload of the media item (for example, the body of an e-mail or the content of a fax), making the view a common target for queries that inspect interaction content.

Underlying Base Objects

The view is defined over twelve documented base objects, accessed in the APPS schema through synonyms: JTF_IH_ACTIVITIES, JTF_IH_INTERACTIONS, JTF_IH_MEDIA_ITEMS, HZ_PARTIES, HZ_CUST_ACCOUNTS, JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, JTF_IH_REASONS_TL, JTF_IH_ACTION_ITEMS_TL, JTF_IH_ACTIONS_TL, JTF_TASKS_B, and JTF_OBJECTS_B.

JTF_IH_ACTIVITIES is the driving table and supplies the activity-level attributes: ACTIVITY_ID, INTERACTION_ID, MEDIA_ID, START_DATE_TIME, END_DATE_TIME, DURATION, DESCRIPTION, ROLE, OUTCOME_ID, RESULT_ID, REASON_ID, ACTION_ITEM_ID, ACTION_ID, OBJECT_ID, OBJECT_TYPE, SOURCE_CODE, and the standard WHO/audit columns. JTF_IH_INTERACTIONS links the activity to its parent interaction via INTERACTION_ID and provides PARTY_ID, which in turn joins to HZ_PARTIES for PARTY_NAME. JTF_IH_MEDIA_ITEMS is joined on MEDIA_ID to yield DIRECTION, MEDIA_ITEM_TYPE, and MEDIA_DATA.

The lookup tables JTF_IH_OUTCOMES_TL, JTF_IH_RESULTS_TL, and JTF_IH_REASONS_TL are outer-joined and constrained by USERENV('LANG'), supplying code and short-description pairs in the session language. JTF_IH_ACTION_ITEMS_TL and JTF_IH_ACTIONS_TL are inner-joined on language to provide ACTION_ITEM and ACTION descriptions. HZ_CUST_ACCOUNTS is outer-joined on CUST_ACCOUNT_ID to return ACCOUNT_NUMBER, while JTF_TASKS_B, JTF_OBJECTS_B, and remaining detail provide task and object-definition context.

Key Columns

  • ROW_ID — the JTF_IH_ACTIVITIES ROWID, useful for updates or drill-back.
  • ACTIVITY_ID / INTERACTION_ID — primary identifiers for the activity and its parent interaction.
  • PARTY_ID / PARTY_NAME — the party involved in the interaction and its display name.
  • MEDIA_ID, DIRECTION, MEDIA_ITEM_TYPE, MEDIADIRTYPE, MEDIA_DATA — media item identifiers, inbound/outbound direction, media classification, the concatenated direction-plus-type descriptor, and the actual media content.
  • START_DATE_TIME / END_DATE_TIME / DURATION — temporal attributes of the activity.
  • OUTCOME_CODE / OUT_DESC, RESULT_CODE / RSL_DESC, REASON_CODE / REA_DESC — language-specific lookup values describing the activity result.
  • ACTION_ITEM, ACTION_ITEM_DESC, ACTION, ACTION_DESC, ACTITM — action-detail columns, with ACTITM concatenating item and action.
  • OBJECT_ID, OBJECT_TYPE, OBJECT_FUNCTION, OBJECT_PARAMETERS — the business object the activity references.
  • CUST_ACCOUNT_ID, ACCOUNT_NUMBER — customer account context.
  • DESCRIPTION, ROLE, TASK_ID, DOC_ID, DOC_REF, DOC_SOURCE_OBJECT_NAME, SOURCE_CODE, SOURCE_CODE_ID, INTERACTION_ACTION_TYPE, OBJECT_VERSION_NUMBER — supporting attributes for classification and navigation.

Common Use Cases and Queries

Typical uses include interaction-history reporting, customer-service dashboards, and integrations that export activity detail. Because lookups are resolved in the session language, the view is well suited to localized reporting.

Retrieving media content for an interaction:

  • SELECT activity_id, party_name, direction, media_item_type, media_data
  • FROM csc_activities_v
  • WHERE interaction_id = :p_interaction_id;

Summarizing activity counts by outcome for a period:

  • SELECT outcome_code, COUNT(*)
  • FROM csc_activities_v
  • WHERE start_date_time BETWEEN :p_from AND :p_to
  • GROUP BY outcome_code;

Joining to customer accounts for account-level service analysis:

  • SELECT account_number, activity_id, role, action_item_desc
  • FROM csc_activities_v
  • WHERE cust_account_id = :p_account_id
  • ORDER BY start_date_time DESC;

Searches referencing "media_data" should target the MEDIA_DATA column, which is sourced from JTF_IH_MEDIA_ITEMS via an outer join, so rows without an associated media item will return NULL.