1. Menu security - not really. You can assign a user profile, or their group, a top level menu. From memory, they cannot get above this menu without access to Menu Search and Select (not P0082 I think, but try starting with this one and see where it takes you). But this isn't really security, it's just making it difficult for them to get to these other menus. Plus you need to make sure you have a set of menus for each group, which just becomes a maintenace hassle. Don't do it.
2. Version security - you'd need to use row security on the F98305 or F983051 (the latter I think) table, but that's a REALLY BAD BAD BAD IDEA. Again, don't do it.
Ultimately, if at all possible, just let users access all menus (to reduce maintenance hassles) and don't use row security on the versions table. If there are only a small number of report versions you want an individual group to have, put them onto a new menu and attach the remaining menus to this one as well (er this didn't make sense, but I'm too tired to explain it better). Again, not great. Basically JD Edwards should sort out version security...
We use Processing Option security to prevent users from prompting for versions, and thus having to take the version assigned to the menu. This is a nice little extra help, and solves 80% of the problem. But obviously not all of it...
The only real current solution is to create copies of your UBE, and create the versions as you see fit for each copy, then securing using Application security each copy. Not brilliant (and again, a maintenance hassle), but workable.
