Start of Content Area

Process documentation Settings and Preparations Locate the document in its SAP Library structure

Purpose

As far as possible in the technical and business sense, the workflow scenarios can be run directly as shipped by SAP without any modifications. However, there are always some settings which must be entered in your system and which cannot be supplied by SAP.

Prerequisites

Customizing for the Workflow System

To make the workflow system in your SAP system function, you need to execute Structure linkautomatic workflow Customizing. This function can be used to check the basic technical settings, and change them if required. Automatic Workflow Customizing is located in Customizing in the SAP system or under Tools ® Business Workflow ® Development ® Utilities ® Automatic Workflow Customizing.

Process Flow

Maintain organizational plan

The enterprise-specific organizational plan describes the organizational assignment of the employees. The aim of this is to determine the responsibility of employees for the execution of individual business activities in the form of activity profiles.

The organizational plan is maintained on a client-dependent basis. An organizational plan created (or to be created) for HR purposes can also be used in SAP Business Workflowas long as the workflow functionality and the HR application are in the same client. If you have set up an organizational plan in a different client or a separate HR SAP system, you can use report RHMOVE30 to copy this data to the client of the SAP system in which the Workflow is to be executed.

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 the Workflow. You should only differentiate individual jobs to the extent required by the different activity profiles.

Note

The corresponding sections of this documentation contain proposals for organizational plans which have been adapted to the relevant scenario.

Agent Assignment for SAP Tasks and Workflows

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. If you use objects of organization management (for example, organizational units) when assigning, you can offer several employees with the same authorization on an organizational basis the same task for execution. If the SAP task is used in a Workflow, you also have the option of defining responsible agents.

Note

The corresponding sections of this documentation contain proposals for linking the task in a scenario to the relevant employees.

The SAP workflows supplied by SAP are client-independent and their validity period does not expire. If SAP Workflow is to be started directly by a user (for example, by using the transaction Start Workflow), you must define possible agents for the Workflow. These are then authorized to start the Workflow directly.

Activating Triggering Events

Workflows and tasks can be started via events in response to status changes for an object. A workflow or a task can have several triggering events. If one of the triggering events is generated in the system, the relevant receiver is started (‘or’ operation). If a task has an active triggering event, when the event occurs, only the task is started as a single-step task. Workflows that contain steps that reference this task are not started.

The event that triggers a workflow or a task is entered in the relevant definition. When you activate the triggering events, the system automatically activates the relevant event-receiver linkage.

Note

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 IMG activities will generally be necessary within the environment of the individual Workflow scenarios. These are described in the individual Workflow scenarios.

 

 

End of Content Area