Search Results ies_svy_responses




Overview
Explore in AI Chat

Overview

The IES_SVY_RESPONSES table resides in the IES schema and belongs to the IES - Scripting product family within Oracle E-Business Suite (available in 12.1.1 and 12.2.2). It stores individual survey responses captured against survey questions and cycles, functioning as the transactional store for IES survey functionality. Each row represents a single answer recorded for a question during a survey cycle, linked to the interaction or transaction that spawned it. Column RESPONSE_MEDIA_TYPE and DEPLOYMENT_MEDIA_TYPE describe how the response was collected (for example, by web, telephony, or agent-entered channels).

From a heuristic Data Vault modeling perspective, ETRM classifies this table as standalone, meaning it is not strongly integrated into a broader hub-link-satellite graph. Where modeled, it would most naturally behave as a satellite capturing survey response detail, with the composite primary key (SURVEY_QUES_ANS_ID, SURVEY_CYCLE_ID, TRANSACTION_ID) behaving like a degenerate link key.

The table is owned by IES and is marked VALID in the ETRM metadata. It carries 30 documented columns in the 12.2.2 physical schema.

Key Information Stored

  • SURVEY_QUES_ANS_ID — identifies the survey question/answer pair being responded to. Part of the composite primary key.
  • SURVEY_CYCLE_ID — identifies the survey cycle under which the response was captured. Part of the primary key.
  • TRANSACTION_ID — links the response to the originating transaction. Part of the primary key.
  • RESPONSE_ID — surrogate identifier for the response record itself.
  • LIST_ENTRY_ID — foreign key to AS_LIST_ENTRIES; holds the selected list value when the answer is a pick-list entry.
  • FREEFORM_STRING, FREEFORM_INT, FREEFORM_DATE — typed free-form answer values for open-ended questions.
  • INTERACTION_ID — links the response to an interaction record in Interaction Center contexts.
  • DEPLOYMENT_MEDIA_TYPE, RESPONSE_MEDIA_TYPE — channel descriptors for the survey delivery and capture.
  • EXISTENCE — flag indicating presence or conditional applicability of the response.
  • F_DELETEDFLAG — soft-delete marker.
  • SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing multi-org / data security partitioning.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle EBS DFF (descriptive flexfield) columns for extensibility.

The primary key index (IES_SVY_RESPONSES_PK) is composite on SURVEY_QUES_ANS_ID, SURVEY_CYCLE_ID, and TRANSACTION_ID; there is no documented single-column business key, so RESPONSE_ID remains a candidate surrogate for joins and lookups.

Common Use Cases and Queries

Typical usage centers on reporting and analysis of survey outcomes: aggregating responses per question, measuring completion rates per cycle, or analyzing channel split via RESPONSE_MEDIA_TYPE. A common query pattern joins list-based answers back to their reference entries:

  • Aggregate answer counts per question within a cycle: SELECT SURVEY_QUES_ANS_ID, COUNT(*) FROM IES.IES_SVY_RESPONSES WHERE SURVEY_CYCLE_ID = :cycle GROUP BY SURVEY_QUES_ANS_ID;
  • Resolve pick-list answers: SELECT r.TRANSACTION_ID, l.meaning FROM IES.IES_SVY_RESPONSES r, AS_LIST_ENTRIES l WHERE r.LIST_ENTRY_ID = l.LIST_ENTRY_ID;
  • Pull free-form verbatim responses: filter on non-null FREEFORM_STRING or FREEFORM_DATE.
  • Security-scoped reporting: restrict results by SECURITY_GROUP_ID to honor org-level access.
  • Interaction Center reporting: join INTERACTION_ID to interaction history to correlate surveys with service or sales contacts.

Because ATTRIBUTE1–15 exist, reporting teams should filter on ATTRIBUTE_CATEGORY to distinguish which DFF context is populated.

Related Objects

  • AS_LIST_ENTRIES — referenced via IES_SVY_RESPONSES.LIST_ENTRY_ID → AS_LIST_ENTRIES. Provides the meaning for coded pick-list responses.
  • FND_SECURITY_GROUPS — referenced via IES_SVY_RESPONSES.SECURITY_GROUP_ID. Governs row-level security visibility of responses.
  • IES_SVY_RESPONSES_PK — the composite primary key index used for unique lookups.
  • Transaction and Interaction tables (via TRANSACTION_ID and INTERACTION_ID) — link responses back to the business event that generated them, though these are not documented as formal FKs.
  • Survey definition objects in the IES schema — referenced through SURVEY_QUES_ANS_ID and SURVEY_CYCLE_ID, providing question and cycle context.

These relationships allow administrators and developers to trace a response from capture channel, through its coded or free-form value, to its owning security group and originating business transaction.