We’re migrating to Kinetic from another vendor and are currently in the testing phase. We’re on 2025.2.8. We are finding the SSRS reports are extremely slow.
For example, the Stock Status report takes 20 minutes to run and show up in the client and will have 360 pages. Another example is the Inventory/WIP Reconciliation report can take anywhere from 3-15 minutes to run, depending on how much data are there.
Where is the bottleneck? Where are the inefficiencies we can look into? Our Epicor SSRS trainer just shrugs their shoulders. Our implementation partner just says, “Wow.” What can we look into to get these reports to run in under a minute?
If you say those numbers are what you would expect, that’s kind of wild that Epicor hasn’t seriously tackled this issue. Unfortunate. We’re not that big of a company, but will admit we have a lot of active parts. I’ve written my own report for this in T-SQL that takes about four seconds. Now working on running it offline via Crystal Reports 2025. It’s gotta be the SSRS reporting engine.
Those other reports are pretty timely, all at or under 30 seconds.
Since we’re implementing now, there really aren’t any changes. Hence, the question about where we could look for inefficiencies that others may be aware of.
Since they are on-prem they could plug the SQL into a custom SSRS report and run it directly to see.
I’m not sure how much is SSRS induced time though, I have not looked at those reports but Epicor doesn’t normally do calculation in the RDL themselves from what I have traditionally seen, they do it further upstream and then present that data to the RDL.
I’d really be curious though if the results generated were always the same as what the Epicor version shows, I suspect that the SQL being written to replace what Epicor is doing in the RDD is not doing all the same calculations. My concern here would be that it may appear or be correct 90%+ of the time but given the importance of these reports having it be off even occasionally would not be accepted here.
Don’t get me wrong, if it was that would be great as it would mean there is hope Epicor could resolve the issue for everyone, I just don’t know. I am fairly certain from conversations I’ve had in the past with Epicor support that the Stock Status Report is known to be less than perfect, you can’t run it accurately back-dated and that it is not designed to be a sub-ledger (might be getting the term wrong, I’m not a finance person).
That sums it up well from my experience. Add to that: the occasional SSRS outright/random fails (PRB0304935) that seem to plague cloud customers…don’t think it extended to on-prems though.
Hi, on prem in mid-migration here too. What would the expected time be for the smaller reports like order confirmation, proforma etc? All these reports tend to take about 30s - 2 mins. Going from SAP crystal reports taking <5s or even <20s on the worst reports to this kind of time is quite the jump
We tried increasing allocated resources to the servers, but never noticed any effect.
For me, this morning: (From hitting print preview to when the new tab is open with the report, random SO & Invoices selected.)
Custom OrderAck - 10s
Stock OrderAck - 10s
Custom Invoice - 9s
Stock Invoice - 5s
The customized order form does not really have a ton of extra fields, it is more layout, the invoice however does have a number of additional tables and fields it pulls in.
I used the suggestion from @leonardpothier to create a custom SSRS report and also used the suggestion of @Evan_Purdy to plug the SQL into the BAQ converter. The report takes about 15-30 seconds to run and present in the Kinetic client. The PDF and Excel versions look super. The total of my report reconciles to the General Ledger.
I wouldn’t consider this thread “solved,” but this is a workaround.
