Storing BAQ Results to use in a BAQ Report

Good Morning Epicor Guru’s

I have done some searching on here for this particular problem, and while it usually brings me to executive reports I don’t think its the solution I need as this seems to point more torwards creating graphs with the stored data (or just don’t understand them <-- Likely).

I have a weekly BAQ report that I run for Purchasing and one of the KPI items that they want to see is the amount of PO suggestions that were present at the start of the PREVIOUS week. So when I run the report on Monday, I need to have stored the # of suggestions that were present the previous Monday…the only way I can think to do that is run a BAQ, and store that number somewhere the previous Monday, and pull that number into the report when it runs on the current Monday…

A swift kick in the right direction would be appreciated…

Thanks!

You could try to store the # of suggestions in a UD table, update that UD table every time the BAQ is run (would need to change to a UBAQ), then include the UD table in your scheduled (U)BAQ (would need to come up with a clever way to join, maybe Datepart(wk,…) = Datepart(wk,…)-1 could work). There may be an easier way, not sure.

Thanks Adam…I figured the UD table option was probably where I was heading but I haven’t really done ANYTHING with UD tables so just starting down that road now…

I’m not sure if this would work on your end but this might be another direction you could try?

Yeah I think this is the right way to go, kinda mixed up BAQ Export Process and Scheduled BAQ Report with my previous post…

So this would export a file…then I would manually put the value back into the system before the BAQ Report runs?

@adamk Yes this would export out a file base on the schedule. Though, when I think about this again this might not be a good direction.

Have you ever code BPM within BAQ before? Don’t take my word on this but this might work.

1)image

  1. In your BAQ, create a Calculated Field with empty data
    image


5)
image
6) In here maybe you can code what you need to look back on the Date range. Here is my example with that calculated field (Size)

1 Like

This looks interesting…certainly a better direction that where I was going…i will venture down this path and see where I get too! Appreciate both suggestions @snguyen and @Asz0ka!