Can it be useful? Sure… but just because you can doesn’t mean you should.
I say #NoThanks it doesn’t “smell” right. At first glance it would violate all security within Epicor which is one of the big selling points of BAQ’s. Poorly written SQL functions and procedures can wreck havoc on your DB… and in my experience the great majority of “BAQ” type users should not be entrusted with this power.
Maybe I’m old fashioned, I am also 100% against adding ANYTHING to the Epicor DB Stored Procs, Views, Functions etc they cause nothing but pain at upgrade time (been there done that) though Epicor has gotten better about it. There was a time where a wrong table or stored proc with the wrong name or naming convention would crash and burn your upgrade.
Again maybe its because I’m always thinking about the future and the next time the customer needs something. Can someone easily pick this up and figure out what I was doing and change it?
You can do something similar in the BPM Code (I won’t share it, you can figure it out on your own and if you break it don’t call me) but with the right call/object you can run straight SQL from BPMs… again a big ole NOPE to that one.