Performance and Workflow - Part 1

Details

Category: Workflow

Published on Sunday, 27 July 2008 16:29

Written by Kevin Wilson

Hits: 10442

General

• To avoid an unnecessarily high number of tRFC calls during workflow implementation, some activities of the workflow runtime system, such as data flow or processor determination, are carried out under the userid of the person responsible instead of under WF-BATCH.

NOTE: Remember to assign this user the necessary authorizations, in particular for the HR authorization object PLOG. Assign more authorizations to the person responsible (for example, for PLOG we recommend the profile P_PLAN_ALL) or add empty background steps to your workflow definition (for example, based on the single step task TS30000044, object type WFTS, method EMPTY_BACKGROUND). Ultimately, there is a trade-off between security and performance. (See SAP Note 755767)

Note: The background user for the workflow runtime system or a user who creates an event always occupies a work process if a transactional RFC is sent. This occurs during the following actions in workflow:

• When starting event receivers (that contains exiting an asynchronous method).
• When starting a background step whose predecessor was not exited by an event. 

Inbox

• The selection time of work items in a user inbox increases with the number of tasks which the user may process.
• The selection time also increases with the number of available work items.
• Data of a work item may have to be read by the database.

• < Prev
• Next >