ALLOut Blog

 

Overcoming Multiple Role Issues in JD Edwards

Understanding Multiple Roles

What are the considerations and potential problems that can arise when using multiple roles in Oracle’s JD Edwards (JDE) EnterpriseOne (E1) solution? What are the available solutions within native JDE and how can ALLOut's toolset highlight any multiple role issues and automatically resolve them using the ‘Fix/Merge’ process and/or Super-Roles (CombiRoles)?

Security Hierarchy

Row Security in JD Edwards - A Balancing Act

Row Security can be a necessity for so many JDE implementations however, very detailed row security can result in excessive effort put into maintaining the security records as well as system performance issues.  It, like so many other security initiatives, is a true balancing act.

Compliance Does Not Stop at Segregation of Duties

Compliance efforts as they relate to security are often thought to end once Segregation of Duties has been achieved. In reality, that is just the beginning.  Really achieving compliance in system security includes managing access to confidential or critical information, ensuring only appropriate access is in place for all users, that changes are authorized and so much more.

Here’s the problem with most Security Audit Reports…

How does The Board and your top management assess the value of Security Audit reports to support their risk assurance?  What do you have to report on and what should you give them?

Three basic requirements of any audit report are as follows, and Security Audit Reports are no different:

Segregation of Duties Concepts

Segregation of Duties (SoD) is the concept of internal controls which attempt to ensure that no single individual has the authority to execute two or more conflicting, sensitive transactions with the potential to impact financial statements. Often these controls are to prevent a single individual from being able to carry out a complete process, without collusion from another individual. Read on....

Pages