Search Results outbound_script

Overview

The APPS.AST_SOURCE_AVAIL_SCRIPTS_V view exposes the set of deployed interaction scripts that are available for a given source code and language within Oracle EBS 12.1.1 and 12.2.2. It acts as a bridge between the script deployment metadata held in the IES (Intelligent Enterprise Scripting / iScript) repository and the source-code and contact-point definitions maintained in the AMS (Marketing) schema. In practical terms, the view answers the question: "For a particular source code, which inbound or outbound scripts are actively deployed and available, and in which language?"

The view is a read-only reporting and integration object. It is commonly referenced by telephony, CTI, and campaign-management integrations that need to resolve the script name to be launched for a screen-pop or predictive-dialer outbound call. The presence of the contact_point_type IN ('INBOUND_SCRIPT', 'OUTBOUND_SCRIPT') predicate makes it directly relevant to the outbound_script search: outbound-capable scripts are exactly those contact points flagged as OUTBOUND_SCRIPT.

Underlying Base Objects

The view is owned by APPS and is defined over four synonyms that resolve to the following base objects:

• IES_DEPLOYED_SCRIPTS (I) — the script deployment table. Provides DSCRIPT_ID, DSCRIPT_NAME, DSCRIPT_LANG_ID, and the ACTIVE_STATUS flag that filters to only currently deployed scripts (ACTIVE_STATUS = 1).
• FND_LANGUAGES (F) — the language repository. Joined on I.DSCRIPT_LANG_ID = F.LANGUAGE_ID to yield the NLS language code NLS_LANGUAGE.
• AMS_ACT_CONTACT_POINTS (P) — the activity/contact-point definition table. The join I.DSCRIPT_NAME = P.CONTACT_POINT_VALUE links the deployed script name to a configured contact point, and the predicate restricts contact points to type INBOUND_SCRIPT or OUTBOUND_SCRIPT.
• AMS_SOURCE_CODES (A) — the source-code definition table. The two-part join P.ACT_CONTACT_USED_BY_ID = A.SOURCE_CODE_FOR_ID and P.ARC_CONTACT_USED_BY = A.ARC_SOURCE_CODE_FOR ties the contact point to a specific source code, so the view returns the SOURCE_CODE_ID associated with each available script.

Key Columns

• DSCRIPT_ID — surrogate primary key of the deployed script record in IES_DEPLOYED_SCRIPTS.
• DSCRIPT_NAME — the logical script name; the value that must equal CONTACT_POINT_VALUE in AMS_ACT_CONTACT_POINTS.
• DSCRIPT_LANG_ID — language identifier of the deployed script, foreign key to FND_LANGUAGES.
• NLS_LANGUAGE — the two-letter NLS language code (e.g., US) derived from FND_LANGUAGES.
• SOURCE_CODE_ID — the source code against which the script is available; the primary key of AMS_SOURCE_CODES used by the contact point.

Common Use Cases and Queries

Typical usage includes validating that a script referenced by an outbound campaign is actually deployed and active, and resolving the correct script for the language and source code of a contact. A representative query to list all active outbound-available scripts for a source code is:

SELECT script_name,
       source_code_id
FROM   apps.ast_source_avail_scripts_v
WHERE  source_code_id = :p_source_code_id;

To find the script to launch for a specific language, filter on nls_language. To enumerate all deployed scripts regardless of type, join back to AMS_ACT_CONTACT_POINTS or drop the type predicate at a higher level. Where feasible, consider materializing results for high-volume CTI lookups, as the four-table join is not optimized for rapid per-call execution.