Search Results ast_avail_scripts_v




Overview
Explore in AI Chat

Overview

AST_AVAIL_SCRIPTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AST (TeleSales) product family. The view exposes the set of TeleSales scripts that are currently available for use — that is, deployed scripts whose active status flag indicates they are enabled. It serves as a filtered, human-readable presentation layer over the underlying deployment table, resolving internal language identifiers into meaningful NLS language names.

The object carries a VALID status in the ETRM repository and is referenced across both Oracle EBS 12.1.1 and 12.2.2 environments using the same APPS ownership and definition. Because it is a view rather than a table, it stores no data of its own; every query is resolved against its base objects at runtime, which guarantees that consumers always observe the current deployment state of TeleSales scripts.

The view is relevant to the search term "ies_deployed_scripts" because that object is one of its two underlying sources. Administrators and developers investigating deployed script records typically encounter this view as the supported, filtered access path to that base table.

Underlying Base Objects

The documented definition of AST_AVAIL_SCRIPTS_V references exactly two base objects, both accessed through APPS synonyms:

  • IES_DEPLOYED_SCRIPTS — the primary source of script deployment records, supplying the script identifier, script name, language identifier, and the active status flag used for filtering.
  • FND_LANGUAGES — the Oracle Application Object Library language repository, joined to translate the numeric language identifier into the installed NLS language code.

The join condition is I.DSCRIPT_LANG_ID = F.LANGUAGE_ID, an equality join on the language identifier. A single-row filter, I.ACTIVE_STATUS = 1, restricts the result set to scripts flagged as active, excluding inactive or retired deployments. No outer joins, aggregation, or grouping is present, so the view returns one row per active deployed script per language and behaves as a straightforward inner join projection.

Key Columns

The view projects four columns, though the ETRM column listing presents them under names that differ from the base-table aliases used in the view text. The mapping is as follows:

  • SCRIPT_ID — the unique identifier of the deployed script, sourced from I.DSCRIPT_ID. This is the primary key value carried forward from IES_DEPLOYED_SCRIPTS.
  • SCRIPT_NAME — the descriptive name of the script, sourced from I.DSCRIPT_NAME, used for display and reporting.
  • SCRIPT_LANGUAGE — the NLS language code obtained from F.NLS_LANGUAGE in FND_LANGUAGES, such as US or FR.
  • SCRIPT_LANGUAGE_ID — the numeric language identifier from I.DSCRIPT_LANG_ID, corresponding to FND_LANGUAGES.LANGUAGE_ID.

Collectively these columns let a consumer identify each active script, its display name, and the language in which it is deployed, without needing to join back to the language table manually.

Common Use Cases and Queries

Typical scenarios include validating which TeleSales scripts are live before a campaign, auditing language coverage of deployed scripts, and feeding script metadata into custom reports or integrations. Because the active-status filter is embedded in the view, callers do not need to re-implement it.

To list all available scripts across languages:

SELECT script_id, script_name, script_language, script_language_id
FROM   apps.ast_avail_scripts_v
ORDER BY script_name, script_language;

To confirm coverage for a single installed language, for example US English:

SELECT script_id, script_name
FROM   apps.ast_avail_scripts_v
WHERE  script_language = 'US';

To count active scripts per language for audit purposes:

SELECT script_language, COUNT(*) script_count
FROM   apps.ast_avail_scripts_v
GROUP BY script_language
ORDER BY script_language;

When comparisons against inactive deployments are required, users must query the base table IES_DEPLOYED_SCRIPTS directly, since the view intentionally excludes rows where ACTIVE_STATUS is not 1. In all cases, standard APPS schema access and the appropriate responsibility-based grants apply.