Remote Worklist (SAP Library - WebFlow Engine (BC-BMT-WFM))

Remote Worklist

Use

If you are a recipient of a work item that is created in a remote SAP System, you can be notified in the system you are currently working in. The SAP System creates a notification work item in your current Business Workplace. The work items in the other SAP System form the Remote Worklist with regard to the current SAP System.

When you execute the notification work item, the system calls your Business Workplace in the remote system, without any additional logon. You can process your work items there.

When you have completely processed your remote worklist, the notification work item is automatically deleted from the current system.

If you have only partially processed your remote worklist, the notification work item remains in the current system with the status in process.

Integration

The system you are currently working in, and in which you are notified of a remote worklist, is referred to as the client system.

The system in which you execute the work items in the remote worklist is known as the server system.

Prerequisites

You must have the same SAP user name in both the client and the server systems.

Features

Each server system has a subscriber table that specifies who wants to be informed in which client system of the presence of work items in the server system. The system executes a report periodically in the server system, which checks the following for each subscriber in the subscriber table:

Whether there are any work items for them in the server system

Whether there is already a notification work item for them in the client system

The following possible scenarios result:

	There is already a notification work item in the client system.	There is not yet a notification work item in the client system.
There are work items (and therefore a remote worklist) in the server system.	Since the user has already been notified, no further action is necessary.	The system creates a work item in the client system, which notifies the subscriber of the existence of their remote worklist.
There are no (more) work items in the server system.	The system deletes the work item in the client system.	No action is required here.

The notification work item in the client system is always created after the associated remote worklist. The maximum time delay is equal to the period with which the report runs in the server system.

When the recipient executes the notification work item in the client system, the system calls their current worklist in the server system by RFC. It is possible that a worklist no longer exists in the server system. This situation may arise if the remote worklist has been processed in the server system in the meantime, and the report has not been executed again there since.

Activities

You create a logical RFC destination in both the client system and the server system, each of which refers to the other system. In this way, you tell each system what the other system "is called" and how it is to be called. For more information, see Creating a Logical RFC Destination.

The server system contains a subscriber table, which specifies which users in which system are to be notified when a work item is created for them in the server system. Depending on your enterprise organization, this entry is made either by a system administrator or by each user. For more information, see Specifying Subscribers.

You schedule a report periodically in the server system that determines whether there are work items for each subscriber in the subscriber table and, if necessary, creates notification work items for them in the client system. For more information, see Scheduling a Report.