E1: SEC: Setting Up Business Unit Security Using P95300 Does Not Create Row Security Records in Security Workbench Table F00950
(Doc ID 2860292.1)
Last updated on APRIL 01, 2022
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
When using Business Unit Security application (P95300) to set up Business Unit security, it does not create the Row Security records in the Security Workbench table (F00950).
NOTE:
Beginning with EnterpriseOne 8.11 and above releases, there is a new application P95300 which provides a way to create Row Security records for Business Unit, but this application provides no new functionality other than a different way to create Row Security records in the Security Workbench table F00950. It works on the assumption that Inclusive Row Security is being used and lacks the logic to enter secured ranges. For example, if you want to allow a user access to business units 1- 10, the P95300 application will create ten F00950 records, with From/Thru ranges of 1-1, 2-2, 3-3, ..., 10-10. Because of the slow performance that will result from this, it is NOT advised to use P95300 to manage Inclusive Row Security on Business Unit. Instead, it is recommended to define Row Security directly within the P00950 Security Workbench application.
Beginning with EnterpriseOne 8.11 and above releases, there is a new application P95300 which provides a way to create Row Security records for Business Unit, but this application provides no new functionality other than a different way to create Row Security records in the Security Workbench table F00950. It works on the assumption that Inclusive Row Security is being used and lacks the logic to enter secured ranges. For example, if you want to allow a user access to business units 1- 10, the P95300 application will create ten F00950 records, with From/Thru ranges of 1-1, 2-2, 3-3, ..., 10-10. Because of the slow performance that will result from this, it is NOT advised to use P95300 to manage Inclusive Row Security on Business Unit. Instead, it is recommended to define Row Security directly within the P00950 Security Workbench application.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |