Is it possible to view items that might be set on menu security through a BAQ? Instead of the slow chug of in/out of each security item to see if something is or is not set, this data has to live somewhere?!? Right?
There is a built-in Menu Audit Report that may have the details you need. Otherwise you will have to build your own BAQ. The menu security information is stored in Ice.Menu and Ice.Security.
The report is erroring out 
When I try to create the BAQ with ice.menu and ice.security I’m not sure how to connect them and I’m not seeing where I can tell which group may or may not have access.
I will open a ticket on the report error, but if you can give guidance on the BAQ in case that ticket takes a while.
I am sure this topic has been raised before and if your search here I am sure there may already be a BAQ posted…
The tables involved are ice.menu ice.Security from ice.SecGroup
Join on the menu.seccode and security.seccode
Point to note there is a 1-many relationship between seccode and menu. So it is possible to change the entrylist on one seccode and effect many menu items. Welcome to Epicor menu security.
in ice.security the EntryList and NoEtnry list drive it. if you want specific users or groups to have access rather than all then * would need to be replace with a ~ delimited list of the groups and users.
1 Like
This seems like the buried lede to the story. Why is it erroring out? Before jumping into custom stuff, you should get the stock functionality working.
2 Likes