BICS: Data Filters and BI Cloud Service Administrators Role

Similar to the on-Premise.rpd File, Data Filters can be configured using the Oracle BICS web modeller. These Data Filters are added to the Analysis to apply a particular data visibility for respective Application Roles. E.g. Users belonging to Application Role “Sales Managers West” should only be able to see data from the West Region, but not middle or East.

Within the web modeller of BICS this can be done using the Data Filters Tab on a Dimension or Fact logical table:


This is similar to OBIEE’s .rpd file, where the Data Filters have been defined also on the Application roles:


Once, the logical Dimension Table is used within an Analysis the defined Data Filter is appended for the defined Application Roles to the Analysis to restrict visibility as row level security.

However, if the User is also a member of the BI Cloud Service Administrators Role then the Data Filters are not applied. Users who are members of this Role are not restricted in terms of data visibility.



fixing: Data filter expression VALUEOF(NQ_SESSION.”variable”; for Applicaton Role is considered as non conditional, error: [nQSError: 23006]

After migrating from Oracle BI EE 11g to Oracle BI 12c the RPD consistency checker shows the following Error message with Error # 38197:

Data filter expression VALUEOF(NQ_SESSION.”variable”) for Applicaton Role is considered as non conditional, error: [nQSError: 23006] The session variable, NQ_SESSION.variable, has no value definition
Within OBI EE 11g consistency checker this was neither thrown as a Error message nor as a Warning.

Within the consistency checker of 12c, this is throwing as a error. To fix this a default value needs to be specified for each variable besides the Authorization Block. For this go to Manage| Variables |  Session |Initialization Blocks and double click on a Name e.g. Business Groups.

And open “Edit Data Target” within the variable Target area and assure that the Default Initializer as a default value as shown below:
After running the consistency checker again, the error message disappears.