Search Results suspended_time

Overview

The APPS.AST_SUSPENDED_SCRIPTS_V view exposes detail about deployed scripts that were suspended or left incomplete during an interaction handled through the Oracle TeleSales / TeleService script engine. It joins transactional script data (IES_TRANSACTIONS, IES_DEPLOYED_SCRIPTS, IES_TRANS_SEGMENTS, IES_PANEL_DATA, IES_PANELS) to interaction history (JTF_IH_INTERACTIONS, JTF_IH_ACTIVITIES) so that the most recent activity of a given action (ACTION_ID = 23) and the most recent panel render for a transaction can be reported together. The view is used primarily for operational reporting and troubleshooting of agent-driven script execution, presenting one row per (script, panel, language, segment end-time) combination that satisfies the suspend/completion filter.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented base objects (all resolved through public synonyms): FND_LANGUAGES, IES_DEPLOYED_SCRIPTS, IES_PANELS, IES_PANEL_DATA, IES_TRANSACTIONS, IES_TRANS_SEGMENTS, JTF_IH_ACTIVITIES, JTF_IH_INTERACTIONS, and JTF_RS_RESOURCE_EXTNS. The join path is anchored on IES_TRANSACTIONS (b), which links to the deployed script, the script language, the resource (via CREATED_BY on IES_TRANS_SEGMENTS), the activity record, and the resource extension. Two correlated subqueries restrict the row set to the latest segment_id and the latest sequence_number for a transaction, and to the maximum activity_id for the suspension action, ensuring that only the most current state of a suspended script is returned.

Key Columns

• transaction_id (IES_TRANSACTIONS) – the script transaction identifier; also the join key to activities, segments, and panel data.
• script_trans_id (JTF_IH_ACTIVITIES) – the activity's reference back to the originating script transaction; the predicate a1.script_trans_id IS NOT NULL and action_id = 23 isolate suspend-type activities.
• dscript_name / dscript_id / dscript_lang_id – deployed script definition name, identifier, and language of the script definition.
• panel_name – the panel associated with the most recent IES_PANEL_DATA row for the transaction.
• nls_language – NLS-formatted language name from FND_LANGUAGES.
• end_time – the segment end time from IES_TRANS_SEGMENTS (the created_by user drives the resource link).
• source_name / resource_id – resource extension details for the user who created the segment record.
• party_id – the party associated with the interaction (JTF_IH_INTERACTIONS).

Common Use Cases and Queries

Typical uses include auditing agent script adherence, identifying scripts that were suspended mid-flow, and reconciling script activity with interaction records. A simple filtered query follows:

SELECT transaction_id, dscript_name, panel_name,
       nls_language, source_name, end_time, party_id
  FROM apps.ast_suspended_scripts_v
 WHERE transaction_id = :transaction_id;

To find suspended scripts for a resource over a period, filter on resource_id with the segment end_time range:

SELECT resource_id, dscript_name, panel_name, end_time
  FROM apps.ast_suspended_scripts_v
 WHERE resource_id = :resource_id
   AND end_time BETWEEN :from_date AND :to_date
 ORDER BY end_time DESC;

Because the view already applies the "latest segment" and "latest activity" correlated subqueries, no additional DISTINCT or ranking logic is required. Note that STATUS = 1 filters the transaction set, and performance is assisted by the ORDERED and USE_NL hints in the view definition.