Search Results fnd_svc_comp_requests_h

Overview

The table FND_SVC_COMP_REQUESTS_H is a core Application Object Library table within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a historical audit log for service component event requests. This table is owned by the APPLSYS schema and is integral to the underlying service-oriented architecture (SOA) and service component framework of EBS. Its primary role is to persistently record the lifecycle and outcome of asynchronous service invocations, such as those initiated by business events, concurrent programs, or other internal service calls, after their processing is complete. This historical record is essential for auditing, troubleshooting, and monitoring the health and performance of integrated service operations within the application.

Key Information Stored

While the provided metadata does not list specific columns, the table's description and naming conventions indicate it stores historical snapshots of service request data. Based on its purpose and common patterns for history tables in EBS, it typically contains a copy of the key data from its corresponding current requests table (often FND_SVC_COMP_REQUESTS), along with timestamps and status information marking the conclusion of the request's processing cycle. The primary key is REQUEST_HISTORY_ID. Expected columns include identifiers for the original request, the service component, the event, the execution status (e.g., SUCCESS, ERROR), detailed message text for outcomes, and critical timestamps for request creation, start, and completion. It serves as the final repository for request data that has been purged from the active processing tables.

Common Use Cases and Queries

This table is primarily accessed for diagnostic reporting and compliance auditing. Common use cases include investigating the history of specific service failures, generating reports on service component throughput and reliability over time, and auditing all service interactions for a particular business entity. A typical query would join this history table to relevant service definition tables to get descriptive names.

• Finding Failed Service Requests for a Component:
  SELECT request_history_id, component_name, event_name, status, message_text, creation_date
  FROM apps.fnd_svc_comp_requests_h
  WHERE status = 'ERROR' AND component_name = 'XX_CUSTOM_COMPONENT'
  ORDER BY creation_date DESC;
• Auditing Service Request Volume:
  SELECT TRUNC(creation_date) as request_date, component_name, COUNT(*)
  FROM apps.fnd_svc_comp_requests_h
  WHERE creation_date > SYSDATE - 30
  GROUP BY TRUNC(creation_date), component_name
  ORDER BY request_date DESC;

Related Objects

FND_SVC_COMP_REQUESTS_H is part of a closely related set of objects within the FND Service Component framework. Its most direct relationship is with the active requests table, FND_SVC_COMP_REQUESTS, from which historical records are likely derived. It also relates to foundational definition tables such as FND_SVC_COMPONENTS and FND_SVC_EVENTS, which store metadata about the available services and events. For comprehensive reporting, views may exist that join the history table with these definition tables. Programmatic interaction with this historical data is typically managed through internal Application Object Library APIs rather than direct DML.