INV Item Import Performance – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
Analytical report by item to predict performance of inventory item load background processes. If the number of items processed per second is decreasing with increasing total items processed, then the interface SQLs are most likely using a wrong nonselective index and should be corrected.
Report Parameters
Past Days, Min Total Item Count
Oracle EBS Tables Used
mtl_system_items_b, fnd_concurrent_requests, fnd_concurrent_programs_tl
Report Categories
Related Reports
FND Concurrent Requests 11i, FND Attached Documents, FND Concurrent Requests, Blitz Report History, ECC Admin - Concurrent Programs, FND Concurrent Managers, FND Concurrent Request Conflicts
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 | INV Item Import Performance 28-Jul-2020 181611.xlsx |
| Blitz Report™ XML Import | INV_Item_Import_Performance.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/inv-item-import-performance/ |
INV Item Import Performance - Case Study & Technical Analysis
Executive Summary
The INV Item Import Performance report is a technical diagnostic tool used by DBAs and Developers. It analyzes the throughput of the Item Import Interface (INCOIN) to identify performance degradation. If the “Items Processed Per Second” metric drops as the volume increases, it typically indicates a missing index or a non-selective index on the interface tables.
Business Use Cases
- Performance Tuning: Used during data migration or large catalog updates to ensure the system can handle the load.
- SLA Monitoring: Verifies that the nightly item feed from the PLM system is completing within the batch window.
- Root Cause Analysis: Helps pinpoint why the “Item Import” concurrent request is taking 5 hours instead of 5 minutes.
Technical Analysis
Core Tables
MTL_SYSTEM_ITEMS_INTERFACE: The interface table (implied source of the metrics).FND_CONCURRENT_REQUESTS: Used to track the start/end time and status of the import jobs.MTL_SYSTEM_ITEMS_B: The target table.
Key Joins & Logic
- Throughput Calculation:
Items Per Second=Total Items Processed/ (Request End Time-Request Start Time). - Trend Analysis: The report looks for a negative correlation between volume and speed.
Key Parameters
- Past Days: How far back to analyze the concurrent request history.
- Min Total Item Count: Filter out small test batches to focus on bulk loads.
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