Search Results event_display_name




Overview
Explore in AI Chat

Overview

APPS.FND_SVC_COMP_REQUESTS_V is a multi-lingual (language-resolved) view in the Oracle E-Business Suite Applications schema. It presents the scheduling and execution state of Service Component Requests, which are the runtime units created and managed by the Service Component Manager (FND_SVC_COMPONENT) infrastructure. Each row represents a single scheduled request associated with a service component, combining the component's own request metadata with the corresponding job scheduler and event queue information.

Because the view is language-resolved, columns that surface translatable text (notably EVENT_DISPLAY_NAME) are returned in the session's current language, drawn from the underlying WF_EVENTS_VL language view. This makes the view suitable for both reporting and integration use, since subscribers to EBS interfaces can read a human-readable event display name without implementing their own language joins. The presence of Object Version Number indicates the row is exposed as an ORM-managed or concurrent-safe entity, useful when the view is consumed programmatically rather than only for ad hoc SQL.

The view has no dependents; it is not referenced by any other database object, so changes to it do not propagate to further database-level consumers.

Underlying Base Objects

According to the documented dependency metadata, APPS.FND_SVC_COMP_REQUESTS_V is defined over three objects:

  • FND_SVC_COMP_REQUESTS (synonym) — the primary source, supplying component request identity, scheduling fields, parameters, and status counters.
  • WF_ALL_JOBS (synonym) — the Workflow job scheduler table, supplying JOB_ID, LAST_DATE, NEXT_DATE, THIS_DATE, INTERVAL, and FAILURES.
  • WF_EVENTS_VL (view) — the language-resolved Workflow events view, supplying EVENT_NAME and EVENT_DISPLAY_NAME.

The join permits a single query to retrieve both the "what should run" definition (component, event, parameters) and the "when did it run" scheduler state (dates and outcomes) for each request.

Key Columns

  • COMPONENT_ID / COMPONENT_REQUEST_ID — identify the owning service component and the individual request instance.
  • EVENT_DISPLAY_NAME (VARCHAR2, 80) — the user-facing event label resolved to the session language; the column most commonly queried by name.
  • EVENT_NAME (VARCHAR2, 240) — the internal Workflow event identifier; parameterized, hence longer than the display name.
  • EVENT_PARAMS (VARCHAR2, 1996) — the serialized parameter string passed to the event subscription.
  • EVENT_DATE / EVENT_FREQUENCY / INTERVAL — timing definition for the schedule, including recurrence interval.
  • JOB_ID, LAST_DATE, NEXT_DATE, THIS_DATE, FAILURES — scheduler state: the job identity, previous run, next scheduled run, current run, and accumulated failure count.
  • REQUESTED_BY_USER (VARCHAR2, 320) — the user context that initiated the request.
  • WHAT (VARCHAR2, 4000) — the executable/command payload for the scheduled job.
  • CREATED_BY and OBJECT_VERSION_NUMBER — standard audit and concurrency columns.

Common Use Cases and Queries

Typical scenarios include monitoring scheduled component requests, diagnosing repeated failures, and reporting on upcoming executions for a given event.

List all requests with readable event labels:

  • SELECT COMPONENT_REQUEST_ID, EVENT_DISPLAY_NAME, EVENT_NAME, NEXT_DATE, FAILURES FROM APPS.FND_SVC_COMP_REQUESTS_V;

Identify requests that have failed repeatedly:

  • SELECT COMPONENT_ID, EVENT_DISPLAY_NAME, LAST_DATE, FAILURES FROM APPS.FND_SVC_COMP_REQUESTS_V WHERE FAILURES > 0 ORDER BY FAILURES DESC;

Retrieve a single request's full payload and schedule:

  • SELECT EVENT_NAME, EVENT_PARAMS, INTERVAL, THIS_DATE, WHAT FROM APPS.FND_SVC_COMP_REQUESTS_V WHERE COMPONENT_REQUEST_ID = :req_id;