Intelligent security role names versus generic or next number role names

rkarnap

Active Member
Hello List,

I hope that I am posting to the appropriate forum. My client is currently using JDE E1 9.0 for some of its companies and is preparing over the next 12 months to roll out JDE E1 9.0 to some of the companies that are now using either World A7.3 or third-party software.

The security manager is leaning slightly toward using generic role names; for example, A001, A002, etc. Among his reasons is that he could modify the description of the role to meet changing circumstances without having to create a new role name. The only intelligence he wants is the first letter of each role name, where "A" would be for the initial creation of the new role names. Then "B" or "C" would be any roles that might be needed either from adding a new company, or from upgrading to a new Tools release, or upgrading to Release 9.1, etc.

I have always used "intelligent" role names; for example, APDAILY, APMGR, etc., and I am not aware of any significant advantages or disadvantages of either naming convention.

Thanks in advance for any comments.
 
Back
Top