Results for “fnd_svc_comp_requests_h”

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

Overview

FND_SVC_COMP_REQUESTS_H is a historical audit table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It records the history of Service Component Event Requests, capturing the lifecycle and state changes of service component events as they are processed by the Service Component Architecture (SCS / Service Component Manager) infrastructure within Oracle EBS. In releases 12.1.1 and 12.2.2, this table serves as the archival counterpart to the transactional service component request table, retaining the sequence of events that administrators and support engineers examine when diagnosing component execution issues, subscription delivery, or event propagation failures.

From a Data Vault modeling perspective, this object is heuristically classified as standalone. That classification suggests the table functions as an independent record store rather than participating in an explicit hub-and-satellite or link relationship within the documented foreign-key topology. In practice, the table behaves like a satellite-style history log anchored on its own surrogate identity, recording descriptive attributes about component events without enforced referential dependencies to other documented objects. This "standalone" designation should be treated as a modeling suggestion, since the metadata exposes no mined FK relationships to adjacent FND objects.

Key Information Stored

The table contains 18 documented columns. The most important of these fall into four functional groups:

• REUQEST_HISTORY_ID — the surrogate primary key defined by FND_SVC_COMP_REQUESTS_H_PK1. It also appears in the unique index FND_SVC_COMP_REQUESTS_H_U1, making it the sole documented business-key candidate as well as the technical identifier.
• COMPONENT_ID, COMPONENT_NAME, COMPONENT_TYPE, and COMPONENT_STATUS — identify the service component involved and its state at the time the historical record was captured.
• EVENT_NAME, EVENT_PARAMS, REQUEST_STATUS, REQUESTED_BY_USER, and COMPLETION_DATE — describe the event that triggered the request, its parameter payload, the outcome status, the requesting user, and when processing completed.
• CONTAINER_TYPE and CONTAINER_NAME — identify the container context in which the component executed, which is useful for distinguishing multiple run-time environments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — standard EBS WHO-column audit metadata and optimistic locking support.

Because the table is historical, CREATION_DATE and COMPLETION_DATE together provide the temporal window for each captured request, while OBJECT_VERSION_NUMBER protects against concurrent modification during archival or purge activity.

Common Use Cases and Queries

Typical use cases center on diagnostics and reconciliation. Support engineers query the table to trace why a service component event failed, stalled, or completed unexpectedly. A representative pattern groups by component and status to surface failure trends:

• Failure analysis: SELECT COMPONENT_NAME, EVENT_NAME, REQUEST_STATUS, COUNT(*) FROM FND_SVC_COMP_REQUESTS_H WHERE REQUEST_STATUS = 'ERROR' GROUP BY COMPONENT_NAME, EVENT_NAME, REQUEST_STATUS;
• Chronological trace for a component: SELECT REQUEST_HISTORY_ID, EVENT_NAME, REQUEST_STATUS, CREATION_DATE, COMPLETION_DATE FROM FND_SVC_COMP_REQUESTS_H WHERE COMPONENT_ID = :component_id ORDER BY CREATION_DATE DESC;
• User activity review: SELECT REQUESTED_BY_USER, COUNT(*) FROM FND_SVC_COMP_REQUESTS_H WHERE CREATION_DATE > SYSDATE - 7 GROUP BY REQUESTED_BY_USER;
• Container-level reporting: SELECT CONTAINER_TYPE, CONTAINER_NAME, COUNT(*) FROM FND_SVC_COMP_REQUESTS_H GROUP BY CONTAINER_TYPE, CONTAINER_NAME;

Because the table is history-oriented and can grow rapidly, purge scripts and date-range filters (using CREATION_DATE) are strongly recommended before running full-table aggregations.

Related Objects

The documented metadata classifies this table as standalone, exposing no mined foreign-key relationships to adjacent FND objects. Consequently, related objects are inferred from the product domain rather than from declarative constraints:

• FND_SVC_COMP_REQUESTS — the transactional counterpart that this table archives; join on COMPONENT_ID, EVENT_NAME, and REQUEST_HISTORY_ID semantics.
• FND_SVC_COMPONENTS — the component definition table; join on COMPONENT_ID to resolve component metadata and naming.
• FND_SVC_CONTAINERS — the container definition table; join on CONTAINER_NAME / CONTAINER_TYPE.
• FND_SVC_COMP_PARAM_VALUES and FND_SVC_COMP_PARAMETERS — parameter definitions referenced by EVENT_PARAMS; join on COMPONENT_ID.
• FND_SVC_COMP_SUBSCR — component subscription definitions that govern event delivery; join on COMPONENT_ID.
• FND_USER — resolves CREATED_BY, LAST_UPDATED_BY, and REQUESTED_BY_USER to user identity.

Pluggable database deployments in 12.2.2 must reference the APPS synonyms rather than the APPLSYS base objects directly, since APPLSYS is the owner of record for this table.