KB36909: Incorrect SQL and filtering is done when Security filters are set to be or joined, have to be evaluated as relationship filters and the subquery type is set to temporary tables

SYMPTOM:
Incorrect filtering is performed on a report for a user who is subject to multiple security filters when the following conditions are met.

1. The security filter must be applied through a relationship filter due to level differences
2. The security filters are set to be joined with an OR instead of an AND.
3. The Subquery type is set to temporary tables.

The SQL generates something similar to the pseudo SQL below.
 
Insert into filter1
select elements from table
where security filter1
 
Insert into filter2
select elements from table
where security filter2
 
select attribute, metric
from table
inner join filter1
inner join filter2
  
Now due to both joins being an inner join this means the filters are being applied in an and situation and only elements that both filters allow will be kept instead of elements allowed by either filter.
 
CAUSE:
This is a known issue with Strategy 10.
 
ACTION:
Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release. 
 
WORKAROUND:
To work around this issue the "Subquery Type" VLDB property should be changed to use something other then temporary tables as the subquery type.