Skip to Content

RLR security not working with LOV based on custom SQL in IDT

Hi All,

I have applied LOV based on custom SQL to achieve "Index Awareness" in IDT. But after applying "LOV based on custom SQL" RLR is not working.

I am using SAP BI 4.2 IDT

Thanks in advance.

Regards,

Jeet

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Nov 21, 2016 at 04:33 PM

    Hi Jeet,

    Does RLR mean Row Level Restriction (Row Level Security)? If yes, then you've answered your own question. Row Level Security will restrict the values displayed in the LOV and in the result for a certain object. But if you use an LOV based on Custom SQL, seems its not honoring the Row Level Security you setup. Try to remove the RLR and check what happens. Also, why do you need LOV based on Custom SQL to achieve Index Awareness? Please share additional details.

    Thanks,

    Mahboob Mohammed

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 22, 2016 at 06:51 AM

    HI Mohammed,

    Thanks for your replay.

    Does RLR mean Row Level Restriction (Row Level Security)?

    Yes i am discussing Row Level Security.

    LOV based on Custom SQL, seems its not honoring the Row Level Security.

    I agree

    Why do you need LOV based on Custom SQL to achieve Index Awareness?

    For Performance tuning i am using Index Awareness Prompt.

    I have follow the steps as per SAP document : https://archive.sap.com/documents/docs/DOC-45263

    Is there any anther way to achieve index aware prompt and Row Level Security both at same time.

    Regards,

    Jeet

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 25, 2016 at 01:32 PM

    Hi Jeet,

    Does LOV based on existing Universe objects not help in Performance Tuning? I'd assume you should have index awareness set on that object, without caring about how is its LOV being created.

    Can you please follow this Index Awareness blog to set it up?

    Thanks,
    Mahboob Mohammed

    Add comment
    10|10000 characters needed characters exceeded