E1: SEC: UDO: Enhancement Request for a User Defined Object View Security Report (Doc ID 3038229.1)

Last updated on JULY 30, 2024

Applies to:

Symptoms

In the current set-up, Security Workbench (P00950) is not utilized to grant or deny access via Application Security, Row Security, Column Security, etc., therefore the Security by Object report (R009501) nor the Security by User/Role report (R009502) meet the need or business report requirement. Additionally, Solution Explorer Menu Filtering nor Secured Task View is implemented therefore the Job Role-to-Task Relationship and Task View Print report (R90351) also does not meet the need or business report requirement.

Instead, Composite Pages are created based on a User or Role job duties. A User or Role, based on their duties, is granted access to a Composite Page via User Defined Object View Security. Composite pages are set up for General Ledger, Credit and Collections, Purchasing, etc. These Composite Pages define the module a User has access to, see below. For this reason, the business is requesting a new UDO View Security report which will provide a detailed or summary listing of User Defined Objects a User or Role has access to. 

P98220U - Work with User Defined Objects - an example of the Composite Pages set up based on job duties

An example of what a User/Role sees when they have access (UDO View Security) to a Composite Page (e.g. General Ledger)

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.