Search Results jtf_ih_scripts_u1

Overview

JTF.JTF_IH_SCRIPTS is a base table in the Oracle E-Business Suite Customer Relationship Management (CRM) schema, owned by the JTF (Java Telephony Foundation / Interaction History) product family. It is defined in the Call Center Schema and serves as the master repository for scripts used within the Interaction History and scripting framework. In Oracle EBS 12.1.1 and 12.2.2, this table underpins agent-facing guided scripting, telemarketing, and telesales activities within the Call Center and Advanced Outbound modules.

The table is registered under FND Design Data as JTF.JTF_IH_SCRIPTS and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. It holds a VALID status in the ETRM documentation. Based on the heuristic Data Vault classification mined from the foreign key structure, this object carries a hub-leaning profile: SCRIPT_ID functions as the natural business key and stable identifier, making the table a candidate hub in a Data Vault model. Dimension and audit attributes, including the standard WHO columns and OBJECT_VERSION_NUMBER, would then be modeled as a satellite attached to that hub.

Key Information Stored

The table is defined with nine documented columns. The most significant are:

• SCRIPT_ID (NUMBER(15), mandatory) — the unique surrogate primary key of the table, backed by the primary key constraint JTF_IH_SCRIPTS_PK and the unique index JTF_IH_SCRIPTS_U1 (type NORMAL, UNIQUE, in APPS_TS_TX_IDX). This column is the principal business-key candidate and the anchor for all downstream references.
• SCR_ACTIVITY_ID (NUMBER(15)) — identifies the script activity context to which the script is tied, linking script definitions to activity configuration.
• OBJECT_VERSION_NUMBER (NUMBER(15)) — sequential lock-control counter used when the scripting UI is rendered as HTML; it implements optimistic concurrency for record updates.
• SECURITY_GROUP_ID (NUMBER) — used in hosted environments and referenced through a foreign key to FND_SECURITY_GROUPS, enabling multi-tenant data partitioning.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — the standard Oracle WHO audit columns, capturing user and login identifiers (foreign keys to FND_USER.USER_ID and FND_LOGINS.LOGIN_ID) as well as creation and update timestamps.

No descriptive name, version label, or status column is documented in this metadata, so consumers should treat SCRIPT_ID and SCR_ACTIVITY_ID as the operative identifiers.

Common Use Cases and Queries

Typical usage includes locating scripts by script identifier, reconciling scripting activity against agent interactions, and auditing change history via the WHO columns. A standard single-row lookup pattern is:

• Retrieve all scripts created within a given date range: SELECT SCRIPT_ID, SCR_ACTIVITY_ID, CREATION_DATE FROM JTF.JTF_IH_SCRIPTS WHERE CREATION_DATE >= :p_from_date AND CREATION_DATE < :p_to_date;
• Count interactions per script by joining to the interaction table: SELECT s.SCRIPT_ID, COUNT(i.SCRIPT_ID) FROM JTF.JTF_IH_SCRIPTS s, JTF.JTF_IH_INTERACTIONS i WHERE s.SCRIPT_ID = i.SCRIPT_ID GROUP BY s.SCRIPT_ID;
• Detect stale records updated since a checkpoint: SELECT SCRIPT_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM JTF.JTF_IH_SCRIPTS WHERE LAST_UPDATE_DATE > :p_checkpoint;
• Reconcile summary versus detail scripting data by joining BIX_SUM_INFO or BIX_INTERACTIONS on SCRIPT_ID for business-intelligence reporting.

Because OBJECT_VERSION_NUMBER governs locking, any direct DML should either preserve or correctly increment this value to avoid invalidating HTML-based script screens.

Related Objects

The documented relationships identify the following significant dependents and references:

• JTF_IH_INTERACTIONS — references JTF_IH_SCRIPTS.SCRIPT_ID; the primary interaction detail table, linking each interaction to its driving script.
• JTF_IH_INTERACTIONS_STG and JTF_IH_INTERACTIONS_STG_LOG — staging and staging-log tables that reference SCRIPT_ID, used during interaction import and auditing.
• AS_SCRIPT_ACTUAL_ANSWERS — references SCRIPT_ID and captures agent responses to scripted questions.
• BIX_SUM_INFO and BIX_INTERACTIONS — business intelligence summary and interaction tables that reference SCRIPT_ID for reporting and analytics.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, providing the hosted-environment security grouping for script records.

The JTF_IH_SCRIPTS# object is listed as a dependent of the base table, representing the underlying index-organized or shadow structure used by the schema. Together, these objects position JTF.JTF_IH_SCRIPTS as the central hub for Call Center scripting data in Oracle EBS.