Video Transcript
This is a brief demonstration of some ALLOut tools for security simplification. Specifically, the tools aid in data cleanup and streamlining, which can reduce mistakes and enhance system performance. Remember, it’s all about the data, and since much of the data associated with JD Edwards access is interconnected, the entire structure must be considered as changes are made. Otherwise, updates will result in orphaned and redundant records.
If you suspect or know that you have some of these orphaned or redundant records, consider the following ALLOut tools to help clean it up. Since the cleanup tools are not used frequently, we’ve put them into the Objective Implementation section of our ALLOut menu. From the user’s roles and upgrading tab, we can manage cleanup, workbench, and run the UBE to delete unused users. And from the JDE security restructuring tab, we can run the UBE to delete security by user or role and the UBE to delete redundant security. Let’s take a look at each of these, beginning with the cleanup workbench, which can be used to identify and sort out data discrepancies through a grid interface. Using this grid, we can gain immediate insight into users, roles, security, and related data. For each user or role, we can tell whether particular data exists or not. This can help us to identify cleanup opportunities such as roles without menu filtering, user-level security, and unassigned roles. And once the opportunities have been identified, mass updates and deletions can be made using the row exits and form exits. These updates occur immediately, similar to running SQL updates at the database level.
Next, let’s look at the UBE to delete unused users. By running this UBE, you can identify and even delete unused users from your JD Edwards system. Automatically, the interactive interface guides us through the filters and options. We can filter by user range and filter lists based on user login activity. In final mode, users will be deleted or disabled, as with other ALLOut UBEs. The first page documents the reporting parameters. The subsequent pages reveal unused users to be removed if the UBE is run in final mode.
Next, let’s look at the UBE to delete security by user or role. This one is ideal for removing one or all security types for a set of users or roles, while also producing a list of the records being deleted. The interactive interface guides us through the options. In addition to user or role ranges, there are more filtering options available here, and depending on your cleanup objectives, you can delete all standard and UDO security or select the security types individually. As with our other updating UBEs, it can be run in proof or final mode. The resulting report lists security records to be deleted in final mode.
Finally, let’s take a quick look at the UBE to delete redundant security. To achieve simpler management and better system performance. Using the interactive interface, we can identify unused, duplicated, and/or unnecessary security records and delete or simply report on those records. The first page of the report documents the options selected, as well as a legend to explain statuses and colors. Subsequent pages reveal records that will be deleted in final mode, along with insight on records that need to be retained to maintain the current effective security.
For more detailed guidance on this and other ALLOut features, please visit the ALLOut Academy.
Discover our industry leading expertise
Industry Insights
Feeling the Risk in an Oracle Licensing Audit
How much risk do you want to take on an Oracle License Audit? Oracle identifies each customer’s pricing model by looking at any exist