Search Results response_collected_date

Overview

The view APPS.IES_SVY_RESP_ENTRIES_V is a reporting and integration layer within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It is part of the Oracle iStore / E-Commerce suite components associated with survey and response tracking (IES = iStore eCommerce Surveys). The view presents survey response entry data collected by the survey engine, exposing the underlying transactional records in a stable, query-safe form suitable for concurrent programs, BI Publisher reports, OAF pages, and inbound/outbound interface programs.

The view is essentially a projection of a single base table, providing column aliasing and a consistent read interface. Because the view selects from a synonym (IES_SVY_RESPONSE_ENTRIES) rather than directly from the physical table, the object can be referenced without schema qualification by applications and customizations running under the APPS schema. This design isolates consumers from the physical table's schema owner and allows Oracle to evolve the underlying storage without breaking dependent reports.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over one referenced base object: the synonym IES_SVY_RESPONSE_ENTRIES. The synonym typically resolves to a physical table of the same name owned by the survey application schema and made visible to APPS through a public or private synonym.

Because the view performs a simple SELECT ... FROM IES_SVY_RESPONSE_ENTRIES REA with no joins, filters, or aggregations, it is a one-to-one mapping to the underlying table. Each row in the view corresponds to exactly one row in IES_SVY_RESPONSE_ENTRIES. No data transformation, deduplication, or derived computation occurs within the view text. This has two practical implications: (1) all DML restrictions and integrity constraints of the base table govern the view's content, and (2) query performance is essentially equivalent to querying the base table directly, apart from any synonym resolution overhead.

Key Columns

The view exposes twenty columns. The most significant for reporting and the column the user searched for — RESPONSE_COLLECTED_DATE — records the date and time the survey response was captured. This is the authoritative timestamp for response aging, SLA measurement, and period-based reporting.

• RESPONSE_ID — Primary identifier for each survey response entry.
• OBJECT_VERSION_NUMBER — Optimistic locking version counter for the row.
• SURVEY_DEPLOYMENT_ID — Identifies the deployment instance of the survey to which the response belongs.
• SURVEY_LIST_ENTRY_ID — References the specific list entry (recipient/invitee) associated with the response.
• DSCRIPT_ID — Identifier for the dialog script or questionnaire definition.
• RESPONSE_STATUS — Current lifecycle status of the response (e.g., in-progress, submitted, abandoned).
• TRANSACTION_ID and INTERACTION_ID — Cross-references to the transaction and interaction records that generated or are linked to the response.
• RESPONSE_SEQUENCE — Ordering sequence of the response within the interaction.
• RESPONSE_COLLECTED_DATE — Date/time the response was collected.
• RESPONSE_MEDIA_TYPE_CODE — Channel through which the response was received (e.g., web, email).
• PASSTHROUGH_REQUIRED_CODE and RESPONSE_EXCLUSION_CODE — Flags governing routing and exclusion logic.
• F_DELETEDFLAG — Soft-delete indicator; rows flagged as deleted should be excluded from active reporting.
• ABANDONED_FLAG — Indicates whether the respondent abandoned the survey before completion.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns for audit and change tracking.

Common Use Cases and Queries

Typical uses include measuring survey response volume by day, identifying abandoned versus completed responses, and correlating responses with transactions or interactions. Because the view is unfiltered, queries should apply the appropriate predicates, including F_DELETEDFLAG = 'N'.

Sample: count responses collected in a date range by media type.

• SELECT RESPONSE_MEDIA_TYPE_CODE, COUNT(*) FROM APPS.IES_SVY_RESP_ENTRIES_V WHERE F_DELETEDFLAG = 'N' AND RESPONSE_COLLECTED_DATE BETWEEN :p_start AND :p_end GROUP BY RESPONSE_MEDIA_TYPE_CODE;

Sample: identify abandoned responses for a deployment.

• SELECT RESPONSE_ID, SURVEY_LIST_ENTRY_ID, RESPONSE_COLLECTED_DATE FROM APPS.IES_SVY_RESP_ENTRIES_V WHERE SURVEY_DEPLOYMENT_ID = :p_deploy AND ABANDONED_FLAG = 'Y' AND F_DELETEDFLAG = 'N';

Sample: correlate responses to transactions.

• SELECT RESPONSE_ID, TRANSACTION_ID, INTERACTION_ID, RESPONSE_STATUS FROM APPS.IES_SVY_RESP_ENTRIES_V WHERE TRANSACTION_ID IS NOT NULL;

These queries remain valid across 12.1.1 and 12.2.2, as the view definition is consistent in the documented metadata.