Search Results concurrent_req_id




Overview
Explore in AI Chat

Overview

The APPS.IES_SVY_REMINDER_HST_V view is a reporting and integration artifact belonging to the IES - Scripting product within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the historical record of survey reminder events generated by the survey and scripting framework, exposing rows stored in the underlying reminder history table in a stable, query-friendly form. Because the object is defined as a view rather than a table, it carries no independent storage and is intended exclusively for read access.

The view is especially relevant to users who monitor the asynchronous execution of survey reminder processing. It surfaces the CONCURRENT_REQ_ID column, which associates each reminder history record with the Oracle EBS concurrent request that processed or generated it. In the EBS architecture, concurrent requests are the unit of background work managed by the Concurrent Manager, so this column provides the critical traceability link between a business-level survey reminder and the technical job that executed it. Administrators and developers searching on "concurrent_req_id" are typically attempting to correlate a reminder record with a specific request in FND_CONCURRENT_REQUESTS.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view is owned by the APPS schema and is defined over the base object IES_SVY_REMINDER_HST, which is referenced through a synonym. The view text is a direct projection:

No joins, filters, or computed expressions appear in the documented definition, meaning the view is a straight passthrough of the base table's columns. This design preserves the table's row identity and enables the view to function as a synonym-like access layer. The presence of standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER confirms that the underlying table participates in the standard EBS Who columns and optimistic locking conventions.

Key Columns

  • SURVEY_REMINDER_HST_ID — Primary identifier for each reminder history row.
  • SURVEY_REMINDER_ID — Foreign reference to the parent survey reminder definition.
  • REMINDER_DATE — The date on which the reminder was issued or scheduled.
  • CONCURRENT_REQ_ID — Identifier of the concurrent request associated with processing the reminder; joins to FND_CONCURRENT_REQUESTS.REQUEST_ID.
  • FULFILLMENT_REQ_ID — Identifier linking the reminder to a fulfillment request.
  • F_DELETEDFLAG — Deletion indicator for soft-deleted history rows.
  • SECURITY_GROUP_ID — Security grouping column used by the IES framework.
  • OBJECT_VERSION_NUMBER — Optimistic locking version counter.

Common Use Cases and Queries

A frequent requirement is to determine which concurrent request processed a given survey reminder, or to list all reminders tied to a specific request. The following query joins the view to the concurrent requests table:

  • SELECT h.survey_reminder_hst_id, h.survey_reminder_id, h.reminder_date, h.concurrent_req_id, r.phase_code, r.status_code FROM apps.ies_svy_reminder_hst_v h, fnd_concurrent_requests r WHERE h.concurrent_req_id = r.request_id;
  • SELECT * FROM apps.ies_svy_reminder_hst_v WHERE concurrent_req_id = :request_id;
  • SELECT * FROM apps.ies_svy_reminder_hst_v WHERE reminder_date BETWEEN :from_date AND :to_date AND NVL(f_deletedflag,'N') = 'N';

These patterns support operational diagnostics, reminder audit reporting, and reconciliation of survey reminder activity against the Concurrent Manager request log. Because the view exposes CONCURRENT_REQ_ID directly, it is the appropriate entry point whenever a user needs to traverse from business reminder data to the technical concurrent processing record.