E1: SEC: CASE STUDY - Programs Run Slower After Setting Row Security Against F0901 (Doc ID 2013877.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Symptoms

 

One of UBE (which computes Account Balance for all transaction daily basis for all accounts in EnterpriseOne) with row security performs 4 times slower than same report without having row security.

Security Policy: Inclusive row security

User / Role Object Name Object  Description From Value Thru  Value Security  Type Description Data  Item Alias View Add Change Delete
UserA F0901 Account Master 00100 00100 4 Row Security Company CO Y Y Y Y
UserA F0901 Account Master 00150 00150 4 Row Security Company CO Y Y Y Y
UserA F0911 Account Ledger 00100 00100 4 Row Security Company CO Y Y Y Y
UserA F0911 Account Ledger 00150 00150 4 Row Security Company CO Y Y Y Y
UserA F0902 Account Balances 00100 00100 4 Row Security Company CO Y Y Y Y
UserA F0902 Account Balances 00150 00150 4 Row Security Company CO Y Y Y Y

Use any users belonging to role/user UserA that can SELECT, INSERT, UPDATE and DELETE when F0901.CO, F0911.CO, F0902.CO IN ('00100', '00150').

Note that this document is case study only, so it is not meant to encompass all slower performance with row security. However you may try to implment same solution given here.

 

 

Changes

Row security is newly set against tables F0901 (Account Master), F0911 (Account Ledger) and F0902 (Account Balance).

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms