Search Results jtf_ih

Overview

The IEU_SH_ACTIVITIES table is a core data object within the Oracle E-Business Suite Interaction Center (iSupport) framework, specifically for releases 12.1.1 and 12.2.2. It functions as a detailed activity log for user sessions within the iSupport application, tracking discrete user interactions or tasks performed during a support session. Its primary role is to provide a granular, auditable history of session activities, which is essential for performance analysis, agent productivity reporting, and understanding customer interaction flows. As indicated by the warning in its metadata, this table is designated for Oracle Internal Use and should only be accessed via standard Oracle Applications programs, not through direct SQL queries in a production environment.

Key Information Stored

The table stores metadata about each logged activity, linking it to a broader session and related entities. Key columns include:

• ACTIVITY_ID: The primary key, uniquely identifying each activity record.
• SESSION_ID: Links the activity to its parent session in the iSupport framework.
• ACTIVITY_TYPE_CODE: A programmatic identifier (e.g., 'CALL', 'EMAIL', 'NOTE') defining the nature of the activity.
• BEGIN_DATE_TIME & END_DATE_TIME: Timestamps capturing the activity's duration.
• MEDIA_ID: A critical foreign key column that references a specific media item in the JTF_IH (Interaction History) schema. This establishes a direct integration point with the broader Oracle TeleService module.
• ACTIVE_FLAG: Indicates whether the activity is currently in progress ('Y') or has been completed ('N').
• COMPLETION_CODE: Categorizes the reason for an activity's completion, sourced from the FND_LOOKUPS table.
• Standard Oracle columns: OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for auditing and data integrity.

Common Use Cases and Queries

This table supports operational and analytical reporting for contact center management. A primary use case is generating detailed agent activity reports to measure handle time and productivity by joining session data. Another is tracing the complete interaction history for a specific customer case by querying activities linked via MEDIA_ID to JTF_IH interactions. While direct querying is discouraged, typical analytical SQL patterns would involve filtering by date ranges and ACTIVE_FLAG, and joining to JTF_IH_MEDIA_SRCS to get interaction details. For example, a report to find completed call activities for a session might filter on ACTIVITY_TYPE_CODE = 'CALL', ACTIVE_FLAG = 'N', and a specific SESSION_ID.

Related Objects

The table's structure and indexes reveal its integration within the EBS architecture. Its most significant relationship is with the JTF_IH schema, as the MEDIA_ID column foreign key references the JTF_IH_MEDIA_SRCS table (or related media tables), linking iSupport activities to the universal interaction history. The ACTIVITY_TYPE_CODE may reference a lookup or base table for activity type definitions. The COMPLETION_CODE column references the FND_LOOKUP_VALUES table for standardized completion reasons. Indexes such as IEU_SH_ACTIVITIES_N1 (on SESSION_ID, ACTIVITY_TYPE_CODE, ACTIVE_FLAG) and IEU_SH_ACTIVITIES_N2 (on MEDIA_ID, ACTIVE_FLAG) are optimized for queries filtering by session state or specific media items, underscoring these common access paths.