Technical Principles of SAP Business Workflow

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4f/41fed1dd88535ae10000000a421937/content.htm

Created on June 13, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 3
2014 SAP AG or an SAP affiliate company. All rights reserved.
 Table of content
1 Technical Principles of SAP Business Workflow

PUBLIC Page 2 of 3
2014 SAP AG or an SAP affiliate company. All rights reserved.
 1 Technical Principles of SAP Business Workflow

Use
The definition and execution of a workflow can be divided into four main areas. A user executes workflows in their Business Workplace where the work items
that they are allowed to execute are displayed. A workflow must be defined to be executed. To this end, a workflow definition is created in the Workflow Builder .
This definition contains steps that are executed at runtime. The steps either control the workflow directly or contain a reference to a task. The task refers to a
method of an object type in the Business Object Repository (BOR) and can be executed at runtime either automatically (background task) or by a user (dialog
task).

Business Workplace and Work Items

Work items are displayed to the user for execution in their Business Workplace. For example, work items represent a step at runtime that is to be executed. There
are various types of work item. Only certain types are displayed in the Business Workplace.
Workflow and Workflow Definition
You have to define a workflow before execution. This workflow definition is made up of steps that control the workflow or refer to the tasks to be executed. You can
make additional specifications about agents and deadline monitoring for a step. These specifications are evaluated at runtime by the work item manager . The
workflow is started either manually by the user or by the system. For the system to start a workflow, the workflow definition must contain at least one triggering
event (for example the event material created ). When the event occurs, the relevant workflow is started automatically.

When you activate a workflow definition, you automatically generate a runtime version. When the workflow is started (manually or automatically), the relevant
runtime version is used for the execution. If the workflow definition is changed later and a new runtime version is generated, these changes do not affect workflows
that are already being executed.
Tasks
Tasks describe elementary business activities. Tasks always refer to a method of an object type. Possible agents are defined for tasks. Tasks can refer to
automatically executable methods (background tasks) or they can require a user to execute them (dialog tasks).
Object Types and Objects
An object type describes the data with which you want to work in a workflow (for example the object type Material ). An object is an individual data record of an
object type. Attributes are defined for an object type, which make up its data record (such as material name , material number ). Every object type has
methods in which activities are defined that can be executed with the data (for example, create material ). You can call the transactions and functions of the
SAP System in a method, as can your own or other applications. Events are another important component of an object type. The events describe the status
changes that an object can undergo (for example, material deleted or material changed ). A workflow can be started by an event of this kind being
triggered.
The Business Object Repository provides an overview of all the object types in the SAP System. You can use or extend the existing object types as well as
create new object types.

PUBLIC Page 3 of 3
2014 SAP AG or an SAP affiliate company. All rights reserved.