W_USERS_D T8402 /* Data Filter */

Actually I think you want to follow the steps described here: https://docs.oracle.com/middleware/12211/biee/BIEMG/GUID-1FDC0A15-9DE7-4838-9C0E-03290F5558B2.htm#dataaccess_db_level

It is not the correct way to apply row level security but you might want to check the logic table source of your FACT W_MEASUREMENTS_F to see if the row level security has been applied by joining to the other tables that way.

Hi,

I am asking you to open the table source for your fact and look at the Logical table there in.

Then double click on that and look at the physical tables that make up the logical table source.

If it is not there then check the physical table in the physical layer and see if anything has been applied in the WHERE clause in that.

Neither way is the correct way to apply row level security, but as you say that row level security is not applied in the conventional way, but your physical sql shows otherwise, the other tables must be entering into the relationship somewhere.

Yes, that is exactly it, delete it and all users will see all rows of data in that table, BUT, before you delete it - this is part of your security model, someone obviously put it there to apply a row level security in your OBIEE solution, don't you want to find out why BEFORE you remove it ??

I need "closure" after sticking with you until the end - did this resolve your issue?