FND Concurrent Request Conflicts – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
Lists concurrent requests that were held by the conflict resolution manager and shows their conflicting / blocking requests which were running at the time between the requested start date and conflict release date. This might not work 100% (it doesn’t consider request set conflicts yet), but should give a good indication of most conflicting scenarios.
Report Parameters
Concurrent Program Name, Started within Days, Requested Start Date From, Requested Start Date To
Oracle EBS Tables Used
fnd_concurrent_requests, fnd_concurrent_program_serial, fnd_concurrent_programs_vl
Report Categories
Related Reports
FND Concurrent Requests 11i, FND Concurrent Requests, ECC Admin - Concurrent Programs, FND Concurrent Managers, FND Concurrent Requests Summary, FND Concurrent Program Incompatibilities, INV Item Import Performance, FND Request Groups, FND Flex Value Sets, Usages and Values
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 Request Conflicts 25-Jun-2023 132118.xlsx |
| Blitz Report™ XML Import | FND_Concurrent_Request_Conflicts.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/fnd-concurrent-request-conflicts/ |
Executive Summary
The FND Concurrent Request Conflicts report analyzes the “Conflict Resolution Manager” (CRM) activity. It identifies requests that were delayed because they were incompatible with currently running jobs.
Business Challenge
- Wait Time Analysis: Understanding why a request stayed in “Pending” status for a long time.
- Incompatibility Tuning: Identifying if incompatibility rules are too aggressive and causing unnecessary bottlenecks.
- SLA Monitoring: Explaining delays in critical report delivery to business users.
The Solution
This Blitz Report reconstructs the conflict scenario:
- Blocked Request: Identifies the request that was held.
- Blocking Request: Identifies the specific request ID that was running and caused the conflict.
- Time Impact: Shows the duration of the delay caused by the conflict.
Technical Architecture
The report logic looks at requests where the PHASE_CODE was ‘P’ (Pending) and analyzes the CRM logs or infers conflicts based on the FND_CONCURRENT_PROGRAM_SERIAL rules and execution timestamps of overlapping requests.
Parameters & Filtering
- Program Name: Filter for the program that was blocked.
- Date Range: Analyze conflicts within a specific window.
Performance & Optimization
- Complex Logic: Determining conflicts retrospectively is complex. The report uses heuristic logic to match blocked requests with potential blockers.
- History: Only works for requests that are still in the
FND_CONCURRENT_REQUESTStable (not purged).
FAQ
- Q: Does it show Request Set conflicts?
- A: As noted in the description, it focuses on individual program conflicts and may not fully capture complex Request Set incompatibilities.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© 2026 Enginatics