FND Concurrent Requests Summary – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Concurrent programs sorted by the sum of their historic execution times

Report Parameters

Started within Days, Running from Date, Running to Date, Program Name, System Program Name, Executable Short Name, Execution Method, Show Argument Text, Show Reports only

Oracle EBS Tables Used

fnd_concurrent_requests, fnd_concurrent_programs_vl, fnd_user, fnd_executables, fnd_responsibility_vl

Report Categories

Enginatics

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource	Link
Excel Example Output	FND Concurrent Requests Summary 15-Oct-2023 092431.xlsx
Blitz Report™ XML Import	FND_Concurrent_Requests_Summary.xml
Full SQL on Enginatics	www.enginatics.com/reports/fnd-concurrent-requests-summary/

Executive Summary

The FND Concurrent Requests Summary report provides a performance profile of your concurrent processing system. It aggregates historical execution data to highlight the most resource-intensive programs.

Business Challenge

Performance Tuning: Identifying the “Top 10” programs that consume the most system time.
Trend Analysis: Seeing if specific jobs are taking longer to run over time.
Housekeeping: Finding programs that run frequently but generate no output or are cancelled often.

The Solution

This Blitz Report aggregates data from FND_CONCURRENT_REQUESTS:

Total Runtime: Sums up the execution time for each program.
Average Runtime: Calculates the mean duration to establish a baseline.
Execution Count: Shows how often the program is run.

Technical Architecture

The report groups data by PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID. It calculates metrics like SUM(ACTUAL_COMPLETION_DATE - ACTUAL_START_DATE).

Parameters & Filtering

Date Range: “Started within Days” or specific dates to define the analysis period.
Program Name: Filter for specific jobs.

Performance & Optimization

Purge Impact: The report can only analyze data currently in the request history table. If you purge requests weekly, you can only analyze the last week.
Summary Level: This is an aggregate report, so it runs fast even with large history tables.

FAQ

Q: Can I drill down to specific requests?
- A: This report gives the summary. Use “FND Concurrent Requests” (Detail) to see the individual runs.
Q: Does “Execution Time” include wait time?
- A: No, it typically measures the time from “Actual Start” to “Actual Completion”, excluding time spent in the queue.

FND Concurrent Requests Summary | Oracle EBS SQL Report

Concurrent programs sorted by the sum of their historic execution times – Oracle E-Business Suite SQL report