Results for “script_type”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AST_AGENT_SCRIPTS_V view is an Oracle E-Business Suite database object owned by the APPS schema within the AST — TeleSales product family. It presents a denormalized, reporting-friendly representation of telemarketing agent scripts deployed through Oracle's Scripting engine. The view consolidates script definition attributes from the underlying deployed-scripts table with human-readable language descriptions and the identity of the user who created each script. This design makes it suitable for operational reporting, integration feeds, administrative auditing, and for any downstream application that needs to enumerate agent scripts without joining raw base tables manually.

The view carries a status of VALID and is documented in the ETRM metadata for both EBS 12.1.1 and 12.2.2. Because the view absorbs the join logic across deployment, language, user, and person entities, it exposes a stable, flattened result set — a key advantage for custom reports, concurrent programs, and OBIEE or BI Publisher data models that consume TeleSales metadata.

Underlying Base Objects

The view is defined over four documented base objects. The primary driving object is IES_DEPLOYED_SCRIPTS, which holds the authoritative script definition rows, including language, activation status, and script type. Referenced as a synonym, it supplies nearly every column projected by the view.

The join to FND_LANGUAGES_VL is a standard (non-outer) join, so any script whose DSCRIPT_LANG_ID does not resolve to a defined language will be excluded from the result set. The creator joins are outer joins (indicated by the (+) operator), ensuring scripts remain visible even when the creating user or associated person record is unavailable.

Key Columns

  • DSCRIPT_ID — unique identifier for the deployed script; the primary key for downstream joins.
  • ACTIVE_STATUS — decoded from the base numeric value to 'Y' or 'N', indicating whether the script is enabled.
  • DSCRIPT_NAME / DESCRIPTION — the script's display name and descriptive text.
  • DSCRIPT_LANG_ID — the language identifier of the script, matching FND_LANGUAGES_VL.LANGUAGE_ID. This is the column directly implicated by the user's search term and is the join key for language resolution.
  • LANGUAGE_DESCRIPTION / NLS_LANGUAGE — the translated language name and the NLS language code derived from the language view.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE — standard WHO columns for auditing.
  • CREATED_BY_NAME — the full name of the creator resolved via PER_ALL_PEOPLE_F.
  • APPLICATION_ID / FUNCTION_ID / SCRIPT_TYPE — linkage to the owning application and function, and a classification of the script.

Common Use Cases and Queries

Typical scenarios include enumerating all active scripts per language, auditing who authored scripts, and supplying script metadata to integration layers or BI extracts. A sample query listing active English scripts follows:

  • SELECT DSCRIPT_ID, DSCRIPT_NAME, ACTIVE_STATUS, LANGUAGEDESCRIPTION, CREATED_BY_NAME
  • FROM APPS.AST_AGENT_SCRIPTS_V
  • WHERE ACTIVE_STATUS = 'Y'
  • AND NLS_LANGUAGE = 'US';

For language-specific reporting, filter on DSCRIPT_LANG_ID directly, or group by NLS_LANGUAGE to produce script counts per locale. Because the view already resolves the language join, queries referencing DSCRIPT_LANG_ID rarely need to join FND_LANGUAGES_VL again. All queries should be executed against the APPS schema with appropriate TeleSales responsibilities or read-only grants.