Auditing changes within E1 can seem daunting! But you can easily audit your History Table for User, Role or Menu changes and identify what was done, when, by whom. Your auditors and going to love this!
Row security in JD Edwards (JDE) EnterpriseOne (E1) is used to protect the data in tables from being viewed and/or updated by unauthorized users. There are two strategies for implementing Row security (Exclusive or Inclusive). While Exclusive can be used to “Manage Exceptions” and the E1 installation defaults to this setting, Inclusive is considered the stronger method for effectively managing data security for a true closed system and to ensure a more painless audit.
The strategy for managing data security is a system setting so one method of the other must be selected and Exclusive is considered the industry standard.
Over time there are frequently Users or Roles in your system that are no longer used, but they still have records associated with them.
Regular maintenance of your User and security tables will help keep your system streamlined and running at peak efficiency. In addition, keeping your User count low may have licensing impact with Oracle.
... or perhaps you will?!
"How is this going to be beneficial to me?"
"Here we go again, advice from people who don't know our business like me"
"This is going to be soooo time consuming"
So why not get ahead of the game and run a DIY Audit first?