A user is notified of the existence of work items they are to process in a remote R/3 System by a work item in their Business Workplace. The work items in the other R/3 System form the remote worklist of this user with regard to the current system.

When the user executes the notification work item, the system calls the user's Business Workplace in the remote system without any additional logon. The user can then process the work items in the remote system.

• Once the user has processed their remote worklist fully, the notification work item immediately disappears from the current system.
• If the user has only processed their remote worklist partially, the notification work item remains in the current system with the status in process.

The current system, in which the user is notified of a remote worklist, is referred to as the client system.

The system in which the work items in the remote worklist are to be executed is known as the server system.

The user must have the same R/3 user name in both the client and the server systems.

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:

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 notification work item is executed by the recipient in the client system, the system calls their current worklist in the server system via RFC. The worklist may not exist anymore on the server system. This situation may arise if there was a remote worklist but it has been processed in the server system and the report has not been run again there in the mean time.

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.

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.

You schedule a report periodically in the server system, which 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.