FND Concurrent Requests 11i
Description:
Running, scheduled and historic concurrent requests including phase, status, parameters, schedule, timing, delivery and output option information. For performance analysis of running requests, the report contains sid, currently executed sql_id and sql_text and distribution of wait time on different wait classes.
Use parameter ‘Scheduled or Running’ to get a list of all currently scheduled or running requests.
Parameters
Concurrent Program Name, Concurrent Progr. (all languages), Concurrent Program Short Name, Request Id, Requested By, Started within Days, Scheduled or Running, Waiting for x Minutes, Running longer than x Minutes, Phase, Status, Show Parameters Display Values, Show BI Pub & Delivery Options, Show active session SQL Text, Parameter Text contains, Request Set Name, Execution Method, Executable Short Name, Running from Timestamp, Running to Timestamp, Requested Start Date From, Requested Start Date To, Node, Manager Name, Operating Unit, Exclude Conc Program Name, Incremental Alert Mode
Used tables
Categories
Dependencies
If you would like to try one of these Oracle EBS SQLs without having Blitz Report installed, note that some of the reports require functions from utility package xxen_util.
Example Report
FND Concurrent Requests 11i 22-Jul-2020 121122.xlsx
Report SQL
www.enginatics.com/reports/fnd-concurrent-requests-11i/
Blitz Report™ import options
FND_Concurrent_Requests_11i.xml
Case Study & Technical Analysis: FND Concurrent Requests
Executive Summary
The FND Concurrent Requests report is the definitive operational dashboard for Oracle E-Business Suite System Administrators and Support Analysts. It provides real-time and historical visibility into the Concurrent Processing system, enabling teams to monitor system health, troubleshoot performance bottlenecks, and ensure the timely execution of critical business processes.
Business Challenge
- Operational Blind Spots: Standard Oracle forms are often slow and lack the advanced filtering needed to manage high-volume environments with millions of requests.
- Performance Troubleshooting: Identifying the root cause of a “long-running” request usually requires separate DBA tools to check database sessions and wait events.
- Resource Management: Unchecked requests generating massive log or output files can silently consume disk space and degrade system performance.
The Solution
This report bridges the gap between functional administration and technical performance monitoring.
- Unified Monitoring: It consolidates request status, scheduling parameters, and delivery options into a single, filterable view.
- Real-Time Diagnostics: For currently running requests, it exposes critical database metrics—including the active
SQL_ID, execution text, and wait classes—allowing immediate diagnosis of “stuck” jobs. - Proactive Alerting: Parameters like “Running longer than x Minutes” or “Log file larger than x MB” enable proactive identification of anomalies before they impact users.
Technical Architecture (High Level)
- Primary Tables:
FND_CONCURRENT_REQUESTS,FND_CONCURRENT_PROGRAMS_VL,FND_USER,FND_RESPONSIBILITY_VL. - Performance Views:
GV$SESSION,GV$PROCESS,GV$SQL(accessed dynamically for running requests). - Logical Relationships:
- The report joins the core Request table to Program, User, and Responsibility definitions to provide human-readable context.
- For requests with
Phase = 'Running', it performs a left join to the database session views (GV$SESSION) using theORACLE_PROCESS_ID(SPID) to retrieve real-time execution details. - It parses and decodes the raw argument string to display meaningful parameter values.
Parameters & Filtering
- Scheduled or Running: A binary flag to instantly filter the list to only active or pending workloads, removing historical clutter.
- Running longer than x Minutes: A critical threshold filter for identifying performance outliers and potential runaways.
- Show active session SQL Text: When enabled, retrieves the actual SQL statement currently executing in the database for running requests.
- Output/Log file larger than x MB: Identifies requests that are consuming excessive file system storage.
- Wait for x Minutes: Highlights requests that have been in a ‘Pending’ state for an extended period, indicating potential manager issues.
Performance & Optimization
- Conditional Logic: The report is optimized to only query heavy performance views (
GV$) when relevant (i.e., for running requests), ensuring the report itself runs instantly. - Indexed Access: Filters on
REQUEST_ID,REQUEST_DATE, andPROGRAM_IDleverage standard EBS indexes to ensure fast retrieval of historical data. - Direct Output: Bypasses the XML Publisher layer to stream data directly to Excel, capable of handling tens of thousands of rows without timeout.
FAQ
Q: Can I see the SQL statement for a request that has already completed?
A: No, the “Active Session SQL Text” is retrieved from the live database session cache (GV$SQL). Once a request finishes and the session closes, this runtime information is no longer available in memory.
Q: Why do some requests show a status of ‘Inactive’ but ‘No Manager’? A: This usually indicates that the Concurrent Manager defined to run this specific program is not running or is busy. The report helps identify these bottlenecks by showing the ‘Manager Name’ and ‘Node’.
Q: Does this report show requests from all RAC nodes?
A: Yes, it queries global views (GV$) to capture session information across all nodes in a Real Application Clusters (RAC) environment.
Oracle E-Business Suite Reporting Library
We provide an open source Oracle EBS SQLs as a part of operational and project implementation support toolkits for rapid Excel reports generation.
Blitz Report™ is based on Oracle EBS forms technology, and hence requires minimal training. There are no data or performance limitations since the output files are created directly from the database without going through intermediate file formats such as XML.
Blitz Report can be used as BI Publisher and Oracle Discoverer replacement tool. Standard Oracle BI Publisher and Discoverer reports can also be imported into Blitz Report for immediate output to Excel. Typically, reports can be created and version tracked within hours instead of days. The concurrent request output automatically opens upon completion without the need for re-formatting.
The Filters, Columns, Rows and Values fields are used to create and deliver the data in pivot table format with full drill down to details.

The Excel template upload functionality in Blitz Report allows users to create their own layouts by uploading an Excel template with additional sheets and charts, automatically refreshed when the report runs again. This allows to create custom dashboards and more advanced visualizations of report data.

You can download and use Blitz Report free of charge for your first 30 reports.
The installation and implementation process usually takes less than 1 hour; you can refer to our installation and user guides for specific details.
If you would like to optimize your Oracle EBS implementation and or operational reporting you can visit www.enginatics.com to review great ideas and example usage in blog. Or why not try for yourself in our demo environment.
Useful Links
Blitz Report™ – World’s fastest data upload and reporting for Oracle EBS
Oracle Discoverer replacement – importing worksheets into Blitz Report™
Blitz Report™ Questions & Answers
Supply Chain Hub by Blitz Report™
© 2025 Enginatics