E1: SEC: How to Setup Different System User IDS to Manage User Access to Tables in Database Based on Datasources
(Doc ID 1394856.1)
Last updated on NOVEMBER 14, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
According to JD Edwards EnterpriseOne Tools 8.9.x Security Administration Guide section Understanding How to Create and Revise User Security it states:
Each time a user accesses a table through a JD Edwards EnterpriseOne application, the software searches for a security record for that user and the specific data source where the table resides. If the software does not find a specific record, then it uses the default data source, which is the security record that you created with the DEFAULT data source field.
To accomplish this, you put records in P98OWSEC (User security) for this userID, as shown in this table:
|User ID / Profile||Data Source||System User|
|USERX||System - 900||JDE|
|USERX||Business Data - Test||JDE|
What should happen (according to the example given in the table above):
- If USERX needs a table that resides in System - 900, when E1 makes a connection to the database, the connection should be made with the JDE system user, independent of the system user SYSUSER associated to the DEFAULT data source for this user profile.
What is actually happening:
- For any tables that USERX needs (no matter what datasource the table is located), the system user "SYSUSER" associated to the DEFAULT data source is being used for all connections to the database.
Why is this happening?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document