Search Results ies_question_data_pk

Overview

IES_QUESTION_DATA is a transactional table in the Oracle E-Business Suite IES (Scripting) module, owned by the IES schema. As documented in the ETRM metadata, its purpose is to store all answers collected by the Scripting Engine. The Scripting Engine drives interactive, question-and-answer workflows used by Oracle's telemarketing, telesales, and customer interaction products, where agents or self-service flows progress through scripted panels of questions. Every response captured against a scripted question — whether selected from a predefined answer list, entered as freeform text, a numeric value, a date, or a long text value — is persisted in this table as a single row keyed to a specific transaction, question, and panel context.

From a dimensional modeling perspective, the ETRM heuristic classification for this object is link. This reflects its role as an associative structure that connects a transaction, a question, an answer, and a lookup value — a many-to-many resolution point between the Scripting Engine's master definitions (questions, answers, lookups) and its runtime execution records (transactions, panel data). This classification is a modeling suggestion derived from the foreign key topology rather than a mandatory design constraint.

Key Information Stored

The table contains 33 documented columns. The most significant are:

• QUESTION_DATA_ID — the surrogate primary key, enforced by the IES_QUESTION_DATA_PK unique index. No separate business-key unique index is documented beyond the LOB index (SYS_IL0000083973C00033$$) associated with the FREEFORM_LONG column.
• TRANSACTION_ID — foreign key to IES_TRANSACTIONS; identifies the scripting session or transaction under which the answer was captured.
• QUESTION_ID — foreign key to IES_QUESTIONS; identifies which scripted question was answered.
• ANSWER_ID — foreign key to IES_ANSWERS; identifies the predefined answer chosen, where the question presents a coded answer list.
• LOOKUP_ID — foreign key to IES_LOOKUPS; supports lookup-driven response values.
• PANEL_DATA_ID — foreign key to IES_PANEL_DATA; ties the answer to the specific panel instance rendered during the script.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-org / security group partitioning.
• FREEFORM_STRING, FREEFORM_INT, FREEFORM_DATE, FREEFORM_LONG — typed freeform response columns holding text, numeric, date, and long-text answers respectively.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS flexfield-style descriptive columns reserved for extension and customer-specific data.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER — standard auditing and optimistic locking columns.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing the complete answer set for a scripting transaction, analyzing which questions were answered with which predefined answers, and extracting freeform responses for downstream processing. A representative query joins answers back to their questions and transactions:

• Reconstruct a full script response set: SELECT qd.QUESTION_DATA_ID, q.QUESTION_TEXT, qd.ANSWER_ID, qd.FREEFORM_STRING, qd.FREEFORM_DATE FROM IES_QUESTION_DATA qd, IES_QUESTIONS q WHERE qd.QUESTION_ID = q.QUESTION_ID AND qd.TRANSACTION_ID = :transaction_id;
• Answer distribution analysis: group by QUESTION_ID and ANSWER_ID to profile response frequencies across transactions.
• Freeform extraction: filter on FREEFORM_STRING IS NOT NULL or FREEFORM_LONG IS NOT NULL to isolate unstructured agent or customer input.
• Security-scoped reporting: constrain results by SECURITY_GROUP_ID to honor multi-org data access rules.

Related Objects

• IES_TRANSACTIONS — joined via IES_QUESTION_DATA.TRANSACTION_ID; the parent session record.
• IES_QUESTIONS — joined via IES_QUESTION_DATA.QUESTION_ID; the question definition.
• IES_ANSWERS — joined via IES_QUESTION_DATA.ANSWER_ID; the predefined answer definition.
• IES_LOOKUPS — joined via IES_QUESTION_DATA.LOOKUP_ID; lookup value source.
• IES_PANEL_DATA — joined via IES_QUESTION_DATA.PANEL_DATA_ID; the panel instance containing the question.
• FND_SECURITY_GROUPS — joined via IES_QUESTION_DATA.SECURITY_GROUP_ID; security partitioning.