Show TOC

Customizing POWLLocate this document in the navigation structure

Use

You use this process to customize POWL, with respect to your application, using POWL transactions.

This transaction is used for maintaining the POWL Type definition. It will register your feeder class in the following sequence:

  • Transaction POWL_TYPE

    1. Create a new POWL type.

    2. Assign your class (implementing interface IF_POWL_FEEDER ).

    3. Add a description. The description will be used within the POWL dialog for the user-specific query definition.

    4. Set the 'Sync' attribute in accordance with the kind of refresh required (If this attribute is set, a forced synchronous refresh of POWL_TYPE occurs. By default, POWL refreshes asynchronously.)

  • Transaction FPB_MAINTAIN_HIER

    This transaction is used to personalize hierarchy maintenance. Use this transaction to create your APPLID. You can setup a hierarchy of application IDs to represent your role or a set of roles.

Example

The table below lists a few application IDs:

Application ID

Description

Parent

OPS

Operations

No Parent

OPS-SALESREP

Sales Representative

OPS

OPS-SALESREP-W1

Worklist 1

OPS-SALESREP

OPS-SALESREP-W2

Worklist 2

OPS-SALESREP

OPS-SALESREP-W3

Worklist 3

OPS-SALESREP

  • Transaction POWL_CAT

    This transaction is used for maintaining POWL categories. Use this transaction to create or deliver administration categories. Categories are used in the POWL dialog to organize/classify worklists.

  • Transaction POWL_TYPER

    This transaction is used for maintaining POWL Type role assignment. Use this transaction to provide POWL with the feeder types that are available for APPLID. The feeder types available are Role or both.

  • Transaction POWL_TYPEU

    This transaction is used for maintaining POWL Type user assignment. This is similar to POWL_TYPER. In this type, queries are defined at user level instead of role level.

  • Transaction POWL_QUERY

    This transaction is used to maintain POWL query definition. Use this transaction to create or change 'admin' worklists. This query will be used for derivation when assigned to a user or an APPLID. This is a simple way for the administrator to define 'template' worklists for "n" users. The query templates can contain predefined selection values, special settings like read-only, quick search, and so on. You can create administration layout variants (now called views) for embedded WD ALV.

  • Transaction POWL_QUERYR

    This transaction is used for maintaining POWL Query role assignment. This is similar to the transaction POWL_TYPER, but used for queries (worklists). Create or change an entry for an admin query and assign it to an application context. These queries will be automatically derived when you start POWL for the first time. You can change the sequence of queries, assign categories, and activate/deactivate your assignments.

  • Transaction POWL_QUERYU

    This transaction is used to maintain POWL Query user assignment. See POWL_QUERYR, but this time at user level.