E8.12 Business Unit Security - GH9052, P95300, P00950

[Rauf]

I was using P00950 all the time to setup row security.
Recently, I came to know that P95300 can be used to setup the security for Business Unit.
Anybody have links to explain this more ? The below links just explains but I need little more info. ( My basic question if P00950 is enough, why should we go for P95300 ?)
Note: We are using Exclusive Row Security.

https://docs.oracle.com/cd/E17984_01/doc.898/e14717/business_unit_security.htm

 

[Rauf]

E1: SEC: Setting Up Business Unit Security Using P95300 Does Not Create Row Security Records in Security Workbench Table F00950

JD Edwards EnterpriseOne Tools - Version 9.2 and later: E1: SEC: Setting Up Business Unit Security Using P95300 Does Not Create Row Security Records in Security Work

support.oracle.com

 

[Luke Phillips]

Hi Rauf,

In JD Edwards EnterpriseOne (E1) security setup, P00950 and P95300 serve different purposes and are used in different scenarios. Here’s a brief explanation:

1. P00950 (Security Workbench): This application is typically used to manage user and role-based security, including object, action code, and row security. It allows you to set up security rules that restrict or allow access to specific applications, reports, and data within JD Edwards.
2. P95300 (Business Unit Security Maintenance): This application specifically focuses on business unit security, which is converted into row security within the database. It provides a more detailed and focused interface for managing row security rules, which control access to specific rows of data within a table. This can be particularly useful when you need to apply complex or granular security rules at the row level.

Why Use P95300 Alongside P00950?

• Granularity: P95300 offers more granular control over row security, which might be necessary for complex security requirements that cannot be efficiently managed through P00950 alone.
• Ease of Use: For users who frequently modify row security, P95300 provides a user interface that might be easier to navigate for row-specific settings.
• Specialized Tools: P95300 might offer additional tools and options tailored specifically for row security management, which are not available in the general security workbench (P00950).

Exclusive Row Security
Since you are using Exclusive Row Security, it's important to note that any changes in methodology (from Exclusive to Inclusive or vice versa) require careful consideration, as existing row security settings will not automatically convert and may cease to function as intended. Testing and validation in a controlled environment are crucial before implementing changes in the production system.

Our tools are focused on facilitating all of the above including: identifying which tables are required, expediting inclusive to exclusive conversion and allowing you to segment your company security in dedicated roles prior to merging them.