Search Results jtf_ih_scripts




Overview
Explore in AI Chat

Overview

JTF_IH_SCRIPTS is a table owned by the JTF schema within the CRM Foundation product family in Oracle E-Business Suite. It is defined in the Call Center schema and serves as the master repository for call center scripting definitions. In the context of Oracle EBS 12.1.1 and 12.2.2, this object holds the top-level script records that drive agent-facing interaction flows within the Interaction History and Telephony/Call Center framework.

From a Data Vault modeling perspective, the ETRM relationship metadata suggests a hub-leaning classification. The table carries a single-column surrogate primary key (SCRIPT_ID) and is referenced by multiple downstream tables, which is characteristic of a hub entity in a Data Vault model. Its modest column count and its absence of foreign-key dependencies beyond the security group reference reinforce that it functions primarily as a reference or master entity rather than as a transactional or link table.

Key Information Stored

The table is documented with nine columns. The most important are summarized below.

  • SCRIPT_ID — The surrogate primary key, enforced through JTF_IH_SCRIPTS_PK. A unique index (JTF_IH_SCRIPTS_U1) also exists on this column, making it the primary business-key candidate and the join point for all dependent tables.
  • OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle Application Framework to detect concurrent updates to script definitions.
  • CREATED_BY, CREATION_DATE — Standard WHO columns recording the user and timestamp of initial record creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login session responsible for it.
  • SECURITY_GROUP_ID — Foreign key reference to FND_SECURITY_GROUPS, enforcing multi-org and data-security partitioning.
  • SCR_ACTIVITY_ID — Identifies the scripting activity associated with the script record, tying the script to its operational context.

Common Use Cases and Queries

The principal use cases involve reporting on active scripts, resolving script references in interaction history, and reconciling call center activity. Typical queries include joining JTF_IH_SCRIPTS to JTF_IH_INTERACTIONS to attribute interactions to their originating script.

  • Listing all scripts for a given security group: SELECT SCRIPT_ID, SCR_ACTIVITY_ID FROM JTF.JTF_IH_SCRIPTS WHERE SECURITY_GROUP_ID = :org_id;
  • Resolving interaction-to-script relationships: SELECT i.INTERACTION_ID, s.SCRIPT_ID FROM JTF_IH_INTERACTIONS i JOIN JTF_IH_SCRIPTS s ON i.SCRIPT_ID = s.SCRIPT_ID;
  • Auditing recently modified scripts using LAST_UPDATE_DATE for governance and change tracking.
  • Feeding BI Publisher or OBIEE dashboards that measure script utilization across call center operations.

Related Objects

The following tables reference JTF_IH_SCRIPTS through the SCRIPT_ID column and are the most significant dependencies for integration and reporting.

  • JTF_IH_INTERACTIONS — References SCRIPT_ID; the primary transactional table linking interactions to the scripts that produced them.
  • JTF_IH_INTERACTIONS_STG and JTF_IH_INTERACTIONS_STG_LOG — Staging and logging counterparts carrying the same SCRIPT_ID reference for load and audit processing.
  • BIX_INTERACTIONS and BIX_SUM_INFO — Interaction and summary tables used by CRM interaction analytics.
  • AS_SCRIPT_ACTUAL_ANSWERS — Stores recorded agent responses tied to a script, essential for script compliance reporting.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID to enforce data security.

Collectively these relationships establish JTF_IH_SCRIPTS as the central reference entity for call center scripting in Oracle EBS CRM Foundation.