Search Results as_script_answer_actions




Overview
Explore in AI Chat

Overview

The AS_SCRIPT_ANSWER_ACTIONS view belongs to the Oracle E-Business Suite (EBS) AS – Sales Foundation product family, the module that underpins Oracle Sales, Oracle TeleSales, and related customer-facing applications. It exposes the actions that may be triggered in response to a script answer during a guided selling or telemarketing conversation. Scripts in Sales Foundation present a question-and-answer flow to end users; the answer selected can drive one or more follow-up "actions," such as creating a lead, recording interest in a product, assigning a rank, advancing a sales stage, or associating a promotion.

In Oracle EBS 12.1.1 and 12.2.2, this object is documented in ETRM as a multi-org secured view. Its description, "Script answer actions (multi-org)," and the presence of both ORG_ID and ORGANIZATION_ID confirm that records are partitioned by operating unit. The view is not implemented in every database, which is typical for configuration-driven Sales Foundation objects that only appear when the relevant application modules are licensed and installed. From an integration and reporting standpoint, the view provides a stable, security-filtered projection over the underlying answer-action data, allowing queries, concurrent programs, and interfaces to retrieve operating-unit-specific rows without directly accessing the base table.

Underlying Base Objects

The documented view text selects from AS_SCRIPT_ANSWER_ACTIONS_ALL, the multi-org "ALL" table that stores all rows across operating units. The view applies an organization security predicate using USERENV('CLIENT_INFO'), a standard Oracle Applications technique: the first ten characters of the client information string are converted to a number and compared against ORG_ID, with a fallback of -99 when no operating unit context is established.

The affected table follows the Oracle multi-org convention: the _ALL table holds every operating unit's rows, and the corresponding non-suffixed view restricts them to the session's current organization. No additional referenced base objects are documented in the ETRM metadata. The view inherits the standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) from the base table and also exposes the fifteen descriptive flexfield columns ATTRIBUTE_CATEGORY through ATTRIBUTE15.

Key Columns

Common Use Cases and Queries

Typical uses include auditing the actions configured against script answers, verifying promotion and lead-generation rules, and joining to script definition tables to trace how an answer drives downstream behavior.

  • List all actions for a given predefined answer: 
    SELECT SCRIPT_ANSWER_ACTION_ID, TYPE, LEAD_NAME, RANK
FROM   AS_SCRIPT_ANSWER_ACTIONS
WHERE  PRE_DEF_ANSWER_ID = :answer_id;
  • Retrieve promotion-driven actions: 
    SELECT SCRIPT_ANSWER_ACTION_ID, PROMOTION_ID, CALL_PROMOTION_ID
FROM   AS_SCRIPT_ANSWER_ACTIONS
WHERE  PROMOTION_ID IS NOT NULL;
  • Audit recent changes: 
    SELECT SCRIPT_ANSWER_ACTION_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE
FROM   AS_SCRIPT_ANSWER_ACTIONS
ORDER BY LAST_UPDATE_DATE DESC;

Because the view enforces operating unit security automatically, queries return only rows visible to the current organization context, making it the preferred access point over the _ALL table for reporting and integration.