Settings and Preparations
Purpose
As far as possible in the technical and business sense, the workflow scenarios can be run directly without any modifications. However, there are always some settings which must be entered in your system and which cannot be supplied by SAP.
Prerequisites
"Technical" Customizing for the workflow system
The Auto-Customizing function can be used to configure basic technical settings for the workflow system. The corresponding functionality is available both in SAP Business Workflow
Customizing and via Tools ® Business Workflow ® Development ® Utilities ® Customizing.Process Flow
Maintaining the organizational plan
The company-specific organizational plan describes the organizational assignment of an employee. This allows the responsibilities of employees for performing individual business activities to be defined in the form of activity profiles.
The organizational plan is part of the PD component "Organization and Planning". The organizational plan is maintained on a client-dependent basis. An organizational plan which was created for personnel management purposes (or is to be created) can be used in SAP Business Workflow without any changes, provided the workflow functionality and the personnel management application run in the same client.
Even if you wish to use one of the supplied workflow scenarios without making any changes, you must always define the organizational plan of your company. You only need to define those areas of the company in which you wish to use SAP Business Workflow. You should only differentiate individual jobs to the extent required by the different activity profiles.
The corresponding sections of this documentation contain proposals for organizational plans which have been adapted to the relevant scenario.
Agent assignment for single-step tasks
The SAP tasks supplied by SAP as part of the workflow scenarios are client-independent and their validity period does not expire.
Tasks must always be linked to their possible agents from an organizational point of view. It may therefore be the case that several employees with the same authorization on an organizational basis are offered the same task for execution. One of these employees assumes responsibility for and processes the task. This assignment principle supports automatic load distribution within work groups with the same activity profile.
The corresponding sections of this documentation contain proposals for linking the task in a scenario to the relevant employees.
Activating the triggering events for a task
Tasks can be started via events in response to status changes for an object. A task can have several triggering events. If one of the triggering events is generated in the system, the relevant task is started ("OR" operation).
If the task is used in a workflow, the workflow that contains the task as a step is not started by the event.
The triggering events of a task are entered in its definition. If you activate the triggering events, the system automatically activates the associated event receiver linkage
If the workflow scenarios described in this documentation are started via triggering events, this fact is mentioned in the relevant sections. If this is the case, the linkage between the triggering event and the receiver (task or workflow) must always be activated. This is usually carried out in Customizing, but can also be carried out later during production operation.
Customizing for individual workflow scenarios
Additional customizing activities will generally be necessary within the environment of the individual application scenarios. These are described in the following sections of this documentation.