Results for “ies_svy_list_entries”

46 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IES_SVY_LIST_ENTRIES table is a core transactional object within the Oracle E-Business Suite IES (Scripting) module. It stores the individual roster entries that make up the deployment population of a survey campaign. Each row represents a single invitee who has been assigned to a deployed survey — a respondent, contact, or target party — together with tracking information about whether the survey was dispatched and how many responses were received. In this respect the table functions as the operational bridge between a survey definition and the actual set of people or entities being surveyed.

From a Data Vault modeling perspective, the mined foreign-key topology classifies this object as hub-leaning. This is a heuristic suggestion rather than a physical architectural mandate: the table carries a single-column surrogate primary key and multiple independent business keys (deployment, list entry, script, security group), giving it the key-preserving character of a hub. Downstream history and response tables then attach to it as satellites and links. Practitioners modeling the IES schema for warehousing should treat IES_SVY_LIST_ENTRIES as the anchor from which survey-response facts branch.

Key Information Stored

The table contains 32 documented columns in the 12.2.2 ETRM schema. The most significant are summarized below.

Only SURVEY_LIST_ENTRY_ID is documented as a unique index candidate (IES_SVY_LIST_ENTRIES_N2); the remaining keys are foreign-key lookups rather than business-key uniqueness constraints.

Common Use Cases and Queries

The principal reporting scenarios involve survey delivery tracking, response-rate measurement, and reminder targeting.

  • Delivery status by deployment: join to IES_SVY_DEPLYMENTS_ALL to report how many entries per campaign have SURVEY_SENT_DATE populated versus NULL (pending dispatch).
  • Response monitoring: aggregate NO_OF_RESPONSES_RECD grouped by SURVEY_DEPLOYMENT_ID to derive completion rates.
  • Reminder targeting: identify entries whose NO_OF_RESPONSES_RECD is zero and SURVEY_SENT_DATE is beyond a threshold, then feed SURVEY_LIST_ENTRY_ID into IES_SVY_ENTRS_REMIND_HST.
  • Error reconciliation: filter on ERROR_CODE to surface failed distributions for retry.
  • Extensibility reporting: query ATTRIBUTE1–ATTRIBUTE15 for customer-defined attributes captured at the roster level.

A representative pattern:

  • SELECT l.SURVEY_DEPLOYMENT_ID, l.SURVEY_SENT_DATE, l.NO_OF_RESPONSES_RECD FROM IES.IES_SVY_LIST_ENTRIES l WHERE l.F_DELETEDFLAG = 'N' AND l.SECURITY_GROUP_ID = :sgid;

All queries should honor F_DELETEDFLAG and SECURITY_GROUP_ID to respect soft deletes and organizational security.

Related Objects

The following objects are the most significant dependents or parents of IES_SVY_LIST_ENTRIES, based on documented foreign-key relationships.

  • IES_SVY_DEPLYMENTS_ALL — parent deployment definition; joined via SURVEY_DEPLOYMENT_ID.
  • AS_LIST_ENTRIES — source list/party definition; joined via LIST_ENTRY_ID.
  • IES_DEPLOYED_SCRIPTS — deployed script version; joined via DSCRIPT_ID.
  • FND_SECURITY_GROUPS — security grouping for data access; joined via SECURITY_GROUP_ID.
  • IES_SVY_RESPONSE_ENTRIES — child table storing captured responses; references SURVEY_LIST_ENTRY_ID.
  • IES_SVY_ENTRS_REMIND_HST — child table recording reminder history; references SURVEY_LIST_ENTRY_ID.

Together these objects form the end-to-end survey lifecycle: list definition, deployment, dispatch, reminder, and response capture.