Personal Worklist (Technical Information)

Use

The personal worklist provides users of the Enterprise Portal (assignment to a portal role or portal user ) with a list of tasks with specific business objects and the functions required for further processing.Users can define and save their worklists as queries .

An iView calls the requested worklist on a portal page or in a workset.For examples, see Worklist for Sales Documents . For more information about portal administration tasks and user administration, see Maintaining the Portal .

Note Note

The personal worklist is also referred to as follows in the Implementation Guide (IMG) and other documents:

POWL ( P ersonal O bject W ork l ist)

POWER List ( P ersonal O bject W ork E ntity R epository List)

End of the note.

Prerequisites

A worklist type (POWL type) is required for each personal worklist. A feeder class must be specified as the base information for the worklist type.

The standard system contains a group of worklist types. You can add other worklist types.

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.

Features

The content of worklists is structured thematically and created for a specific business object.

In the back-end system of an Enterprise Portal, the worklist type maps information about which business object can be processed using fixed methods.

The personal worklists are visible as queries in the Enterprise Portal.These queries can be registered for an individual user or a role.

Define worklists using existing worklist types

Worklists that are used in the standard system by the portal roles in the Business Packages are fully defined.For an overview of all the worklist types in the standard delivery, see Customizing for the Personal Worklist (POWL for SAP ERP 2005) under Configure Worklist Type Repository (transaction POWL_TYPE).

For these worklist types, you can create your own, more specific queries and assign them to individual users or roles.

  • You make the required settings in Customizing for the personal worklist .

    For more information, see Cockpit for POWL Administration .

  • Portal users can create new worklists or modify existing worklists by creating and editing queries in the Enterprise Portal.

    For more information, see New Worklist and Change Worklist .

Define worklists with company-specific worklist types

If you want to define worklists for business objects for which there are no definitions in the standard system, carry out the following steps for standard POWLs .

  1. Create a new feeder class for a standard POWL.Use the feeder interface IF_POWL_FEEDER in the standard system.

    For more information, see Feeder Implementation .

  2. You make the required settings in Customizing for the personal worklist .

    For more information, see Cockpit for POWL Admininstration .

  3. Create portal iView

    For more information, see Creating Portal iViews for POWL .

  4. Portal users can create new worklists or modify existing worklists by creating and editing queries in the Enterprise Portal.

    For more information, see New Worklist and Change Worklist .

Example

For a production order-related worklist, based on a predefined selection variant, the Production Supervisor (portal role) gets a worklist with planned orders for his or her area of responsibility within a plant. The worklist includes a workshop that is represented by all materials belonging to the same material class.

The production supervisor can now select one or more planned orders, convert them to production orders, release the orders, print the work instructions, and distribute the worklists to the responsible employee groups.