POWL Reports: POWL developers and administrators can execute various reports for personal worklists (Personal Object Worklist, POWL). These reports help in updating the cache data, query information etc.
Table of Contents
The details of POWL reports are given below:
You can use this report to update queries. 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. This is a way of controlling the server load. Therefore you have to use the report POWL_WLOAD. You can restrict the asynchronous refresh to a chosen Logon/server group. If you check ‘Discard old cached results’ the cached results and the field catalog will be deleted.
The selection parameters stay constant (will not be deleted because otherwise it would mean that the queries will be deleted).
With Note?1456947.
POWL_WLoad report selects all the queries in system based on selection criteria provided by the user and updates the cache for all the queries. Some of the queries may be more frequently accessed than the rest. The user may wish to update the most frequently used queries so that the execution time of the report is less. Explanation of functionality: To selectively refresh the most frequently used queries, an option “Query last accessed in (days)” is provided.This is an optional parameter. This optional parameter is in inclusive of the other selection options already provided by the report. Note: POWL_WLOAD is a performance intensive report. It is not recommended that this report be used for frequent refresh.
This report deletes derived/ user defined POWL Queries from the cache based on Application Id and/ or User. It performs the following operations:
You can specify a selection for Application Id and/ or User. The report runs a check matching this selection and display the corresponding list of queries. Additionally, you can also decide if you want to display the results of your selection or you want to directly delete them without displaying it. The checkbox “Display Only” is used for this purpose,
The output of this report gives the following options:
This report shows the structure of POWL applications – the assigned POWL types, admin queries and feeder classes. It can be useful in following cases:
You can select the desired POWL applications two ways:
You can see blocks per POWL application ID. If selection based on roles was made, you can also see the role names and the names of the role entries referring to the POWLs. Each application ID is followed by POWL types assigned to that application ID with the corresponding feeder class. Below each POWL type all admin queries of that type are listed. Furthermore you can see admin queries that are assigned to the current application ID but the type of which is not assigned to that application ID. Below each query the type of the query and the corresponding feeder class are mentioned. The report provides also some additional information:
This report checks the mapping consistency and existence of POWL table entries – Application IDs, POWL Types and Queries. It performs the following checks:
You can specify a selection for Application ID, POWL type and Query and the report runs a check matching this selection. If you want the (query related) check to be performed only for those queries that were refreshed after a particular period, you can specify a selection for date and time with the checkbox ‘Chk If Query Refreshed After’ checked. Additionally, you can also decide if you want the check results of your selection saved to have it available for future reference. Any of these saved results could be deleted using report POWL_D05.
In addition to display of check results for current selection options, you can decide to:
Display your last saved results * Display any previously saved results (of any user) * Compare the results of current selection with any previously saved results and you can decide if you want to display all the results or only the differences * Compare any two previously saved results and you can decide if you want to display all the results or only the difference
This report deletes the selection criteria cache of admin queries based on the provided admin Query Id and/ or POWL Type. The output of this report is a transportable workbench request. Thus the report is intended for the administrators to delete any selection cache of admin queries before updating the query with new selections.
For example, consider a query ‘Flight Details’ was delivered with the .following selection (set using transaction POWL_QUERY). Carrier = ‘AA’. After the query is delivered, if the administrators or developers would like to add a selection to the query ‘Flight Details, for example, like the following Carrier = ‘AA’ and Connection Number = ‘0017’. To have this new change visible to business users during their query execution, the current cache has to be first deleted by running this report and then the selections have to be set again in transaction POWL_QUERY.
You can specify a selection for Admin Query Id and/ or POWL Type, the report runs a check matching this selections and deletes the cached selection criteria.
The output of this report gives the following options:
This report deletes POWL check results that were generated or saved previously using report POWL_D03.
Report POWL_D06 is used for activating the derived queries. This should be used when the admin queries (created using transaction POWL_QUERY and mapped to an application using transaction POWL_QUERYR) are initially inactive (Active flag in transaction POWL_QUERY is unchecked) and are activated at a later point in time. In such a case the derived queries for the initially inactive query will not be visible on POWL as the changes made to the admin query are not transferred to derived queries. After executing this report the derived queries would get activated.
You can specify a selection for Application Id, POWL Type and Master Query Id. In case derived queries of another user need to be activated, the user name field needs to be updated.
This report deletes derived/ user defined POWL Queries created in shadowing mode from the cache based on Application Id and/ or User. It performs the following operations:
Quick hint on what is shadowing mode: POWL queries are personalized queries that are locked for a user in a particular session. Meaning, when the same user opens the same query in the second session, the query is displayed in a disabled mode from the second session onwards.
This is the normal behavior of POWL. Nevertheless, in cases where same ‘User Ids’ will be shared across business users, it is critical to have the same query opened in N number of sessions in an enabled state to allow the users to perform their business operation.
This behavior can be switched on explicitly from the configuration and is referred to as ‘Shadowing Mode’ execution of POWL.
You can specify a selection for Application Id and/ or User. The report runs a check matching this selection and display the corresponding list of queries. Additionally, you can also decide if you want to display the results of your selection or you want to directly delete them without displaying it. The checkbox “Display Only” is used for this purpose,
The output of this report will show following:
You can use this report to delete layouts delivered by SAP/ created by an administrator (from the POWL_QUERY transaction). The output of this report is a transportable workbench request. This report mandatorily needs to be executed in the development client only.
Ideally, admin layouts (also called as variants) are created on a per query basis and delivered. If at a later point, the administrators would like to make a particular layout unavailable for users, it requires a deletion of the layouts which can be achieved using this report.
You can specify a selection for the application ID and the report retrieves all the queries mapped to this application ID for which layout variants were created by the administrator.
The output of this report gives the following options:
You can use this report to delete mapping of default layouts to queries created by an administrator (from the POWL_QUERY transaction). The output of this report is a transportable customizing request. This report mandatorily needs to be executed in the customizing client only. Ideally, ‘N’ admin layouts (also called as variants) could be created for a single query and one of these layouts is set as the default variant for the query. If at a later point, the administrators would like to reset/ remove this mapping or would like to validate if their layouts really exist in the system, this report could be executed to achieve the same.
You can specify a selection for the application ID and the report retrieves all the queries mapped to this application ID for which layout variants were created by the administrator.
The output of this report gives the following options:
All Credits goes to?POWL Reports
SAP ISU Tables for Technical master data, for Billing Master Data, Billing and invoicing Tables?…
SAP Fiori 3 UX and Design of SAP Fiori Apps for SAP S/4HANA, SAP TechEd…
Dunning is the business practice of informing a customer of past due payment. Dunning letters…
SAP AP Tcodes & SAP AR Tcodes: House Banks Tcodes, Advance Payments or Down Payments,…
What are the main SAP Payment Terms Tables ? What are the related Tables in…
Work center consists of master data related to routing of products. It contains data related…