Show TOC

 Settings for Personal Worklists (Standard POWL)

Purpose

If you want to use personal object worklists (POWL) in the portal, you must make certain settings in Customizing.

Note Note

Because of the technical data that is processed for the personal worklists, as well as the standard POWL there are two technical POWL types: the reporting POWL and easy POWL .

For more information about the technical POWL types, see Cockpit for POWL Administration .

End of the note.

Prerequisites

The feeder class of the worklist has been defined. The feeder class is registered in the POWL repository, and the personalization hierarchy has been defined in Customizing for the personal worklist .For more information, see Feeder Implementation .

Process Flow

Settings in Customizing

You make the settings for the personal worklist in the back-end system by choosing Start of the navigation path Cross-Application Components Next navigation step General Application Functions Next navigation step Generic mySAP Suite Functions Next navigation step Personal Object Worklist. End of the navigation path

You can process the technical data as follows:

  • You can use the Cockpit for POWL Administration .

    The cockpit contains all processing steps grouped into one IMG activity. You can also start a report straight from the cockpit to check the completeness of the POWL design information.

  • You process the data using the individual IMG activities as listed below.If you want to check whether the data is complete, you must start report POWL_D02 (Display POWL Design Information) separately.

Start IMG Activities Separately
Worklists in the standard system

If you do not define new worklist types in your company but only use the worklists in the standard system, carry out the following activities:

  1. You define categories .The categories are used on the portal interface as an organizational structuring element for the queries. Queries that are assigned to a category appear together in the same block. Under the personalization data, portal users can assign a query to a category based on their tasks.

    You make these settings in Customizing under Define Categories (transaction POWL_CAT).

  2. You create standard queries (content for your personal worklist).

    If you do want the user to have an empty personal worklist, you must create standard queries and assign them to the responsible roles or directly to the user names.

    You make these settings in Customizing under Define Standard Queries (transaction POWL_QUERY).

  3. So that the queries are clearly visible in a category, you must assign the category to the standard query.

    You make the settings in the following activities in Customizing:

    • Define Query Visibility at Role Level (transaction POWL_QUERYR)

      You assign a query to a role in this activity.

    • Define Query Visibility at User Level (transaction POWL_QUERYU)

      In this activity, you assign a query to a user.

  4. You make the required settings to make your worklist type visible for your user role or user group.

    You make the settings in the following activities in Customizing:

    • Define Visibility of Worklist Type at Role Level (transaction POWL_TYPER)

    • Define Visibility of Worklist Type at User Level (transaction POWL_TYPEU)

  5. You can edit the settings for the personalization application hierarchy. For more information, see Feeder Implementation .

Company-specific worklists

If you have defined new worklists (feeder class) in your company, you must register the worklist type and define the application hierarchy before you carry out the steps listed above.

For more information, see Feeder Implementation .

Scheduling queries

The results of all user queries (worklists) from the personal worklists are cached in an internal cluster table. The results of the feeder class method GET_OBJECTS are stored in the cache. The personal worklist always reads the cache – regardless of the how the Activate Synchronous Query Updates indicator is set ( Define Worklist Repository or Define Standard Queries activity) . The user can display the current worklist by choosing Refresh .

The administrator can use the cache to schedule worklist creation and create a worklist overnight, for example. Worklist creation can be scheduled in the back-end system using the report POWL_WLOAD (Refresh Active POWL Queries ).

Authorization check

You can control processing of the personal worklists (Personal Object Worklist, POWL) for the individual application areas (application ID).

For more information, see Assign Authorizations (Standard POWL) .

Reports for managing queries

For an overview of reports that can be used by POWL administrators to analyze and process the POWL data, see Reports for Personal Worklists .

Business Add-Ins (BAdIs)

The BAdI definition BADI_TYPE_CUST allows you to change the POWL types at runtime.

The POWL runtime calls the implementation of this BAdI definition and makes the visible POWL types, application ID, user name, and system language available according to the listed POWL application. The implementations can change the POWL types and return them to the framework.

You can create the implementation for this BAdI in Customizing for the Personal Object Worklist under BAdI: Visible POWL Types .

Error page

If an error occurs when the user calls a personal worklist, the system generates an error page with adump analysis. You can now design your own error page.

The administrator can create an application configuration and set up the URL of the customer-specific error page as the attribute Error Page URL . Without this setting, the dump analysis is displayed based on the standard setting.