Page tree
Skip to end of metadata
Go to start of metadata


Users are experiencing performance problem, time out on POWL screen. This page is created to identify the route cause of performance problems and provides further recommendations to improve POWL performance.


SRM POWL performance issues can caused by:

  • improper usage of the functionality,
  • amount of data,
  • authorizations,
  • PD locks and indexes,
  • missing performance corrections (SAP Notes).

Index tables

Index tables are help to improve the system performance when you create or display a large document lists. If these tables are not in use, the system needs to read unnecessarily large volumes of data in staggered database accesses. In case of POWL search is important to make sure that the indexes are used properly. For more information please check SAP Wiki page Index Tables.


The execution of unrestricted queries is time consuming and, in most cases, unwanted. Therefore, SAP delivers most of the queries with a default timeframe of the last 30 days. To avoid performance problems due to very large result sets, we recommend that you restrict the Administrator Queries even more, depending on the use case of the queries. Use the transaction POWL_QUERY to restrict the query results and, by restricting the query results in this way, you can avoid performance problems on the initial refresh.

Query Configuration Recommendations

To avoid performance problems please follow the following recommendations:

  • Define queries with the selection criteria pre-filled org data to minimize the result list (e.g. purchasing org, purchasing group, plant, document type).
  • The queries would need to be role or user assigned.
  • Define the query settings such that key attributes are made mandatory and will therefore require entry prior to the query being executed


We recommend limiting the number of active queries for each POWL. Only queries relevant to the user’s daily work should be defined by the system administrator. Since POWL caches queries per user, too many unnecessary queries could lead to unnecessarily high memory consumption. It is possible to restrict user authorization to create new queries using the authority object CA_POWL Field POWL_QUERY. The recommendations are the following:

  • Remove access to define new queries.
  • Remove access to define new queries for specific Application ID's.
  • Allow  users to define new queries, but only with reference to an existing template - ensuring that a mandatory criterion is inherited.
  • Prevent users from being able to "refresh all" queries.
  • Turn off Sync mode of POWL Types.


You can schedule the POWL_WLOAD report to refresh the queries nightly, based on POWL application, query, user, or feeder type. This avoids the ‘morning refresh’.

We strongly recommend restricting user access to the Refresh all button. You can do this using the authority object CA_POWL Field POWL_RA_AL. This authority object determines if the user gains access to a "Refresh all" button, which triggers a simultaneous refresh of all queries that are active on the POWL iView identified by POWL_APPLID. Note: This may cause a high system-load on the application server group used for refreshes on this POWL iView.

For further details please check SAP SCN Wiki POWL Automatic Refresh.

Sync call setting in transaction POWL_TYPE

This flag determines whether the execution/ refresh of query should happen in synchronous or asynchronous mode. What it means is, in case of synchronous type, query is always executed in the same application server in which the POWL application is executed. Hence, in case of larger results in a Worklist numerous business users running POWL at the same time, this sync setting is not recommended as it results in poor performance and sometimes even a dump due to memory overflow.

If this is set to asynchronous (meaning sync flag is unchecked), the query execution happens in any of the available servers of the server group remotely in a separate task. Hence, this is recommended to overcome any performance issue with refresh of huge result lists.


Improper BAdI implementations can also cause performance problems (handling of search criteria or search result). Please check the following SAP SCN Wiki pages about the POWL BAdIs:

BD_POWL_CHNG_SEL_RSLT - Change Selection Result of POWL Search in Feeder
BD_POWL_CHNG_SELCRIT - Change the list of possible selection criteria in the POWL feeder
BBP_WF_LIST - Change Worklists and Search Results Lists

Related Content

Related Documents

SAP SCN Wiki - Index Tables
SAP SCN Wiki - POWL Automatic Refresh
SAP SCN Wiki - BD_POWL_CHNG_SEL_RSLT - Change Selection Result of POWL Search in Feeder
SAP SCN Wiki - BD_POWL_CHNG_SELCRIT - Change the list of possible selection criteria in the POWL feeder
SAP SCN Wiki - BBP_WF_LIST - Change Worklists and Search Results Lists