implicit personalization wont work for POWL!
it would be easier if you go to POWL_QUERY and delete the entry for the
queries you want to hide, or go to POWL_QUERYR and delete the
application linkage, then transport the changes on those tables.
These tabs can be deactivated via transaction POWL_QUERYR, application
application OSA-POWL-MSS.
execute report POWL_D01 for all required users/application ID
combination and delete the cached results (by selecting the respective
query line item and clicking the delete button from the result/ output
list/ screen). Please select only the query for which you would like to
update parameters/ settings in POWL_QUERY.
Deleting the query using POWL_D01, only deletes the derivation of the
admin query for that query, which means the cache. The query will still
remain and will show up when the POWL is executed again by that user.
The queries aka the tabs are built dynamically at runtime by the POWL
framework. A tab header is constructed using the query description +
query count and tab tooltip is constructed from the tab caption
and the associated POWL type description.
The reason behind this kind of implementation is because no of tabs
visible for every user is not known until runtime. So any static
personalization thereby becomes invalid.
HAP_START_PG_POW_MSS_AC