Search Results sys_il0000083973c00033

Overview

IES.IES_QUESTION_DATA is a transactional table in the Oracle E-Business Suite Scripting Engine (IES) module. It stores each individual answer collected during execution of a scripted interaction, producing one row per question response. The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and it functions as the persistent record of answers tied to a transaction, a question, and an evaluation panel. In Oracle EBS 12.1.1 and 12.2.2, this object remains VALID and carries FND Design Data registered under IES.IES_QUESTION_DATA.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classification as a link table. It connects a transaction, a question, an optional lookup, an answer definition, and an optional panel into a single association, rather than acting as a standalone hub or a descriptive satellite of one parent.

Key Information Stored

The surrogate primary key is QUESTION_DATA_ID, defined by IES_QUESTION_DATA_PK. The table declares 33 columns in the documented ETRM 12.2.2 schema. The most significant columns are:

• QUESTION_DATA_ID — unique identifier for the answer record (primary key).
• TRANSACTION_ID — foreign key to IES_TRANSACTIONS; binds the answer to a scripting run.
• QUESTION_ID — foreign key to IES_QUESTIONS; identifies which question was answered.
• ANSWER_ID — foreign key to IES_ANSWERS; populated when the response maps to a defined answer.
• LOOKUP_ID — foreign key to IES_LOOKUPS; populated when the answer was associated with a lookup choice.
• FREEFORM_STRING — VARCHAR2(4000); holds the answer value as a string when no lookup choice applies.
• FREEFORM_INT — numeric freeform value (noted as not currently used).
• FREEFORM_DATE — date-typed freeform capture.
• FREEFORM_LONG — extended freeform storage.
• PANEL_DATA_ID — foreign key to IES_PANEL_DATA; associates the answer with a panel data record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; supports multi-tenant data segregation.
• OBJECT_VERSION_NUMBER — concurrency control for row locking.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — DFF-enabled descriptive flexfield segments.

No business-key unique index is documented beyond the surrogate key and the LOB index SYS_IL0000083973C00033$$ (UNIQUE, associated with the FREEFORM_LONG LOB). Six non-unique indexes — N1 through N6 — accelerate lookups on TRANSACTION_ID, ANSWER_ID, QUESTION_ID, LOOKUP_ID, QUESTION_DATA_ID, and PANEL_DATA_ID.

Common Use Cases and Queries

Typical usage includes auditing questionnaire responses, reporting on scripted interactions, and extracting answers for downstream analytics. Joining to IES_TRANSACTIONS and IES_QUESTIONS is fundamental. A representative pattern:

SELECT qd.QUESTION_DATA_ID, qd.TRANSACTION_ID,
       q.QUESTION_TEXT, qd.ANSWER_ID, qd.FREEFORM_STRING
FROM   IES.IES_QUESTION_DATA qd,
       IES.IES_QUESTIONS q
WHERE  qd.QUESTION_ID = q.QUESTION_ID
AND    qd.TRANSACTION_ID = :p_transaction_id;

Because the table is indexed by TRANSACTION_ID (N1), by QUESTION_ID (N3), and by ANSWER_ID (N2), these are the preferred predicates for performance-sensitive queries. Reports frequently pivot freeform answers against lookups, using LOOKUP_ID (N4) to resolve coded choices and FREEFORM_STRING otherwise. Security-derived reporting should always constrain by SECURITY_GROUP_ID when operating in a multi-org or partitioned deployment.

Related Objects

The documented foreign-key relationships anchor this object to the following primary dependencies:

• IES_TRANSACTIONS — via TRANSACTION_ID; the parent scripting transaction.
• IES_QUESTIONS — via QUESTION_ID; defines the question answered.
• IES_ANSWERS — via ANSWER_ID; resolves predefined answers.
• IES_LOOKUPS — via LOOKUP_ID; resolves coded lookup responses.
• IES_PANEL_DATA — via PANEL_DATA_ID; links the answer to its panel record.
• FND_SECURITY_GROUPS — via SECURITY_GROUP_ID; enforces data security.

These six parents constitute the immediate referential neighborhood of IES_QUESTION_DATA and drive nearly all reporting joins and API interactions involving collected script answers.