Search Results survey_list_entry_id




Overview

The IES_SVY_ENTRS_RMD_HST_V view is a reporting and integration object within the Oracle EBS IES – Scripting product module (also referred to in ETRM as the Scripting component of Oracle Marketing/Advanced Outbound). It is owned by the APPS schema and carries a VALID status in both the 12.1.1 and 12.2.2 environments. The view exposes a denormalized, read-only projection of the reminder history for survey list entries, allowing concurrent programs, Oracle Answers reports, and external integrations to retrieve reminder scheduling and fulfillment data without directly accessing the underlying transactional table.

Functionally, the view presents one row per survey list entry reminder history record. This supports auditing of when survey reminders were dispatched, which concurrent request produced them, and which fulfillment request was associated with each reminder. The SURVEY_LIST_ENTRY_ID column is the primary correlation key that customers and integrators use to join this reminder history back to the parent survey list entry — this is the exact identifier referenced in the user search phrase "survey_list_entry_id". In 12.2.2 the view is documented in ETRM with the referenced base object IES_SVY_ENTRS_REMIND_HST (SYNONYM).

Underlying Base Objects

The view is defined over a single base object: the synonym IES_SVY_ENTRS_REMIND_HST, which resolves to the underlying reminder history table in the APPS schema. The view text is a straightforward SELECT of all significant columns from that synonym, aliased as ERH. No joins, aggregations, or filters are applied in the view definition, meaning the view is a column-level projection only — row filtering and relational joins must be supplied by the consuming query.

Because the view references the synonym rather than the physical table directly, it participates in the standard EBS synonym resolution model, and the view inherits the same security and grants applicable to the base object. Multi-tenancy is preserved through the SECURITY_GROUP_ID column, and soft deletes are represented through F_DELETEDFLAG. The OBJECT_VERSION_NUMBER column supports optimistic locking semantics consistent with the underlying entity.

Key Columns

  • SURVEY_LIST_ENTRY_ID — Foreign key to the survey list entry; the primary business correlation identifier for joining to survey list entry data.
  • ENTRY_REMINDER_HST_ID — Surrogate primary key of the reminder history record.
  • REMINDER_DATE — The scheduled or actual date on which the reminder was issued.
  • CONCURRENT_REQ_ID — The concurrent request that generated the reminder record, enabling traceability through the concurrent manager.
  • FULFILLMENT_REQ_ID — The associated fulfillment request identifier.
  • F_DELETEDFLAG — Soft-delete indicator; active rows typically carry a non-deleted flag value.
  • SECURITY_GROUP_ID — Security group for multi-org/multi-tenant data partitioning.
  • OBJECT_VERSION_NUMBER — Optimistic locking version, incremented on each update of the base row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns for audit and concurrency.

Common Use Cases and Queries

Typical scenarios include auditing reminder dispatch activity for a survey campaign, reconciling reminder history against concurrent requests, and integrating reminder data into external marketing analytics. A common query retrieves all active reminders for a specific survey list entry:

  • SELECT survey_list_entry_id, entry_reminder_hst_id, reminder_date, concurrent_req_id, fulfillment_req_id FROM ies_svy_entrs_rmd_hst_v WHERE survey_list_entry_id = :entry_id AND f_deletedflag = 'N' ORDER BY reminder_date DESC;

Another frequent pattern aggregates reminder counts per entry, or joins to concurrent request tables via CONCURRENT_REQ_ID to determine which program generated the reminder. Because the view is unfiltered, callers should always constrain by SURVEY_LIST_ENTRY_ID, REMINDER_DATE, or SECURITY_GROUP_ID to avoid full scans of reminder history.