Search Results script_language




Overview
Explore in AI Chat

Overview

APPS.AST_AVAIL_SCRIPTS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data identifier AST.AST_AVAIL_SCRIPTS_V. It exposes the set of scripts that are available and deployed for use within the Oracle Scripting (AST) module, joined to language information so that consumers can identify which language each script belongs to. The view carries a Status of VALID and is classified as an Internal view type. As with most ETRM-documented AST objects, it is flagged Oracle Internal Use Only: Oracle does not support direct access to applications data through this object except from standard Oracle Applications programs. It is therefore best understood as an internal read interface used by Oracle Scripting runtime and setup components rather than as a public API surface. Searches for the column name script_language_id typically arise from developers mapping language-aware script lookups, since that column is the numeric foreign key tying a script to a specific installed language.

Underlying Base Objects

The view is defined over two base objects, both resolved through APPS synonyms:

  • IES_DEPLOYED_SCRIPTS — the driving table, holding script definitions that have been deployed. AST (Oracle Scripting) shares the IES schema prefix with its underlying deployed-script and interaction entities.
  • FND_LANGUAGES — the EBS language repository, supplying the language identifier and language code used to resolve script_language and script_language_id.

The ETRM dependency report shows AST_AVAIL_SCRIPTS_V referencing APPS, FND_LANGUAGES, and IES_DEPLOYED_SCRIPTS, and confirms that no database object references the view itself. It is a terminal, read-only dependency leaf, meaning changes to the underlying tables propagate to the view without downstream columnar impact on other compiled objects.

Key Columns

The view exposes exactly four documented columns:

  • SCRIPT_ID (NUMBER) — the unique identifier of the deployed script; the primary lookup key.
  • SCRIPT_NAME (VARCHAR2, length 256) — the descriptive name of the script as presented to users.
  • SCRIPT_LANGUAGE (VARCHAR2, length 30) — the language code or description associated with the script, resolved from FND_LANGUAGES.
  • SCRIPT_LANGUAGE_ID (NUMBER) — the numeric language identifier corresponding to an FND_LANGUAGES row; this is the column most often searched, as it enables joins to language-dependent reference data and filtering by installed language.

Common Use Cases and Queries

The view is used to enumerate deployed scripts alongside their language assignments, typically to drive selection lists in Oracle Scripting configuration or to validate that a script exists for a given language before an interaction is launched. A representative query retrieving all available scripts is shown in the ETRM query text and remains the canonical access pattern:

  • SELECT SCRIPT_ID, SCRIPT_NAME, SCRIPT_LANGUAGE, SCRIPT_LANGUAGE_ID FROM APPS.AST_AVAIL_SCRIPTS_V;
  • Filtering by language: add WHERE SCRIPT_LANGUAGE_ID = :language_id to restrict results to one installed language.
  • Lookup by identity: add WHERE SCRIPT_ID = :script_id to return a single deployed script with its language attributes.
  • Joining to FND_LANGUAGES via SCRIPT_LANGUAGE_ID where additional language metadata is required beyond the code exposed here.

Because the view is internally scoped, custom queries should be treated as diagnostic or reporting aids only. Production logic should rely on Oracle-provided Scripting programs, and any direct querying should be confined to read-only statements against the view's documented columns.