What are the advantages of generic or next-number role names versus intelligent names for security r
Hello Community,
I am not sure to which community I should address this question. We are bringing several divisions and companies onto JDE E1 9.0 from either JDE World or from third-party software. Our security manager is leaning slightly toward an almost generic role naming convention; for example, A001, A002, A003, etc., where the first letter "A" would be the roles that were created for this release 9.1 and for the rollout to this group of companies.
The security manager likes this design for multiple reasons, one of which is that the role description can be changed as needed when the internal business process changes and the security manager would not have to create a new role name. I have always used "intelligent" role names, such as APDAILY, APMGR, etc., and I don't know of any disadvantages to the security manager's suggestion, but I wanted to ask the Oracle community about the advantages and disadvantages of either naming convention.
I am not sure to which community I should address this question. We are bringing several divisions and companies onto JDE E1 9.0 from either JDE World or from third-party software. Our security manager is leaning slightly toward an almost generic role naming convention; for example, A001, A002, A003, etc., where the first letter "A" would be the roles that were created for this release 9.1 and for the rollout to this group of companies.
The security manager likes this design for multiple reasons, one of which is that the role description can be changed as needed when the internal business process changes and the security manager would not have to create a new role name. I have always used "intelligent" role names, such as APDAILY, APMGR, etc., and I don't know of any disadvantages to the security manager's suggestion, but I wanted to ask the Oracle community about the advantages and disadvantages of either naming convention.
0