Results for “fulfillment_req_id”

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

Overview

The IES_SVY_ENTRS_REMIND_HST table is a transactional table within the IES - Scripting (Oracle iScript / Scripting) module of Oracle E-Business Suite. It stores the historical audit record of reminders issued against survey list entries that require respondent action. When a survey participant is expected to complete an entry and does not do so within the configured window, the Scripting engine generates a reminder notification; each such event is persisted in this table as a history row. The table therefore functions as an append-oriented audit trail rather than as the operational driver of reminder logic, which is exercised by the Scripting runtime and its concurrent programs.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. This is a modeling suggestion: the table carries a surrogate primary key, a foreign reference to a parent business entity, descriptive and audit attributes, and a set of standard EBS WHO columns — the classic profile of a satellite attached to a hub, capturing the changing state of a business object over time. Its role is historical (the _HST suffix and the presence of a dedicated reminder-date attribute confirm this), and it is not intended to act as a hub of independent business keys.

Key Information Stored

The table is documented with twenty-nine columns under the IES schema. The most significant of these are grouped below.

• ENTRY_REMINDER_HST_ID — the surrogate primary key, enforced by IES_SVY_ENTRS_REMIND_HST_PK and reinforced by the unique index IES_SVY_ENTRS_REMIND_H_N1. It uniquely identifies each historical reminder event.
• SURVEY_LIST_ENTRY_ID — the foreign key to IES_SVY_LIST_ENTRIES and the true business-key candidate linking the reminder history row to the survey list entry that triggered it.
• REMINDER_DATE — the effective date and time on which the reminder was generated or scheduled, central to tracking cadence and escalation.
• CONCURRENT_REQ_ID — identifies the concurrent request that produced the reminder history row, enabling traceability to the submitting program.
• FULFILLMENT_REQ_ID — links the reminder event to the fulfillment request, supporting correlation of notification delivery.
• F_DELETEDFLAG — a soft-delete / logical-deletion indicator, allowing records to be retained for audit while excluded from active processing.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, providing the multi-tenant or responsibility-based data segregation typical of EBS tables.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) to detect concurrent modifications.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard WHO audit columns recording insert and update actors and timestamps.
• LAST_UPDATE_LOGIN — the login identifier of the user who last touched the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF (Descriptive Flexfield) columns reserved for customer-specific extensions without schema modification.

Common Use Cases and Queries

Typical usage centers on auditing reminder activity and diagnosing notification behavior for surveys.

• Extract all reminder events for a given survey entry to understand how many reminders were issued and when:

SELECT h.ENTRY_REMINDER_HST_ID,
       h.SURVEY_LIST_ENTRY_ID,
       h.REMINDER_DATE,
       h.CONCURRENT_REQ_ID,
       h.FULFILLMENT_REQ_ID
  FROM IES.IES_SVY_ENTRS_REMIND_HST h
 WHERE h.SURVEY_LIST_ENTRY_ID = :p_entry_id
   AND NVL(h.F_DELETEDFLAG,'N') = 'N'
 ORDER BY h.REMINDER_DATE;

• Volume and cadence analysis by day or period, useful for reporting on survey response pressures:

SELECT TRUNC(h.REMINDER_DATE) REMINDER_DAY,
       COUNT(*) CNT
  FROM IES.IES_SVY_ENTRS_REMIND_HST h
 GROUP BY TRUNC(h.REMINDER_DATE)
 ORDER BY 1;

• Filtering strictly to the current security group to respect EBS multi-tenant boundaries:

SELECT h.ENTRY_REMINDER_HST_ID
  FROM IES.IES_SVY_ENTRS_REMIND_HST h
 WHERE h.SECURITY_GROUP_ID = :p_security_group_id;

Because the table is historical, queries should generally join back to IES_SVY_LIST_ENTRIES to recover the current entry state rather than relying on the history row alone.

Related Objects

The following objects are the most significant relationships documented for this table.

• IES_SVY_LIST_ENTRIES — the parent entity; joined on SURVEY_LIST_ENTRY_ID. This is the primary business relationship and the source of entry context.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, providing the security grouping for the row.
• IES_SVY_ENTRS_REMIND_HST_PK — the primary key constraint on ENTRY_REMINDER_HST_ID.
• IES_SVY_ENTRS_REMIND_H_N1 — the unique index supporting key lookup on ENTRY_REMINDER_HST_ID.
• FND_CONCURRENT_REQUESTS — the logical join target for CONCURRENT_REQ_ID, used to resolve the program and run details that generated each reminder.

The Scripting module's reminder generation processes and the OAF survey pages that display entry status are the runtime consumers that populate and read this table. Together with its parent list-entries table and the fulfillment and concurrent request references, IES_SVY_ENTRS_REMIND_HST forms the historical backbone for reminder auditing in Oracle EBS Scripting.