If I submit for week 15 it works but week 5 crashes. I suspect it might be for some internal, technical reason. For example, I believe our GLPeriodBal table doesn’t have a week-zero in it yet for the year in question (whatever that might mean, it comes up in my search results).
Is a week zero necessary for running trial balances? Is there a way to get it added? Since week 5 predates the time we started on the ERP, I would expect the report to come back empty … but not to crash altogether.!
Any help would be appreciated. I found the data dictionary in Epicor ERP for the table, GLPeriodBal, but I would appreciate having a lot more technical information in this area, if anyone has it. We may be writing our own trial balance report or dashboard if the canned report is unreliable.
@asalvatore Yes I do see that same message in the third tab. Thanks for the pointer.
It says “No Record Selected”.
The same things happen if I filter a report on COA categories that aren’t present in a given week (ie. in a week that is otherwise working fine). It seems like the more preferred approach in this case would be to deliver a report that is empty rather than to crash altogether.
Do you happen to know where I can find information about the GLPeriodBal table? We may need that in case we want to write our own reporting against this data.
I’d start by looking at the GLPeriodBal table within the Business Activity Query Designer. If you are considering custom reporting I believe that BAQ reports behave the same and will not execute if they have no data to display (thought perhaps you could trick it with a calculated field?).
There is some utility in not having reports execute if there is no data, I find it especially useful for scheduled reports. Don’t want a bunch of essentially blank reports taking up space.
