Search Results ast_source_avail_scripts_v

Overview

AST_SOURCE_AVAIL_SCRIPTS_V is an APPS-owned database view within the Oracle E-Business Suite TeleSales (AST) product family. It exposes the set of deployed TeleSales scripts that are available to a given source code, filtered by active status and restricted to inbound and outbound script contact point types. The view serves as a reporting and integration bridge between the script repository held in IES_DEPLOYED_SCRIPTS and the source-code telephone contact-point configuration held in AMS_ACT_CONTACT_POINTS and AMS_SOURCE_CODES, joining both to FND_LANGUAGES for language resolution.

In practice, this view answers the operational question: "Which active scripts in which languages are associated with a given source code?" That makes it useful to TeleSales administrators, contact-center reporting, and any downstream integration that must resolve a script identifier against the source code from which an interaction originated. The view is documented as VALID in the ETRM metadata for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over four referenced base objects, all exposed through APPS synonyms:

• IES_DEPLOYED_SCRIPTS (aliased I) — the primary script repository table, providing the deployed script identifier, name, and language identifier. The view filters on ACTIVE_STATUS = 1, so only live scripts are surfaced.
• FND_LANGUAGES (aliased F) — the language reference table, supplying the NLS language name that corresponds to the script language identifier.
• AMS_ACT_CONTACT_POINTS (aliased P) — the contact-point configuration table, which links a script name to the source code it is used by. The join is made on DSCRIPT_NAME = CONTACT_POINT_VALUE, with the contact point type constrained to 'INBOUND_SCRIPT' or 'OUTBOUND_SCRIPT'.
• AMS_SOURCE_CODES (aliased A) — the source code definition table, providing the source code identifier for the contact point.

Two linkage predicates tie the contact point to the source code: P.ACT_CONTACT_USED_BY_ID = A.SOURCE_CODE_FOR_ID and P.ARC_CONTACT_USED_BY = A.ARC_SOURCE_CODE_FOR. Together these constrain the association to the correct source-code entity. The script-to-language join is I.DSCRIPT_LANG_ID = F.LANGUAGE_ID.

Key Columns

The view projects five columns, mapping the internal DSCRIPT identifiers to a friendlier reporting interface:

• SCRIPT_ID — sourced from I.DSCRIPT_ID; the unique identifier of the deployed script.
• SCRIPT_NAME — sourced from I.DSCRIPT_NAME; the script name, which must match a contact point value to appear in the view.
• SCRIPT_LANGUAGE — sourced from F.NLS_LANGUAGE; the NLS language of the script.
• SCRIPT_LANGUAGE_ID — sourced from I.DSCRIPT_LANG_ID; the numeric language identifier. This is the column most frequently searched, as it is the join key to FND_LANGUAGES and the target of language-filtering predicates.
• SOURCE_CODE_ID — sourced from A.SOURCE_CODE_ID; identifies the source code that the script is available to.

Common Use Cases and Queries

Typical use cases include validating that a newly deployed script is exposed for the intended source code; producing language coverage reports across scripts; and driving integrations or inbound routing that must select an active script based on the calling source code.

List available scripts by language:

• SELECT script_id, script_name, script_language, source_code_id FROM apps.ast_source_avail_scripts_v WHERE script_language_id = :language_id ORDER BY script_name;

List scripts for a specific source code:

• SELECT script_id, script_name, script_language FROM apps.ast_source_avail_scripts_v WHERE source_code_id = :source_code_id;

Group scripts by language to assess coverage:

• SELECT script_language, COUNT(*) FROM apps.ast_source_avail_scripts_v GROUP BY script_language ORDER BY 1;

Because the view restricts results to active scripts and to the two script contact point types, it should be preferred over ad hoc joins to IES_DEPLOYED_SCRIPTS whenever the availability-by-source-code relationship is the reporting objective.