Search Results script_trans_id

Overview

AST_SUSPENDED_SCRIPTS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the AST (TeleSales) product family and carries a VALID status in the ETRM metadata. The view surfaces telemarketing script transactions that were suspended in mid-execution by an agent, providing a consolidated, read-oriented projection of script, panel, language, agent, resource, and party context inferred from the underlying IES and JTF interaction tables.

Because suspended scripts represent incomplete or interrupted guided-selling flows, the view is chiefly used for operational monitoring, agent coaching, and supervisory dashboards. Rather than requiring report authors to reconstruct the multi-table join logic across the interaction, activity, transaction, segment, and panel data structures, the view encapsulates that logic and delivers a denormalized result set. This makes it well suited for both ad hoc reporting in tools such as Oracle Reports, BI Publisher, and Discoverer, and for downstream integration extracts where suspended-script activity must be captured as a discrete event.

Underlying Base Objects

The view is defined over eight base objects, all resolved through APPS 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 IES objects supply the script deployment, panel, transaction, and segment detail, while the JTF objects provide the interaction, activity, and resource context.

The join chain links IES_TRANSACTIONS to IES_DEPLOYED_SCRIPTS on DSCRIPT_ID, to FND_LANGUAGES on DSCRIPT_LANG_ID, and to IES_TRANS_SEGMENTS on TRANSACTION_ID. IES_PANELS is joined to IES_PANEL_DATA on PANEL_ID, with the panel data tied back to the transaction. The JTF_IH_ACTIVITIES table bridges to JTF_IH_INTERACTIONS on INTERACTION_ID and to the transaction on SCRIPT_TRANS_ID. JTF_RS_RESOURCE_EXTNS is joined to IES_TRANS_SEGMENTS on USER_ID = CREATED_BY.

Suspension is isolated by correlated subqueries that restrict rows to the latest segment, the latest panel sequence number, and the maximum suspended activity. A STATUS filter on IES_TRANSACTIONS (= 1) and an ACTION_ID filter (= 23) further constrain the population to genuine suspension events.

Key Columns

• SCRIPT_NAME — Name of the deployed script (DSCRIPT_NAME) that was suspended.
• PANEL_NAME — Panel within the script where suspension occurred, from IES_PANELS.
• SCRIPT_LANGUAGE / SCRIPT_LANGUAGE_ID — Language of the script, derived from FND_LANGUAGES via LANGUAGE_ID.
• SUSPENDED_TIME — Timestamp of the suspension, sourced from IES_TRANS_SEGMENTS.END_TIME.
• SUSPENDED_BY — Resource name of the agent (SOURCE_NAME) who suspended the script.
• TRANSACTION_ID — Identifier of the IES transaction associated with the script run.
• SCRIPT_ID — Deployed script identifier.
• AGENT_ID — Resource identifier (RESOURCE_ID) of the suspending agent.
• PARTY_ID — Party identifier of the customer engaged in the interaction.

Common Use Cases and Queries

Supervisors commonly query the view to review suspended scripts by agent over a date range, identifying coaching opportunities or process bottlenecks. Analysts aggregate by SCRIPT_NAME and PANEL_NAME to determine where scripts most frequently stall.

SELECT SCRIPT_NAME, SUSPENDED_BY, PANEL_NAME, SUSPENDED_TIME
FROM   APPS.AST_SUSPENDED_SCRIPTS_V
WHERE  SUSPENDED_TIME >= SYSDATE - 7
ORDER BY SUSPENDED_TIME DESC;

A second frequent pattern counts suspensions per agent:

SELECT SUSPENDED_BY, COUNT(*) SUSPENSIONS
FROM   APPS.AST_SUSPENDED_SCRIPTS_V
GROUP BY SUSPENDED_BY
ORDER BY SUSPENSIONS DESC;

Joining to customer or resource master data via AGENT_ID or PARTY_ID extends the view for integration extracts. All queries should respect the view's read-only, reporting-oriented nature and standard EBS security conventions.