Search Results as_script_actual_answers_n3

Overview

The OSM.AS_SCRIPT_ACTUAL_ANSWERS table is a transactional data object within the Oracle EBS TeleService and Interaction Center (OSM) schema. It stores the answers captured against a scripted interaction, recording which predefined answer was selected in response to a script question during a customer or agent interaction. The table acts as the persistent ledger of scripted responses, linking an interaction to the script, questions, predefined answers, and the associated customer, address, and contact context.

From a Data Vault modeling perspective, the ETRM heuristic classification identifies this object as a link. This suggests it functions as an associative table resolving the many-to-many relationships between interactions, script questions, predefined answers, and customer party data. The table resides in the APPS_TS_ARCHIVE tablespace with PCT FREE 10, indicating it is expected to grow continuously as interactions are processed and is optimized for high-volume insert activity.

Key Information Stored

The table is defined with 38 columns in the documented 12.2.2 physical schema. The most significant columns are:

• SCRIPT_ACTUAL_ANSWER_ID — The surrogate primary key, enforced by the unique index AS_SCRIPT_ACTUAL_ANSWERS_U1 and the constraint AS_SCR_ACT_ANSWERS_PK. Uniquely identifies each captured answer.
• INTERACTION_ID and PRE_DEF_ANSWER_ID — Together form the business-key candidate AS_SCRIPT_ACTUAL_ANSWERS_U2, a unique index ensuring that a given predefined answer is recorded only once per interaction.
• SCRIPT_ID — Identifies the script that was presented, referencing JTF_IH_SCRIPTS.
• QUESTION_ID — The script question that was answered, referencing AS_SCRIPT_QUESTIONS.
• PRE_DEF_ANSWER_ID — The predefined answer selected from AS_SCRIPT_PRE_DEFINED_ANSWERS.
• CUSTOMER_ID, ADDRESS_ID, CONTACT_ID — Customer party context, identifying the customer, site address, and contact associated with the interaction.
• COMMENTS — Free-text notes captured alongside the answer (up to 2000 characters).
• STATUS_CODE — Workflow or processing status of the recorded answer.
• EVENT_OFFERING_ID, CALL_PROMOTION_ID, MAIL_PROMOTION_ID — Links to the campaign or offering context in which the script was executed.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield columns for extensible, context-sensitive attributes.
• Who-columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, plus the concurrent program audit columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage centers on scripted-interaction reporting: which answers were captured, by which agents, for which customers, and how those answers tie into campaign or promotional outcomes. A common query pattern joins the table to JTF_IH_SCRIPTS and AS_SCRIPT_QUESTIONS to reconstruct the question-and-answer dialogue for an interaction:

• Retrieving all answers for an interaction: SELECT * FROM OSM.AS_SCRIPT_ACTUAL_ANSWERS WHERE INTERACTION_ID = :interaction_id, which leverages the AS_SCRIPT_ACTUAL_ANSWERS_N1 index on (INTERACTION_ID, SCRIPT_ID).
• Locating answers by customer and site: filtering on CUSTOMER_ID and ADDRESS_ID using index AS_SCRIPT_ACTUAL_ANSWERS_N2.
• Contact-level response history: querying by CONTACT_ID via AS_SCRIPT_ACTUAL_ANSWERS_N3.
• Status-driven operational reporting: using AS_SCRIPT_ACTUAL_ANSWERS_N4 on STATUS_CODE to find incomplete or pending answers.

Reporting models commonly resolve the flexfield attributes ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 through the descriptive flexfield views, and join to RA_CUSTOMERS and RA_SITE_USES_ALL to enrich answers with customer and site attributes.

Related Objects

The documented foreign-key relationships identify the following key dependencies:

• JTF_IH_SCRIPTS — joined via SCRIPT_ID; the parent script definition.
• AS_SCRIPT_QUESTIONS — joined via QUESTION_ID; the question answered.
• AS_SCRIPT_PRE_DEFINED_ANSWERS — joined via PRE_DEF_ANSWER_ID; the predefined answer chosen.
• RA_CUSTOMERS — joined via CUSTOMER_ID; the customer party.
• RA_SITE_USES_ALL — joined via ADDRESS_ID; the customer site.
• Contact reference — CONTACT_ID resolves against the contact entity, though the target table is not fully qualified in the metadata.

Because this is a link-style transactional table, it is generally consumed through the interaction and script APIs rather than updated directly, and it participates in the broader OSM TeleService interaction model alongside these parent definition tables.