POWL_WLOAD and structural authorizations

[Micha_Reisner]

Hi,

We have an issue with the POWL mechanism for refreshing the user queries and preparing the result using the report POWL_WLOAD.

According to the documentation (POWL Reports - Web Dynpro ABAP - SCN Wiki) this report is meant to prepare the query results for users to provide cached results:

"If you schedule the report as a background job, for example, you can update the queries overnight. Users then have access to the updated data when they start work, without having to refresh the data themselves."

But:

Recently I discovered differences in the query results between the data which were prepared by the scheduled report POWL_WLOAD and the data after the user himself refreshes the query. Our analysis showed that the reason for this difference was because some data were filtered out from the result if the users refreshes himself. This happened because he was not allowed to access the belonging HR objects according to his structural authorization rules. Unfortunately the report POWL_WLOAD does not take the structural profiles of the processed users into account.

In this regard we do not dare to use the POWL_WLOAD report for preparing the query results if structural authorizations are in use. Because there is the risk that users get data which they should not be allowed to see. On the other hand forcing a refresh when the user access the POWL is in several cases too time-consuming.

Is there anything I am missing or does anybody have a solution for this inconsistant behavior?

Thanks for any input.

Regards
Michaela

[Former Member]

Hi Michaela,

Are you facing issue in auto refreshing the POWL inbox after the action taken on the work item or you want to generate any report on the POWL query.

If you want to auto refresh the POWL query, Could you please check the below configuration in your system.

Tcode POWL_QUERY-> Query Id ( based on you requirement ) -> select the check box 'Sync. call' and Refresh Type as 'On every List Visit'.

Regards,

Deviprasad

[Micha_Reisner]

Hi Deviprasad

No, it  is not about auto refreshing the POWL inbox.

It is about a custom report based on POWL. Unfortunately for some users the data selection takes a lot of time. Therefore we wanted to utilize the possibility of preparing the data at night. Which could be done by report POWL_WLOAD out of the box. With the described issue that the POWL_WLOAD does not reflect the structural authorization of the user it is running for.

Regards

Michaela