Results for “ies_svy_reminder_hst”

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

Overview

The IES_SVY_REMINDER_HST table resides in the IES schema and belongs to the Oracle EBS Scripting (IES) product family. It serves as a history or audit repository for survey reminder records, capturing the chronological lifecycle of reminder activities associated with survey scripts and their delivery to respondents. In Oracle EBS 12.1.1 and 12.2.2, this table supports the Scripting module's ability to schedule, track, and reconcile survey reminders while preserving a durable record of past states for reporting and compliance purposes.

Under a heuristic Data Vault classification derived from the foreign key structure, this object is best characterized as a satellite-leaning entity. Its dependency on IES_SVY_REMINDERS via SURVEY_REMINDER_ID suggests that it records descriptive, time-variant attributes that belong to a parent reminder business key rather than establishing new relationships or acting as an independent hub. This modeling hint reflects the table's role as a historical companion to the operational reminder entity.

Key Information Stored

The table contains 29 documented columns. The most significant are:

• SURVEY_REMINDER_HST_ID — the surrogate primary key defined by IES_SVY_REMINDER_HST_PK, also exposed through the unique index IES_SVY_REMIND_HST_N1.
• SURVEY_REMINDER_ID — the foreign key referencing IES_SVY_REMINDERS, identifying the parent reminder record to which each history row belongs.
• REMINDER_DATE — the date on which the reminder event occurred or was scheduled.
• CONCURRENT_REQ_ID and FULFILLMENT_REQ_ID — identifiers linking the historical reminder to concurrent processing requests and fulfillment activity.
• F_DELETEDFLAG — a soft-delete indicator used to preserve rows while excluding them from active views.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant or organizational data partitioning.
• OBJECT_VERSION_NUMBER — the optimistic locking column standard in EBS 12.2.x tables.

The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit traceability, while the fifteen ATTRIBUTE flex columns plus ATTRIBUTE_CATEGORY support extensibility without schema changes. The distinction between the surrogate key SURVEY_REMINDER_HST_ID and the business-key candidate SURVEY_REMINDER_ID must be observed carefully when designing joins.

Common Use Cases and Queries

Typical use cases include audit reporting of reminder delivery, reconciliation of concurrent processing outcomes, and trend analysis of survey response rates over time. A representative query joins the history table to its parent:

• SELECT h.SURVEY_REMINDER_HST_ID, h.SURVEY_REMINDER_ID, h.REMINDER_DATE, h.CONCURRENT_REQ_ID FROM IES.IES_SVY_REMINDER_HST h WHERE h.SURVEY_REMINDER_ID = :p_reminder_id ORDER BY h.REMINDER_DATE DESC;
• Filtering active history rows with WHERE NVL(F_DELETEDFLAG,'N') = 'N' to exclude soft-deleted entries.
• Joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to constrain results to the caller's security context.

Related Objects

• IES_SVY_REMINDERS — parent entity joined on IES_SVY_REMINDER_HST.SURVEY_REMINDER_ID = IES_SVY_REMINDERS.SURVEY_REMINDER_ID.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security partitioning.
• IES_SVY_REMINDER_HST_PK — primary key constraint over SURVEY_REMINDER_HST_ID.
• IES_SVY_REMIND_HST_N1 — unique index supporting business-key lookups.
• Concurrent manager objects referenced by CONCURRENT_REQ_ID, and fulfillment objects referenced by FULFILLMENT_REQ_ID.