Search Results fnd_svc_comp_requests_v




Overview
Explore in AI Chat

Overview

FND_SVC_COMP_REQUESTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, classified under the FND — Application Object Library product. It exposes the scheduling and execution state of Service Component Requests, which are the workload definitions that drive the FND Service Components framework: the dispatching, retry, and governance layer for concurrent service requests such as workflow background events, Java Concurrent Programs, or Service Component Manager jobs.

The view resolves the user's queried column, EVENT_FREQUENCY, from the FND_SVC_COMP_REQUESTS base, while enriching the request content with the display-friendly event label from WF_EVENTS_VL and the live Workflow job schedule detail from WF_ALL_JOBS. It therefore provides a single denormalized row per component request that blends configuration intent, event metadata, and actual scheduler timing. In 12.1.1 and 12.2.2 the view is documented as VALID and reports no editioning or Online Patching complications; it carries no materialized or indexed basis and inherits the security of its underlying tables, so queries run under APPS or a synonym are subject to standard FND security and privilege checks.

Underlying Base Objects

  • FND_SVC_COMP_REQUESTS (referenced through a synonym, alias CR) — the primary driver table, holding one row per component request and supplying COMPONENT_ID, COMPONENT_REQUEST_ID, EVENT_FREQUENCY, EVENT_NAME, EVENT_PARAMS, JOB_ID, and audit columns.
  • WF_EVENTS_VL (view, alias EV) — the translatable Workflow Events definition, joined on CR.EVENT_NAME = EV.NAME to yield the localized EVENT_DISPLAY_NAME.
  • WF_ALL_JOBS (synonym, alias WAJ) — the Workflow scheduler job table, joined on CR.JOB_ID = WAJ.JOB to expose runtime scheduling state: THIS_DATE, LAST_DATE, NEXT_DATE, INTERVAL, FAILURES, and WHAT.

The join and the columns projected map directly to the registered view text, and the view remains usable only where WORKFLOW and the Service Components tables are installed and their synonyms are visible from the querying schema.

Key Columns

  • COMPONENT_ID / COMPONENT_REQUEST_ID — identifiers for the service component and its individual request instance; the pair is the natural key for most diagnostic queries.
  • EVENT_FREQUENCY — the recurring cadence at which the component request is intended to fire. This is the column surfaced in the user's search and is the primary configuration field governing repeat scheduling.
  • EVENT_NAME / EVENT_DISPLAY_NAME / EVENT_PARAMS — the Workflow event key, its translatable display label, and the parameter payload passed to the event.
  • JOB_ID, THIS_DATE, LAST_DATE, NEXT_DATE, INTERVAL, FAILURES, WHAT — the current job snapshot: the scheduler job identifier, execution timestamps, the interval expression, the failure counter, and the call specification executed by the job.
  • CREATED_BY, EVENT_DATE, REQUESTED_BY_USER, OBJECT_VERSION_NUMBER — audit and concurrency control; OBJECT_VERSION_NUMBER supports optimistic locking when the underlying request is updated.

Common Use Cases and Queries

Typical uses include verifying that scheduled service component requests are firing at the intended frequency, diagnosing repeated job failures, and auditing which user or process registered an event-driven request. The following sample identifies active requests whose current interval or frequency indicates retry pressure and lists their next scheduled execution.

  • SELECT component_request_id, event_name, event_display_name, event_frequency, interval, failures, next_date FROM fnd_svc_comp_requests_v WHERE failures > 0 ORDER BY failures DESC;
  • SELECT component_id, event_display_name, this_date, last_date, next_date FROM fnd_svc_comp_requests_v WHERE job_id = :job_id;
  • SELECT event_frequency, COUNT(*) FROM fnd_svc_comp_requests_v GROUP BY event_frequency;
  • SELECT cr.component_request_id, ev.event_display_name, cr.requested_by_user, cr.event_params FROM fnd_svc_comp_requests_v cr WHERE cr.event_date > SYSDATE - 7;

Because the view reads live Workflow scheduler data, results reflect the current job state rather than a historical snapshot; for trend analysis capture the output to a staging table. Queries should be run as APPS or through an appropriately granted synonym, and the FND Service Components framework must be configured for rows to be returned.