Search Results script_type_code

Overview

AS_SCRIPT_ACT_ANS_DISTINCT_V is a reporting view in the Oracle E-Business Suite Sales Foundation (AS) module. Its documented description is "Distinct actual answers view," and it exposes a de-normalized, distinct projection of data captured by Oracle Scripting when agents record answers against a script during a customer interaction. The view flattens the relationship between an actual script answer, the promotion (script) definition it belongs to, the interaction that produced it, and the resource to whom that interaction was assigned. This makes the object suitable for operational reporting, downstream data warehouse extraction, and integration queries that need one row per unique combination of script, code, interaction, and customer context.

The view is especially relevant to the script_type lookup, since one of its key columns resolves the SCRIPT_TYPE lookup code into a descriptive meaning through AS_LOOKUPS. Because the view text applies SELECT DISTINCT, duplicate answer rows captured within a single interaction are collapsed, so consumers see a single logical record per distinct answer context.

Underlying Base Objects

The ETRM metadata notes that the object is "not implemented in this database" and that no base objects are formally documented for the 12.2.2 repository entry. The supplied view text nevertheless defines the object over the following Sales Foundation and shared reference tables:

• AS_SCRIPT_ACTUAL_ANSWERS (AA) — the transactional source of recorded script answers, keyed by SCRIPT_ID and INTERACTION_ID.
• AS_PROMOTIONS (PROM) — the script/promotion definition; joined on AA.SCRIPT_ID = PROM.PROMOTION_ID and providing SCRIPT_TYPE, CODE, and NAME.
• AS_TODO_LISTS (INT) — the interaction/work item record, joined on AA.INTERACTION_ID = INT.TODO_ID, supplying TODO_ID and CREATION_DATE.
• PER_ALL_PEOPLE_F (PER) — the assignee, joined on INT.ASSIGN_TO_PERSON_ID = PER.PERSON_ID and filtered to the currently effective person row using TRUNC(SYSDATE) between the effective dates.
• AS_LOOKUPS (ASLKP) — the lookup that translates SCRIPT_TYPE into a meaning, filtered to LOOKUP_TYPE = 'SCRIPT_TYPE'.

Key Columns

• SCRIPT_ID / SCRIPT_CODE / SCRIPT_NAME — identifier, code, and name of the script (promotion) against which the answer was recorded.
• SCRIPT_TYPE_CODE / SCRIPT_TYPE — the script type lookup code and its translated meaning from AS_LOOKUPS; central to filtering by script category.
• INTERACTION_ID / INTERACTION_DATE — the interaction (TODO_ID) and its creation date, supporting time-based reporting.
• PERSON_ID / PERSON_FIRST_NAME / PERSON_LAST_NAME — the assigned agent or resource for the interaction.
• CUSTOMER_ID / ADDRESS_ID / CONTACT_ID — the customer, address, and contact context of the recorded answer.

Common Use Cases and Queries

Typical uses include enumerating distinct answers by script type, reporting agent activity, and feeding ETL extracts keyed on script categories.

• Answers by script type:

SELECT SCRIPT_NAME, SCRIPT_TYPE, COUNT(DISTINCT INTERACTION_ID)
FROM   AS_SCRIPT_ACT_ANS_DISTINCT_V
WHERE  SCRIPT_TYPE_CODE = 'SURVEY'
GROUP  BY SCRIPT_NAME, SCRIPT_TYPE;

• Agent activity over a period:

SELECT PERSON_ID, PERSON_LAST_NAME, COUNT(*)
FROM   AS_SCRIPT_ACT_ANS_DISTINCT_V
WHERE  INTERACTION_DATE BETWEEN :from_date AND :to_date
GROUP  BY PERSON_ID, PERSON_LAST_NAME;

Because the view is distinct and joins effective-dated PER_ALL_PEOPLE_F to SYSDATE, results reflect only currently active assignees and unique answer contexts.