BIT601
SAP Workflow – Definition and Use
of Customer-Specific Workflows
SAP NetWeaver

Date
Training Center
Instructors
Ed...
Copyright
Copyright © 2007 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in an...
About This Handbook
This handbook is intended to complement the instructor-led presentation of this
course, and serve as a...
About This Handbook

BIT601

Icons in Body Text
The following icons are used in this handbook.
Icon

Meaning
For more info...
Contents
Course Overview ......................................................... vii
Course Goals .........................
Contents

BIT601

Unit 9: Events and Workflow ......................................... 283
Basic Processing Logic and Def...
Course Overview
The course BIT601 provides the knowledge required for modeling and controlling
business processes in custo...
Course Overview

BIT601

Course Objectives
After completing this course, you will be able to:
•

Create an organizational ...
Unit 1
Introduction
Unit Overview
This unit reinforces the Workflow Engine terminology covered in the course
BIT600.
The u...
Unit 1: Introduction

BIT601

Lesson: Fundamentals of Workflow Architecture
Lesson Overview
This lesson reinforces your kn...
BIT601

Lesson: Fundamentals of Workflow Architecture

Workflow Architecture and its Use

Figure 1: Why Use SAP Workflow?
...
Unit 1: Introduction

BIT601

Figure 2: Workflow Architecture

In key words, workflow is: Getting the right work to the ri...
BIT601

Lesson: Fundamentals of Workflow Architecture

To the right person: The organizational level creates the link to t...
Unit 1: Introduction

BIT601

To do this, you require the knowledge from this course. You can use the template
as a model ...
BIT601

Lesson: Fundamentals of Workflow Architecture

General Procedure When Implementing a Workflow Scenario: BOTTOM UP
...
Unit 1: Introduction

BIT601

Figure 4: Example: Designing a Workflow for “Approving Vacation”

The business steps require...
BIT601

Lesson: Fundamentals of Workflow Architecture

For each event you should ask yourself:
•

When is this event gener...
Unit 1: Introduction

BIT601

Figure 6: Overview of Customizing Activities

Notification Using Enhancements in the Standar...
BIT601

Lesson: Fundamentals of Workflow Architecture

For sending missed deadline work items, read Note 200996.

2007

© ...
Unit 1: Introduction

12

BIT601

© 2007 SAP AG. All rights reserved.

2007
BIT601

Lesson: Fundamentals of Workflow Architecture

Exercise 1: Components of a Workflow
Exercise Objectives
After comp...
Unit 1: Introduction

4.

BIT601

If there is no template that represents your business requirements, you must
contact SAP...
BIT601

Lesson: Fundamentals of Workflow Architecture

3.

An
is a pre-defined workflow definition
supplied by SAP that de...
Unit 1: Introduction

BIT601

Solution 1: Components of a Workflow
Task 1:
You are invited to attend a meeting about workf...
BIT601

Lesson: Fundamentals of Workflow Architecture

Task 2:
A lot of workflow terms were used in the meeting. Some of t...
Unit 1: Introduction

9.

BIT601

Interaction between the runtime execution of workflows and users
responsible for carryin...
BIT601

Lesson: Fundamentals of Workflow Architecture

Lesson Summary
You should now be able to:
•
Describe the workflow a...
Unit 1: Introduction

BIT601

Lesson: Workflow and Organizational Management
Lesson Overview
This lesson describes the opt...
BIT601

Lesson: Workflow and Organizational Management

Options for using Organizational Management

Figure 7: Using Organ...
Unit 1: Introduction

BIT601

Creating Organizational Units in “Simple Maintenance”

Figure 8: Features of “simple mainten...
BIT601

Lesson: Workflow and Organizational Management

Figure 9: Interaction of Tasks with Positions and Jobs (Agent Assi...
Unit 1: Introduction

BIT601

Figure 10: Create Organizational Plan (Simple Maintenance)

The first step in “simple mainte...
BIT601

Lesson: Workflow and Organizational Management

Definition of Possible Agents Using Organizational
Management

Fig...
Unit 1: Introduction

BIT601

Digression: Substitution in the workflow
The substitution is maintained in the Business Work...
BIT601

Lesson: Workflow and Organizational Management

The task step in the workflow on which a work item is based has as...
Unit 1: Introduction

28

BIT601

© 2007 SAP AG. All rights reserved.

2007
BIT601

Lesson: Workflow and Organizational Management

Exercise 2: Creating an Organizational
Structure for a Workflow Sc...
Unit 1: Introduction

BIT601

Solution 2: Creating an Organizational
Structure for a Workflow Scenario
Task:
The agents of...
BIT601

Lesson: Workflow and Organizational Management

3.

In the organizational unit, create a position for the employee...
Unit 1: Introduction

BIT601

Lesson Summary
You should now be able to:
•
List the different options for using organizatio...
BIT601

Unit Summary

Unit Summary
You should now be able to:
•
Describe the workflow architecture
•
Name the steps involv...
Unit Summary

34

BIT601

© 2007 SAP AG. All rights reserved.

2007
BIT601

Test Your Knowledge

Test Your Knowledge
1.

Standard tasks call methods of an object type.
Determine whether this...
Test Your Knowledge

BIT601

Answers
1.

Standard tasks call methods of an object type.
Answer: True
You can use methods o...
Unit 2
Workflow Definition in the Workflow
Builder
Unit Overview
This unit provides an introduction to working with the Wo...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

Lesson: Structure of the Workflow Builder
Lesson Overview
Thi...
BIT601

Lesson: Structure of the Workflow Builder

Workflow templates have an internal key with the following structure:
•...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

Existing workflow tasks can still be executed, but they are n...
BIT601

Lesson: Structure of the Workflow Builder

Figure 16: Workflow-Definition: Workflow Builder

The workflow definiti...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

The Workflow Builder is subdivided into the following areas:
...
BIT601

Lesson: Structure of the Workflow Builder

The following areas are disjointed in the display: insertable step type...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

A workflow definition is made up of individual modular steps....
BIT601

Lesson: Structure of the Workflow Builder

Example:
Step Approve vacation request
The step can end with the result...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

Enable top-down modeling
•
•
•
•

Use Extras → Options → Defa...
BIT601

Lesson: Structure of the Workflow Builder

transaction. Start transactions are being replaced with start forms. Ex...
Unit 2: Workflow Definition in the Workflow Builder

48

© 2007 SAP AG. All rights reserved.

BIT601

2007
BIT601

Lesson: Structure of the Workflow Builder

Exercise 3: Overview of the Workflow
Definition
Exercise Objectives
Aft...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

Task 2:
Create a user decision.
Since no tasks are available ...
BIT601

Lesson: Structure of the Workflow Builder

Task 4:
After you start the workflow template, you will be asked to mak...
Unit 2: Workflow Definition in the Workflow Builder

2.

BIT601

Start your workflow and test your modified workflow defin...
BIT601

Lesson: Structure of the Workflow Builder

This view mainly indicates the role an employee has played in
executing...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

Solution 3: Overview of the Workflow
Definition
Task 1:
Imple...
BIT601

Lesson: Structure of the Workflow Builder

Task 2:
Create a user decision.
Since no tasks are available yet, you s...
Unit 2: Workflow Definition in the Workflow Builder

2.

BIT601

Determine the responsible agent for the step. Use the F4 ...
BIT601

Lesson: Structure of the Workflow Builder

Go back to the first session and choose the Test icon in the Workflow B...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

If the work item is still displayed, refresh the inbox.
a)

I...
BIT601

Lesson: Structure of the Workflow Builder

2.

The agent for the user decision should be the position of your mana...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

Task 7:
Check the workflow log for your workflow and check th...
BIT601

Lesson: Structure of the Workflow Builder

This view lists the objects that are related to the workflow or that
ha...
Unit 2: Workflow Definition in the Workflow Builder

BIT601

Lesson Summary
You should now be able to:
•
Create a workflow...
BIT601

Unit Summary

Unit Summary
You should now be able to:
•
Create a workflow template with a workflow definition
•
Li...
Unit Summary

64

BIT601

© 2007 SAP AG. All rights reserved.

2007
BIT601

Test Your Knowledge

Test Your Knowledge
1.

The Workflow Builder displays warnings and errors that are displayed ...
Test Your Knowledge

BIT601

Answers
1.

The Workflow Builder displays warnings and errors that are displayed when
a new r...
Unit 3
Business Objects and Business
Object Repository
Unit Overview
The activities that take place at runtime of a busine...
Unit 3: Business Objects and Business Object Repository

BIT601

Lesson: Structure of Object Types in the Business
Object ...
BIT601

Lesson: Structure of Object Types in the Business Object Repository

Business Object Types and the Business Object...
Unit 3: Business Objects and Business Object Repository

BIT601

Figure 21: Business Object Repository (BOR)

The graphic ...
BIT601

Lesson: Structure of Object Types in the Business Object Repository

Figure 22: Examples of Object Types

The SAP ...
Unit 3: Business Objects and Business Object Repository

BIT601

Object Type and Object Instance

Figure 23: Object Type a...
BIT601

Lesson: Structure of Object Types in the Business Object Repository

Figure 24: Addressing Instances in the Workfl...
Unit 3: Business Objects and Business Object Repository

BIT601

Objects in the Workflow

Figure 25: Objects in the Workfl...
BIT601

Lesson: Structure of Object Types in the Business Object Repository

Figure 26: Material Workflow BIT601

Procedur...
Unit 3: Business Objects and Business Object Repository

76

© 2007 SAP AG. All rights reserved.

BIT601

2007
BIT601

Lesson: Structure of Object Types in the Business Object Repository

Exercise 4: Familiarize yourself with the
Bus...
Unit 3: Business Objects and Business Object Repository

BIT601

Solution 4: Familiarize yourself with the
Business Object...
BIT601

Lesson: Structure of Object Types in the Business Object Repository

Enter G## in the Lab/Office field.
a)

Return...
Unit 3: Business Objects and Business Object Repository

BIT601

Lesson Summary
You should now be able to:
•
Describe the ...
BIT601

Lesson: Adjusting Standard Object Types to Suit Customer Requirements

Lesson: Adjusting Standard Object Types to ...
Unit 3: Business Objects and Business Object Repository

BIT601

Definition of a Subtype and Delegation

Figure 27: Object...
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows
Upcoming SlideShare
Loading in...5
×

142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows

3,787

Published on

BIT601

Published in: Education, Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,787
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
517
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Transcript of "142165153 bit601 sap-workflow-definition-and-use-of-customer-specific-workflows"

  1. 1. BIT601 SAP Workflow – Definition and Use of Customer-Specific Workflows SAP NetWeaver Date Training Center Instructors Education Website Participant Handbook Course Version: 62 Course Duration: 5 Days Material Number: 50086346 An SAP course - use it to learn, reference it for work
  2. 2. Copyright Copyright © 2007 SAP AG. 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. Trademarks • Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. • IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. • ORACLE® is a registered trademark of ORACLE Corporation. • INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated. • UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. • Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. • HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. • JAVA® is a registered trademark of Sun Microsystems, Inc. • JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. • SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS. g2007112133224
  3. 3. About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study. Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style Description Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal (in this documentation) and external (in other locations, such as SAPNet). Example text EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE. Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program. Example text Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation. <Example text> 2007 Emphasized words or phrases in body text, titles of graphics, and tables Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. © 2007 SAP AG. All rights reserved. iii
  4. 4. About This Handbook BIT601 Icons in Body Text The following icons are used in this handbook. Icon Meaning For more information, tips, or background Note or further explanation of previous point Exception or caution Procedures Indicates that the item is displayed in the instructor's presentation. iv © 2007 SAP AG. All rights reserved. 2007
  5. 5. Contents Course Overview ......................................................... vii Course Goals ...........................................................vii Course Objectives .....................................................vii Unit 1: Introduction........................................................ 1 Fundamentals of Workflow Architecture .............................2 Workflow and Organizational Management ....................... 20 Unit 2: Workflow Definition in the Workflow Builder ............ 37 Structure of the Workflow Builder ................................... 38 Unit 3: Business Objects and Business Object Repository ... 67 Structure of Object Types in the Business Object Repository .. 68 Adjusting Standard Object Types to Suit Customer Requirements ...................................................... 81 Unit 4: Task Structure and Use in Workflows .................... 109 Definition of Tasks ................................................... 110 Integrating Tasks in the Workflow Templates and Administration of Task Groups ...................................................140 Unit 5: Containers and Interfaces in Workflow .................. 155 Existing Containers and Binding Directions ......................156 Container Definition and Binding Definition ......................167 Unit 6: Determining the Recipients of Work Items .............. 185 Options for Agent Assignment and Examples of Rules .........186 Rule Definition of Type Responsibilities...........................193 Interaction Between Possible and Responsible Agents ........213 Unit 7: Ad Hoc Processing Options ................................ 221 Dynamic Selection of Agents and Used Tasks...................222 Enhancing workflows using the ad hoc anchor step type, and starting review processes .......................................234 Unit 8: Monitoring Steps in Business Processes ............... 259 Options for Simple and Modeled Deadline Monitoring ..........260 2007 © 2007 SAP AG. All rights reserved. v
  6. 6. Contents BIT601 Unit 9: Events and Workflow ......................................... 283 Basic Processing Logic and Definition of Events in the BOR ..285 Linking the Workflow and the Event ...............................291 Triggering Events in the Application ...............................300 Additional Start Conditions for Workflows and Event Queue ..316 Testing in the Event Environment and During Workflow Implementation ...................................................329 Unit 10: Special Step Types and Methods of Processing ..... 343 Forks, Multiline Attributes, and Using Document Templates ...344 Loops, Form Processing and Conditions in the Workflow Step 364 Using BLOCK and SWITCH ........................................377 Unit 11: Wizards ......................................................... 397 Wizards for the Definition of Workflow Templates ...............398 Wizards for the Definition of Steps in Workflow Templates.....404 Unit 12: Tutorial ......................................................... 413 Tutorial ................................................................414 Appendix 1: Data sheet for the course BIT601 Appendix 2: Important transaction codes ................ 471 ...................... 473 Appendix 3: Triggering events or starting workflows in the application (Business Transaction Event and message control) ................................................................. 475 Appendix 4: Basic Customizing for the Workflow Engine Appendix 5: Specific Transactions for Runtime Monitoring .. 481 491 Appendix 6: Addressing using SAP Organizational Objects .................................................................. 503 Glossary................................................................... 505 vi © 2007 SAP AG. All rights reserved. 2007
  7. 7. Course Overview The course BIT601 provides the knowledge required for modeling and controlling business processes in customer-specific workflow templates. It covers the following areas: • • • • • • • • Creating workflow definitions using the Workflow Builder Enhancing standard business object types using the Business Object Builder Defining steps in the business process: Task definition Container and binding logic Dynamic agent determination with rules for evaluating the runtime data. Triggering events in applications Linking events to workflows Monitoring of business process steps with deadline monitoring models Target Audience This course is intended for the following audiences: • Project team members who develop workflows and who are responsible for running workflows Course Prerequisites Required Knowledge • • SAPTec R/3 Basis Technology BIT600 Introduction to SAP Business Workflow Course Goals This course will prepare you to: • • • • • • 2007 Enhance SAP standard object types to suit your own requirements Generate and test executable workflow templates Use events to start workflow templates Use ad hoc workflow functions Use the organizational model or rules for agent determination for individual process steps Use wizards to support the design process © 2007 SAP AG. All rights reserved. vii
  8. 8. Course Overview BIT601 Course Objectives After completing this course, you will be able to: • Create an organizational plan and link organizational objects to tasks in the workflow Enhance standard object types Generate tasks (TS) Generate workflow templates (WS) Monitor/enhance interfaces (= containers) Define rules for agent determination Model deadline monitoring Determine and actively link triggering events for a workflow Trigger events within applications Use Workflow Wizards • • • • • • • • • SAP Software Component Information The information in this course pertains to the following SAP Software Components and releases: • • viii ERP 6.0 SAP Web Application Server 6.20 © 2007 SAP AG. All rights reserved. 2007
  9. 9. Unit 1 Introduction Unit Overview This unit reinforces the Workflow Engine terminology covered in the course BIT600. The unit also explains how Organizational Management can be used for agent determination in workflow, and introduces the business example that you will use in the exercises throughout the course. Unit Objectives After completing this unit, you will be able to: • • • • • • Describe the workflow architecture Name the steps involved in a workflow project Describe the general procedure for design and implementation. List the different options for using organizational management in a workflow Create an organizational unit with positions Describe the different ways of assigning possible agents to units in the organizational model Unit Contents Lesson: Fundamentals of Workflow Architecture..............................2 Exercise 1: Components of a Workflow .................................. 13 Lesson: Workflow and Organizational Management ........................ 20 Exercise 2: Creating an Organizational Structure for a Workflow Scenario ...................................................................... 29 2007 © 2007 SAP AG. All rights reserved. 1
  10. 10. Unit 1: Introduction BIT601 Lesson: Fundamentals of Workflow Architecture Lesson Overview This lesson reinforces your knowledge of the underlying architecture of the Workflow Engine, and the associated terminology. It also introduces the example workflow that you will create during the course. Lesson Objectives After completing this lesson, you will be able to: • • • Describe the workflow architecture Name the steps involved in a workflow project Describe the general procedure for design and implementation. Business Example You want to use the SAP Workflow Engine in your company to be able to control and monitor your business processes effectively. You want the first business process to be a materials management process that will start when changes are made to a material master. The system first displays the change documents to an assigned user (these documents are for the material master that was changed), the user then decides whether the change is okay. If the assigned user accepts the change, another user receives a work item that displays the material master. If this user does not accept the change, a mail is sent to the person who made the change. The workflow should use the organizational plan of the company. 2 © 2007 SAP AG. All rights reserved. 2007
  11. 11. BIT601 Lesson: Fundamentals of Workflow Architecture Workflow Architecture and its Use Figure 1: Why Use SAP Workflow? SAP Workflow supports your business processes that run in an SAP system. It also supports communication between business processes that are running on different systems. For communication between systems, SAP Workflow uses the Wf-XML interface. This interface is not covered in BIT601, but is dealt with separately in course BIT603. The SAP Workflow can combine different component steps into a single process. The SAP Workflow supplies the end user with all of the information required for the step to be processed. The SAP standard delivery contains workflow templates that map business processes. You can generate your own workflow templates or adapt those provided by SAP to meet your requirements. 2007 © 2007 SAP AG. All rights reserved. 3
  12. 12. Unit 1: Introduction BIT601 Figure 2: Workflow Architecture In key words, workflow is: Getting the right work to the right user at the right time. The right work: Whatever you want to achieve by using the workflow: it must be implemented as a business object type in the business object repository. Methods can be implemented as BAPIs. You can then call them from outside the system. BAPIs have an established static interface. The tool for maintaining business object types is the Business Object Repository (BOR). In SAP ERP, the ABAP-OO interface is also available for defining “the right work ”. As of SAP ERP, you can also call methods from ABAP-OO classes in a process step. Note: Course BIT611 provides further information about this interface. At the right time: The process level describes the business process in a sequence of individual steps. Together, these steps form the workflow definition. An individual step can refer to a method in the BOR, but it can also be used to control the process, for example, to allow loop processes, to query conditions or to fill the interface (= container) with values. The tool used for maintaining the process level is the Workflow Builder. 4 © 2007 SAP AG. All rights reserved. 2007
  13. 13. BIT601 Lesson: Fundamentals of Workflow Architecture To the right person: The organizational level creates the link to the organizational structure. • • A task that can be executed within a workflow has a group of possible agents. This group can be restricted by specifying the agent in the workflow step. At runtime, selected agents receive a work item in their Business Workplace. If the work item is executed, the system starts the relevant method of the business object type. Creating a Workflow Scenario Figure 3: Steps in a Workflow Project If you want to use the SAP Workflow Engine to map a business process in your company, you should first ascertain whether SAP supplies a workflow template for this process. The process of finding a workflow template and adapting it for execution is covered in course BIT600. The documentation for the SAP Workflow Engine is available in the SAP Library under AP NetWeaver 7.0 - SAP NetWeaver by Key Capability - Application Platform by Key Capability - Business Services - SAP Business Workflow Reference Documentation. As of R/3 Enterprise, you can find which applications provide workflows as templates by consulting the documentation for the relevant application. In Release 4.6C, the documentation is available in the SAP Library under Basis Components → Business Management → SAP Business Workflow → Reference Documentation. The templates delivered for different applications are listed under Workflow Scenarios in Applications. If you find a template, you may still have to adapt the process logic. 2007 © 2007 SAP AG. All rights reserved. 5
  14. 14. Unit 1: Introduction BIT601 To do this, you require the knowledge from this course. You can use the template as a model after you have created a copy. Only if you do not find a suitable template, do you have to plan and implement the workflow yourself from start to finish. General Procedure When Creating a Workflow Scenario: Top Down • • • • • • Determine the business steps in the process. Define each step as a method of an object type. Determine the agents responsible for the steps. Determine any additional control steps in the workflow: Loops, container operations, conditions, and so on. Determine when the workflow is to start: Triggering event, start form, and so on. Define possible additional functions: Deadline monitoring, conditions when steps are completed, and so on. You have selected a business process that you want to control using the Workflow Engine. You have to divide the process into individual steps that can be executed in the workflow. A step that executes business functions must refer to an object type method. You must determine the organizational responsibility for these business steps, that is, you have to define which of your employees are responsible for the function. You can map the responsibilities in the workflow by referring to organizational objects. An agent can be an SAP user, organizational unit, position, job, or HR work center. You can also assign an activity group. You may find the relevant objects in your customized organizational plan again. In addition to your organizational plan, you may also have to create special organizational units for your workflow scenario only, or you may also have to refer to the existing objects of your organizational level during agent determination. You can assign activity groups if you do not want to refer to the organizational model. In addition to the business steps, a workflow also normally contains control steps, for example, loops or condition queries, and so on. Establishing which steps are required is a part of the design process. In the design phase, clarify how the workflow is to be triggered. 6 © 2007 SAP AG. All rights reserved. 2007
  15. 15. BIT601 Lesson: Fundamentals of Workflow Architecture General Procedure When Implementing a Workflow Scenario: BOTTOM UP • • • • • • Business Object Repository: Check to see whether a suitable object type exists and whether it has all of the necessary attributes, methods and events. Create the necessary tasks (TSxxxxxxxx). Generate the workflow template and implement the tasks ( = business steps). Implement any additional controlling steps such as loops, conditions, container operations, and so on. Test the link between the workflow and the event: Triggering event in transaction SWUE without using the application Trigger the event in the required application. You have selected a business process and divided it into individual steps that can be executed in a workflow. Find the suitable object types in the Business Object Repository. Check that all required methods, attributes and events are available. If they are not available, you must enhance the object type to suit your requirements. Check whether the system already contains tasks for your required steps. If not, you need to define new tasks. You can define tasks explicitly, but you can also create them directly from the Workflow Builder. In your workflow definition, always create the steps that refer to an object method first (these are the business steps). This allows the system to generate the necessary container elements. Call transaction SWUS from the Workflow Builder and use it to test the workflow. If you have defined a triggering event for test purposes, you can use transaction SWUE to trigger the event directly in the system. 2007 © 2007 SAP AG. All rights reserved. 7
  16. 16. Unit 1: Introduction BIT601 Figure 4: Example: Designing a Workflow for “Approving Vacation” The business steps required in the process are: • • • • • Approve request Delete request Review request User decision on how to continue if the superior has rejected the request. Send a mail if the superior approves the request. For each step you should ask yourself: • What work has to be done? This establishes which object type and which method you need. • For dialog steps: Who is doing the work? This establishes who the responsible agents are. • Which text should be displayed in the workplace of the work item recipient? This text is maintained when the step is created as a task. • Include your answers in the design. The process requires a loop because a new request has to be resubmitted each time. The loop is a controlling step that has to be implemented with a termination condition. The process is then triggered if a user creates a vacation request using a special transaction. The system triggers the “Request created” event and starts the workflow. 8 © 2007 SAP AG. All rights reserved. 2007
  17. 17. BIT601 Lesson: Fundamentals of Workflow Architecture For each event you should ask yourself: • When is this event generated, and using which application? Basic Customizing for the Workflow Engine Figure 5: Workflow Engine Customizing To make the basic Customizing settings for the Workflow Engine, choose: Tools → Business Workflow → Development → Utilities → Automatic Workflow Customizing (transaction SWU3) A number of client-specific system settings and activities need to be carried out for the Workflow Engine. For a description of the customizing activities and their functions, see the online documentation or online help. The function “Execute Automatic Workflow Customizing” enables you to maintain the standard settings for the Workflow Engine “at the touch of a button”. You can then use the button Verification workflow to start a first “test workflow” to check the customizing settings. In the section “Workflow Runtime System”, green checkmarks should be set. In the “Workflow development environment” section, an entry with errors in “Number range for customer tasks” can be ignored. Automatic Customizing does not include maintenance of the organizational plan or task-specific Customizing (that is, assignment between tasks and possible agents). 2007 © 2007 SAP AG. All rights reserved. 9
  18. 18. Unit 1: Introduction BIT601 Figure 6: Overview of Customizing Activities Notification Using Enhancements in the Standard Mail Inbox Work Item Notification by Report • Aim: – • Every time a work item is stored in the Business Workplace of the SAP System, the relevant user should receive an e-mail. Procedure: – – – – SAPNet Note 627397 contains an ABAP program and describes the procedure in the context of notifications. The user for whom the report is scheduled must have maintained an Internet address in the user data under “further communication”. This becomes the sender of the e-mail. A SendMail process must be active. An Internet Gateway must be active in the SAP system. The e-mail text is formed from the description text for the underlying task of the work item. The program enables you to add executable attachments to the e-mail. The e-mail recipient can then either ... Using transaction SCOT, you can determine whether the necessary processes are running in the system. You also can trigger sending specifically from this transaction. The send process is called RSCONN01. 10 © 2007 SAP AG. All rights reserved. 2007
  19. 19. BIT601 Lesson: Fundamentals of Workflow Architecture For sending missed deadline work items, read Note 200996. 2007 © 2007 SAP AG. All rights reserved. 11
  20. 20. Unit 1: Introduction 12 BIT601 © 2007 SAP AG. All rights reserved. 2007
  21. 21. BIT601 Lesson: Fundamentals of Workflow Architecture Exercise 1: Components of a Workflow Exercise Objectives After completing this exercise, you will be able to: • Correctly name and assign workflow components Business Example You want to use a workflow in your company to automate business processes. Your goal is to support a business process in materials management. To better understand the terminology used, you will first review the basics from the introductory workflow course. Task 1: You are invited to attend a meeting about workflows. Many of the people present do not know anything about the SAP Workflow Engine. They are relying on you to answer their questions and concerns. Below are some of the statements people made in the meeting. Determine which are true and which are not. 1. The Workflow Engine is a tool for automating business processes, which is not tied to any particular application and operates uniformly across different applications. Determine whether this statement is true or false. □ □ 2. True False The Workflow Engine coordinates all of the tasks involved and provides the user with active support. Determine whether this statement is true or false. □ □ 3. True False SAP provides several workflow templates that you can use for your specific business requirements. Determine whether this statement is true or false. □ □ True False Continued on next page 2007 © 2007 SAP AG. All rights reserved. 13
  22. 22. Unit 1: Introduction 4. BIT601 If there is no template that represents your business requirements, you must contact SAP to develop the required business scenario. Determine whether this statement is true or false. □ □ 5. True False The Workflow Engine provides runtime tools for user interaction, process modeling and control. Determine whether this statement is true or false. □ □ 6. True False The Workfllow Engine uses the SAP Object Builder as a tool for modeling processes and creating workflow definitions. Determine whether this statement is true or false. □ □ True False Task 2: A lot of workflow terms were used in the meeting. Some of the people present did not know the meanings of these terms. As the workflow expert, you must define these terms for everyone. Using the terminology list provided below, ensure that everyone knows the appropriate term for each statement about the workflow. SAP Workflow Tasks Workflow template Events Jobs Positions Object Method Object type Inbox/Workplace Workflow definition Workflow Builder 1. An is a generic description of an object. It includes the definition of key fields, methods, attributes and events. Fill in the blanks to complete the sentence. 2. Any type of related information that can be accessed uniquely under an identifying key is called an . Fill in the blanks to complete the sentence. Continued on next page 14 © 2007 SAP AG. All rights reserved. 2007
  23. 23. BIT601 Lesson: Fundamentals of Workflow Architecture 3. An is a pre-defined workflow definition supplied by SAP that defines a specific business scenario. Fill in the blanks to complete the sentence. 4. A system workflow defined by the user or supplied by SAP is called a . Fill in the blanks to complete the sentence. 5. Workflows are generally started by . Fill in the blanks to complete the sentence. 6. The is a tool used to define, access and modify workflow definitions in a graphical format. Fill in the blanks to complete the sentence. 7. The technical implementation of a business process is referred to as a which consists of a sequence of connected steps. Fill in the blanks to complete the sentence. 8. From an organizational perspective, are the central element in the workflow system. They form the business steps of a business process. Fill in the blanks to complete the sentence. 9. Interaction between the runtime execution of workflows and users responsible for carrying out specific work to be done is managed by various . Fill in the blanks to complete the sentence. 10. and a workflow. can be used to assign agents to a step in Fill in the blanks to complete the sentence. 11. An employee occupies a . directly to . Employees are not assigned Fill in the blanks to complete the sentence. 12. model functions that are executed when the workflow is running. Fill in the blanks to complete the sentence. 2007 © 2007 SAP AG. All rights reserved. 15
  24. 24. Unit 1: Introduction BIT601 Solution 1: Components of a Workflow Task 1: You are invited to attend a meeting about workflows. Many of the people present do not know anything about the SAP Workflow Engine. They are relying on you to answer their questions and concerns. Below are some of the statements people made in the meeting. Determine which are true and which are not. 1. The Workflow Engine is a tool for automating business processes, which is not tied to any particular application and operates uniformly across different applications. Answer: True 2. The Workflow Engine coordinates all of the tasks involved and provides the user with active support. Answer: True 3. SAP provides several workflow templates that you can use for your specific business requirements. Answer: True 4. If there is no template that represents your business requirements, you must contact SAP to develop the required business scenario. Answer: False 5. The Workflow Engine provides runtime tools for user interaction, process modeling and control. Answer: True 6. The Workfllow Engine uses the SAP Object Builder as a tool for modeling processes and creating workflow definitions. Answer: False Continued on next page 16 © 2007 SAP AG. All rights reserved. 2007
  25. 25. BIT601 Lesson: Fundamentals of Workflow Architecture Task 2: A lot of workflow terms were used in the meeting. Some of the people present did not know the meanings of these terms. As the workflow expert, you must define these terms for everyone. Using the terminology list provided below, ensure that everyone knows the appropriate term for each statement about the workflow. SAP Workflow Tasks Workflow template Events Jobs Positions Object Method Object type Inbox/Workplace Workflow definition Workflow Builder 1. An object type is a generic description of an object. It includes the definition of key fields, methods, attributes and events. Answer: object type 2. Any type of related information that can be accessed uniquely under an identifying key is called an object. Answer: object 3. An SAP Workflow is a pre-defined workflow definition supplied by SAP that defines a specific business scenario. Answer: SAP Workflow 4. A system workflow defined by the user or supplied by SAP is called a workflow template. Answer: workflow template 5. Workflows are generally started by events. Answer: events 6. The Workflow Builder is a tool used to define, access and modify workflow definitions in a graphical format. Answer: Workflow Builder 7. The technical implementation of a business process is referred to as a workflow definition which consists of a sequence of connected steps. Answer: workflow definition 8. From an organizational perspective, tasks are the central element in the workflow system. They form the business steps of a business process. Answer: tasks Continued on next page 2007 © 2007 SAP AG. All rights reserved. 17
  26. 26. Unit 1: Introduction 9. BIT601 Interaction between the runtime execution of workflows and users responsible for carrying out specific work to be done is managed by various inboxes. Answer: inboxes 10. Jobs and positions can be used to assign agents to a step in a workflow. Answer: Jobs, positions 11. An employee occupies a position. Employees are not assigned directly to jobs. Answer: position, jobs 12. Methods model functions that are executed when the workflow is running. Answer: Methods 18 © 2007 SAP AG. All rights reserved. 2007
  27. 27. BIT601 Lesson: Fundamentals of Workflow Architecture Lesson Summary You should now be able to: • Describe the workflow architecture • Name the steps involved in a workflow project • Describe the general procedure for design and implementation. 2007 © 2007 SAP AG. All rights reserved. 19
  28. 28. Unit 1: Introduction BIT601 Lesson: Workflow and Organizational Management Lesson Overview This lesson describes the options available for using organizational management within a workflow, and how to create a link between organizational management and workflow. Lesson Objectives After completing this lesson, you will be able to: • • • List the different options for using organizational management in a workflow Create an organizational unit with positions Describe the different ways of assigning possible agents to units in the organizational model Business Example You want to use the SAP Workflow Engine in your company to be able to control and monitor your business processes effectively. You want the first business process to be a materials management process that will start when changes are made to a material master. The system first displays the change documents to an assigned user (these documents are for the material master that was changed), the user then decides whether the change is okay. If the assigned user accepts the change, another user receives a work item that displays the material master. If this user does not accept the change, a mail is sent to the person who made the change. The workflow should use the organizational plan of the company. 20 © 2007 SAP AG. All rights reserved. 2007
  29. 29. BIT601 Lesson: Workflow and Organizational Management Options for using Organizational Management Figure 7: Using Organizational Structures If the agents of the individual workflow steps are determined using the customer-specific organizational chart, your agent assignment in the workflow remains flexible to change. There are many ways to link your workflows to the SAP organizational plan. Example 1: • • • There is only one chart for the whole company. All workflows have to be connected to organizational objects from this structure. This option does not have any specific structures for the workflow alone. Example 2: • • HR manages the general structure for all employees in the company. To support the workflow, there is a small specific structure for each business process. Example 3: • • 2007 Your company does not (yet) have a general HR structure for all employees. To support the workflows, there will be one small structure for each process. © 2007 SAP AG. All rights reserved. 21
  30. 30. Unit 1: Introduction BIT601 Creating Organizational Units in “Simple Maintenance” Figure 8: Features of “simple maintenance” Maintenance of SAP Organizational Management is available as a basis component. Choose th following from the SAP Easy Access menu: Tools → Business Workflow → Development → Environment → Organizational Management → Simple Maintenance You are working with a main window and three main functions. Each function is determined for a particular group of maintenance activities. The Create Organizational Unit icon allows you to create and maintain the organizational structure for your organizational plan. The Create Position icon allows you to create the positions again as part of your organizational structure. The Tasks function allows you to create, maintain and view assignments for jobs, positions, and users. Caution: The HR component recognizes both SAP system users and individual persons as holders of positions. Workflow only recognizes SAP system users as valid agents. If the existing HR organizational structure is to be used for the workflow, the infotype 105 and communication type 0001 (SAP system user) must be entered for each person in the master record. This infotype is used to assign an SAP system user to an HR person These users are created by maintaining the HR master record. From the basic menu, choose: HR → Personnel Management → Administration → HR Master Data → Maintain. 22 © 2007 SAP AG. All rights reserved. 2007
  31. 31. BIT601 Lesson: Workflow and Organizational Management Figure 9: Interaction of Tasks with Positions and Jobs (Agent Assignment) A task can be assigned to one or more jobs. Jobs are general activity descriptions. Jobs are not designed to be held by employees. It is the positions in your company that are held by individuals. If a position is assigned to a job, the position inherits the tasks of the job, but it can also have additional tasks related to the specific task area for that position. One position may also be shared by several employees, each working less than full time. For example, two employees can occupy 60% and 40% of a position. The workflow regards both employees as valid agents and ignores the percentage division of the job. 2007 © 2007 SAP AG. All rights reserved. 23
  32. 32. Unit 1: Introduction BIT601 Figure 10: Create Organizational Plan (Simple Maintenance) The first step in “simple maintenance” is to create the root organizational unit. Once this organizational unit has been created, create the appropriate lower-level organizational units. Organizational units and jobs may be created in any order, but they must exist before the related positions are created. Jobs may exist in the job index, or they may be created once the model contains an organizational unit. Positions are created after the corresponding jobs have been created in the job index. Caution: In SAP R/3 release 4.6B, you must define a position first. You can then create the job with reference to the position. Holders are assigned to positions, not to jobs. The link between workflow tasks and organization units is explained in the next section. 24 © 2007 SAP AG. All rights reserved. 2007
  33. 33. BIT601 Lesson: Workflow and Organizational Management Definition of Possible Agents Using Organizational Management Figure 11: Agent Assignment Options Between Tasks and Organizational Objects All the tasks required (such as approve request, create purchase order, update customer master, and so on) are created as part of the workflow definition. A user is only authorized to process the corresponding work item at runtime if he or she is defined as a possible agent for the task. This chart shows all the basic options available for creating the connection: • • • • • • Task 1: Task 2: Task 3: Task 4: Task 5: Task 6: User 1 (assigned by job) User 1, user 2 (assigned by jobs) User 1, user 2, user 3, user 4 (assigned by organizational unit) User 1, user 3, user 4 (assigned by position or by job) User 2 (assigned by job) User 3, user 4 (assigned by jobs) The assignment of a workflow task to an organizational object is best performed using task maintenance under Additional data - Maintain Agent Assignment. After you create an agent assignment, you have to generate the index for that agent assignment again (using the Generate index button within task maintenance). 2007 © 2007 SAP AG. All rights reserved. 25
  34. 34. Unit 1: Introduction BIT601 Digression: Substitution in the workflow The substitution is maintained in the Business Workplace. • You can maintain substitution in two ways: • – Personal substitute (for an SAP user) – Position substitute Substitutes may be – – – – Created and activated at the same time From the time of activation, the substitute automatically receives not only their own work items, but also the substitution work items. Created and not activated The substitute can take active control of the substitution function at any time. Until the substitute actively ends the substitution, only the substitution work items are displayed in his or her Workplace. Hint: As of SAP ERP 6.0, in the basic Customizing of the Workflow Engine, you can set that a substitute (if they explicitly execute the substitution themselves) sees not only the work items of the absent user, but also their own work items. The maintenance is available under transaction SPRO → choose SAP Reference IMG → SAP NetWeaver → Application Server → Business Management → SAP Business Workflow → Basic Settings (Workflow System) → Change Presettings for Personal Workflow Settings. To create and activate the substitution, choose: → Workplace icon (or Office → Workplace) → Settings → Workflow Settings → Maintain Substitute/Activate Substitute To actively adopt or end a substitution, choose → Workplace icon (or Office → Workplace) → Settings → Workflow Settings → Adopt Substitution/End Substitution Caution: Since the agent in many workflows is not determined from positions, using the “Position Substitute” variant may cause problems. It should only be used if you are sure that positions are used to determine the agent in all workflows used throughout the system. Example 1: 26 © 2007 SAP AG. All rights reserved. 2007
  35. 35. BIT601 Lesson: Workflow and Organizational Management The task step in the workflow on which a work item is based has assigned the position. The substitute for the position receives the work item. Example 2: The task step on which a work item is based has assigned a role and this role determines a user. The substitute does not receive the work item. Recommendation: Every user should maintain a personal substitute. This can transfer the substitution as required. Example workflow for this course Figure 12: Example Workflow “Changing the Material Master” General process scenario: Smith changes the material master 100-300. He or she enters the new value, “New_Part”, into the “Old material number” field. A change document is generated. The event “Material changed” is then published in the system. This event forms part of the BUS1001 object type. The published event triggers a workflow. In the first task, the workflow displays the change document for the changed material to the superior of the agent who changed the material master. In the second step, the material master is shown to all those responsible for material group 001. This organizational responsibility is determined within the design process of a rule definition. In this case, it comprises the members of an organizational unit. 2007 © 2007 SAP AG. All rights reserved. 27
  36. 36. Unit 1: Introduction 28 BIT601 © 2007 SAP AG. All rights reserved. 2007
  37. 37. BIT601 Lesson: Workflow and Organizational Management Exercise 2: Creating an Organizational Structure for a Workflow Scenario Exercise Objectives After completing this exercise, you will be able to: • Create an organizational unit to use for agent determination in the workflow • Create positions in the organizational unit, and assign users to the positions. Business Example You want to use components of organizational management for agent determination, and need to create an organizational unit that suits your requirements. Task: The agents of a workflow step may be organizational units for the entire organization or for the jobs or positions within an organization. Assigned users receive and process work items generated when a workflow definition is executed. Create an organizational structure with two positions, that will be help by your two agents BIT601-## and BIT601-MGR##. 1. Create an organizational structure. Assign the following names: Abbreviation ZWF_ORG_##. Name: organizational unit (## is your group number). 2. In the organizational unit, create a position for the chief. Enter the abbreviation: zpos_head_##, and the name: Position department head ##. 3. In the organizational unit, create a position for the employee. Enter the abbreviation: zpos_empl_##, and the name: Position employee ##. 4. Assign users to the positions. Department head position: BIT601–MGR## Employee position: BIT601–## 5. 2007 Define Position department head as the chief position. © 2007 SAP AG. All rights reserved. 29
  38. 38. Unit 1: Introduction BIT601 Solution 2: Creating an Organizational Structure for a Workflow Scenario Task: The agents of a workflow step may be organizational units for the entire organization or for the jobs or positions within an organization. Assigned users receive and process work items generated when a workflow definition is executed. Create an organizational structure with two positions, that will be help by your two agents BIT601-## and BIT601-MGR##. 1. Create an organizational structure. Assign the following names: Abbreviation ZWF_ORG_##. Name: organizational unit (## is your group number). a) Select Tools → Business Workflow → Development → Environment → Organizational Management → Simple Maintenance → Organizational Plan Basic Data → Create b) Accept the time limit of the 31.12.9999 c) Make the following entries in the section “Details for Organizational Unit”: Abbreviation for organizational unit: ZWF_ORG_## Name: Organizational unit group ## d) 2. Select Save. In the organizational unit, create a position for the chief. Enter the abbreviation: zpos_head_##, and the name: Position department head ##. a) Remain in the same screen as for exercise 1, or call the following path: Tools → Business Workflow → Development → Environment → Organizational Management → Simple Maintenance → Organizational Plan Basic Data → Change b) Position the cursor on organizational unit group ##. c) Select Create. d) Double-click Incorporates Position. e) Enter the basic data for the position in the detail screen. Abbr.: Zpos_head_## Name: Position department head ## f) Choose Save. Continued on next page 30 © 2007 SAP AG. All rights reserved. 2007
  39. 39. BIT601 Lesson: Workflow and Organizational Management 3. In the organizational unit, create a position for the employee. Enter the abbreviation: zpos_empl_##, and the name: Position employee ##. a) Position the cursor on organizational unit group ##. b) Select Create. c) Double-click Incorporates Position. d) Enter the basic data for the position in the detail screen. Abbr.: Zpos_empl_## Name: Position employee ## e) 4. Choose Save. Assign users to the positions. Department head position: BIT601–MGR## Employee position: BIT601–## a) b) Enter BIT601-MGR## in the Name field. c) Choose Search. The user is displayed in the selection area. d) Use Drag&Drop to assign the user to the Position department head ##. e) Accept the proposed time limit. f) Choose Save. g) 5. Click on Users in the search area on the left of the screen. Repeat this procedure for the department employee position. Define Position department head as the chief position. a) b) Double-click the detail screen to display the position. c) Select the Head of own organizational unit indicator. d) 2007 Position the cursor on the name for Position department head. Choose Save. © 2007 SAP AG. All rights reserved. 31
  40. 40. Unit 1: Introduction BIT601 Lesson Summary You should now be able to: • List the different options for using organizational management in a workflow • Create an organizational unit with positions • Describe the different ways of assigning possible agents to units in the organizational model 32 © 2007 SAP AG. All rights reserved. 2007
  41. 41. BIT601 Unit Summary Unit Summary You should now be able to: • Describe the workflow architecture • Name the steps involved in a workflow project • Describe the general procedure for design and implementation. • List the different options for using organizational management in a workflow • Create an organizational unit with positions • Describe the different ways of assigning possible agents to units in the organizational model 2007 © 2007 SAP AG. All rights reserved. 33
  42. 42. Unit Summary 34 BIT601 © 2007 SAP AG. All rights reserved. 2007
  43. 43. BIT601 Test Your Knowledge Test Your Knowledge 1. Standard tasks call methods of an object type. Determine whether this statement is true or false. □ □ 2. True False Which options are available for defining possible agents for a task? Choose the correct answer(s). □ □ □ □ 2007 A B C D Positions Jobs Persons without assignment to a system user Activity groups © 2007 SAP AG. All rights reserved. 35
  44. 44. Test Your Knowledge BIT601 Answers 1. Standard tasks call methods of an object type. Answer: True You can use methods of a BOR object type to implement business process logic. The workflow calls the methods using a standard task to which the workflow refers. 2. Which options are available for defining possible agents for a task? Answer: A, B, D SAP Workflow only accepts system users An HR person must therefore be assigned to a system user. 36 © 2007 SAP AG. All rights reserved. 2007
  45. 45. Unit 2 Workflow Definition in the Workflow Builder Unit Overview This unit provides an introduction to working with the Workflow Builder. It provides an overview of the components of workflow templates, and the structure of the Workflow Builder and how to use it. Unit Objectives After completing this unit, you will be able to: • • • Create a workflow template with a workflow definition List the possible step types in a workflow Use the Workflow Builder Unit Contents Lesson: Structure of the Workflow Builder ................................... 38 Exercise 3: Overview of the Workflow Definition ........................ 49 2007 © 2007 SAP AG. All rights reserved. 37
  46. 46. Unit 2: Workflow Definition in the Workflow Builder BIT601 Lesson: Structure of the Workflow Builder Lesson Overview This lesson provides information on the structure of workflow templates as a whole, and on the workflow definition that is created in the Workflow Builder. Lesson Objectives After completing this lesson, you will be able to: • • • Create a workflow template with a workflow definition List the possible step types in a workflow Use the Workflow Builder Business Example You have designed a workflow template for your business process. To implement the workflow, you need to learn about the Workflow Builder. Defining Workflow Templates in the System Figure 13: How Are Workflows Created in the System? 38 © 2007 SAP AG. All rights reserved. 2007
  47. 47. BIT601 Lesson: Structure of the Workflow Builder Workflow templates have an internal key with the following structure: • • Task abbreviation WS for workflow templates Sequential 8-figure number The system recognizes from the structure of the 8-character number whether the template is a standard template delivered by SAP, or one that customers have created. Customer-defined templates start with the prefix number that was defined in Customizing for the system and client. Transaction SWU3 contains basic Customizing for the SAP Workflow Engine. This is discussed in detail in course BIT600. Figure 14: Terminology Workflow-controlled business processes are called workflows as of Release 4.5. They are called multistep tasks before Release 4.5. A single step in a business process that refers to a method of a business object type is called a single-step task before Release 4.5, and simply a task as of Release 4.5. As of Release 4.5, workflows are only created in the system as workflow templates. Workflow templates or workflow tasks can be created before Release 4.5. Individual steps for the SAP R/3 component must be created as standard tasks as of Release 4.5. Customer tasks can also be created before Release 4.5. Workflow templates and standard tasks are cross-client and time-independent. Workflow tasks and customer tasks are client-specific and time-dependent. 2007 © 2007 SAP AG. All rights reserved. 39
  48. 48. Unit 2: Workflow Definition in the Workflow Builder BIT601 Existing workflow tasks can still be executed, but they are no longer being further developed (for more information, see SAPnote 114811). Workflow Template/Workflow Definition/Workflow Builder Figure 15: Workflow Templates and Workflow Definitions A workflow template contains: • • • • • Basic data for the workflow, including instructions for buffering reporting data, automatic forwarding, and so on. Specification of triggering events If the specified event occurs in the system, the workflow starts if the event is actively linked to the workflow. Initial values Interface specifications (workflow container and event container) A link to the corresponding workflow definition, that is, the specification of the individual workflow steps that are to be executed. The binding identifies the relevant data required to execute the workflow. It establishes the connection between the input data required to execute a task and the output data as the result of the task, which has to be transferred to the next step in the workflow. 40 © 2007 SAP AG. All rights reserved. 2007
  49. 49. BIT601 Lesson: Structure of the Workflow Builder Figure 16: Workflow-Definition: Workflow Builder The workflow definition is created in the Workflow Builder and displayed graphically in a network. 2007 © 2007 SAP AG. All rights reserved. 41
  50. 50. Unit 2: Workflow Definition in the Workflow Builder BIT601 The Workflow Builder is subdivided into the following areas: • • • • Display of the abbreviation, version, and the status of the currently displayed workflow definition Navigation area with steps: Tree structure showing the sequence of workflow steps. Double clicking on a step displays the corresponding step definition Step types: All available step types for Drag&Drop into the workflow definition Container: Variables of the workflow interface Using the context menu, it is possible to create, change, display, delete, and rename container elements • • • • • • • 42 My Workflows and Tasks: In the tasks area, you can display all tasks and workflows that are relevant for your workflow, and transfer them into your workflow definition by double-clicking. Document templates: Here you can create and display existing document templates Workflow Wizards: Displays wizards for modeling steps and workflows Workflows of this Definition: Displays the current runtime instances Team working: Searching for steps according to certain criteria (created or changed by user, created or changed in release, created or changed in the period) Overview: Displays the whole workflow definition Message: All messages generated in where-used lists and workflow tests are displayed here. © 2007 SAP AG. All rights reserved. 2007
  51. 51. BIT601 Lesson: Structure of the Workflow Builder The following areas are disjointed in the display: insertable step types, containers, my workflows and tasks, document templates, Workflow Wizards and workflows of this definition. You have to choose one each time. Note: Notes about the search help for workflow objects The search help occurs when you enter complete object abbreviations or parts of these. The system displays all objects whose abbreviations correspond to the search. When you enter a complete abbreviation, this may also be more than one object. The abbreviation does not have to be unique. The uniqueness of an object uses the assignment of a unique internal key to produce the Workflow Engine. (WS30000015, TS30000016, and so on) Note: The search help evaluates Customizing. Table T778L contains the languages that the HR-PD supports. In the table T77S0, in the field Group SEARK, sm. abbr. LMODE, the entry defines the language for the search function. • • • Entry 0: the system searches only in the logon language Entry 1: the system first searches in the logon language and then in the first language from the table T778L and so on. The search ends as soon as objects are available in the relevant languages Entry 2: the system searches for objects in all of the languages from the table T778L Value 1 is the standard delivery. Figure 17: Workflow-Definition: Steps 2007 © 2007 SAP AG. All rights reserved. 43
  52. 52. Unit 2: Workflow Definition in the Workflow Builder BIT601 A workflow definition is made up of individual modular steps. When you create a step in a workflow definition, you must specify the step type first. The following step types exist: • Steps that refer to business activities: Activity, user decision, document from template, web activity, send mail, form. • Steps that are used for internal process control and monitoring: condition, multiple condition, loop, fork, container operation, event creator, wait for event, ad-hoc anchor, block, local workflow The steps can be arranged in series or in parallel processing (fork). The processing sequence of the steps depends on the result of each preceding step. The possible results of a step are usually derived from the relevant business function and are specified in the workflow step on the 'Outcomes' tab. The system adds another branch to the processing chain for each possible outcome. Depending on their type, all steps and events have certain symbols in the graphical display. Figure 18: Workflow-Definition: Functions of the Workflow Builder The Workflow Builder works in blocks. Each step is the determining element of “its” block. Operations in the individual steps always affect the whole block, that is, you can only delete, cut, and paste in blocks. A block has a start and includes all actions until a common outcome is found. 44 © 2007 SAP AG. All rights reserved. 2007
  53. 53. BIT601 Lesson: Structure of the Workflow Builder Example: Step Approve vacation request The step can end with the result approved or rejected. Both results have follow-up actions. The follow-up actions still belong to the Approve vacation request block and are therefore included in the block operations. As of SAP ERP 6.0, the step type "block" exists. Customers can use this step type to define their own block logic. In addition to the general workflow administrator set in Workflow Customizing, an administrator can also be assigned to each individual workflow in the basic data: To do this, choose Goto → Basic Data → Version-Independent tab page → Agents tab page. In Release 4.6, the assignment is made on the Responsibilities tab page. Special functions in the Workflow Builder You can use the My Workflows and Tasks view on the left of the object area in the Workflow Builder to display task groups. From here, you can double-click to transfer tasks to the workflow definition. You can use Extras → Options → View to display or hide certain areas of the Workflow Builder in the object area. Steps types displayed on the left of the screen can be transferred to the navigation area using Drag&Drop. These steps automatically appear in the graphical definition. Steps types that are rarely used or not used at all can be hidden from the step type display on the left of the screen. To hide these step types, use Extras - Options Hidden Step Types. You can reset the standard settings at any time. If a team of people is developing your workflow and you want to quickly obtain an overview of who has developed what, you can display the 'Team working views' function in the object area on the left of the screen. Among other things, this allows you to find steps that belong to other users. Workflow modelers can already be viewed in the graphical display using either user-specific or customer-specific block views. Choose Extras → Options → View → Block Display → User-Specific/Customer-Specific View 2007 © 2007 SAP AG. All rights reserved. 45
  54. 54. Unit 2: Workflow Definition in the Workflow Builder BIT601 Enable top-down modeling • • • • Use Extras → Options → Default Settings to activate top-down modeling in the Workflow Builder. The settings allows you to perform top-down modeling without specifying particular tasks. The steps are filled with placeholders that you have to replace in succession. You cannot perform a real runtime test with placeholders. Top-down modeling, which you have to explicitly activate, allows you to use your workflow chart to implement the workflow steps without having to create tasks. To do this, select Extras → Options → Default Settings → Use Top-Down Modeling. Here you can define the process and fill the individual steps with specific values. The task that you must use for this is TS30100074, WF_MODTASK. Starting Workflows and the Workflow Toolbox • For test purposes: – – • Test (F8) icon in the Workflow Builder Call the test transaction SWUS directly by choosing the following from the basic menu: Tools → Business Workflow → Development → Runtime Tools → Test Workflow Using events • – Applications trigger events. – Workflows are actively linked to events Using start forms or start transactions – – • • Create a form based on a DDIC structure in SAP R/3 Release 4.5 and 4.6, you can generate a start transaction for a workflow. Using function modules Using transaction SWUI (“workflow toolbox”) In test transaction “SWUS”, you can save input test data for a workflow as of Workflow Release 6.10 and reload this data for another test. You can also supply ad hoc agents directly. In Release 4.6, you can also create start transactions. You can enter the generated start transaction in your Favorites and then use it to start the corresponding workflow. As of workflow release 6.20, you can no longer create a start 46 © 2007 SAP AG. All rights reserved. 2007
  55. 55. BIT601 Lesson: Structure of the Workflow Builder transaction. Start transactions are being replaced with start forms. Existing start transactions are displayed on the Start Forms tab in the basic data of the Workflow Builder. Workflows are started using application events by default. A material is changed in transaction MM02: The application triggers the event “Material changed”. A vacation request is created. The application triggers the event “Vacation request created”. Course BIT610 discusses the option of using function modules to trigger workflows directly. Figure 19: Workflow Toolbox Transaction SWUI displays a list of small sample workflows. (toolbox principle) You can start the workflows and test them “live”. Call the Workflow Builder and view the technical details for the workflow. In contrast to transaction “SWUS”, which displays all the workflows in the system to any authorized user, transaction “SWUI” displays only the workflows in which the current user is explicitly named as a possible agent, or that have been created as general tasks. In the basic data of a workflow, you can choose the icon Agent Assignment for Task to maintain the possible users of a workflow. 2007 © 2007 SAP AG. All rights reserved. 47
  56. 56. Unit 2: Workflow Definition in the Workflow Builder 48 © 2007 SAP AG. All rights reserved. BIT601 2007
  57. 57. BIT601 Lesson: Structure of the Workflow Builder Exercise 3: Overview of the Workflow Definition Exercise Objectives After completing this exercise, you will be able to: • Use the Workflow Builder to create a workflow definition • Read runtime data from logs Business Example You have designed a workflow scenario and now want to use the Workflow Builder to create a workflow template. Task 1: Implement a workflow-controlled business process. When editing a workflow template, you create the workflow definition. This is processed when the workflow is executed. While the basic data of the workflow represents the external relationship (triggering events, for example), the workflow definition describes a business scenario as a sequence of linked steps. In the following, create a workflow template for your workflow which will start as soon as changes are made to a material. Since you have not yet defined the required tasks, but you want to test the workflow template, integrate two user decisions into your workflow definition. 1. As user BIT601-##, create a workflow template. Enter the following abbreviation: ZWF_TEST1_##. Enter the following name: Workflow material master change group ##. Place the object into package Z001 and when prompted by the system, create a new request with BIT601-## as the short description. Continued on next page 2007 © 2007 SAP AG. All rights reserved. 49
  58. 58. Unit 2: Workflow Definition in the Workflow Builder BIT601 Task 2: Create a user decision. Since no tasks are available yet, you should now incorporate a user decision into your workflow definition. At the beginning, the Workflow Builder displays an initial workflow definition with a default structure. The default structure consists of: • • 1. Two symbols indicating the start and end of the workflow definition One undefined step Create the user decision as the first step in the workflow definition after the workflow is started. Enter the following: Title: Material master change ok? Decision text 1: Change ok Decision text 2: Change not ok Outcome name for text 1: OK Outcome name for text 2: not_ok 2. Determine the responsible agent for the step. Use the F4 help to choose the position for the employee BIT601-## as a responsible agent. 3. How has your workflow definition changed? Check the change you made in the Workflow Builder. 4. Then activate your workflow definition. Task 3: Test your workflow. Display the work item in a parallel session in the Business Workplace. To do this, open another session and go to the Business Workplace. Arrange the windows so you can see both at the same time. 1. Start the workflow to test it and open a second session. Go back to the first session and choose the Test icon in the Workflow Builder. Continued on next page 50 © 2007 SAP AG. All rights reserved. 2007
  59. 59. BIT601 Lesson: Structure of the Workflow Builder Task 4: After you start the workflow template, you will be asked to make one of the following decisions: Change ok, Change not okay or Cancel and keep work item in inbox. You defined the Change ok and Change not ok decisions in the user definition. The system automatically generates the Cancel and keep work item in inbox decision. Do not specify any other decision. 1. Call the Business Workplace of the user in a second session. Switch to the other session and check the worklist of the Business Workplace. Does it contain a work item? If it does, do not execute the work item. 2. Return to the decision step in the other session and specify that it is not okay to change. (The decision text is: Change not ok) 3. Switch back to the other session and check your worklist. Is the previous work item still in the second session? If the work item is still displayed, refresh the inbox. Task 5: Enter a second user decision. Go from the test environment back to the Workflow Builder in change mode to add another user decision to your workflow definition. If you choose “Change not ok”, a work item is sent to the manager. The work item contains a user decision again. 1. Enter a second user decision into your workflow definition. This step should be specified for the undefined step immediately after the “not_ok” event following the first user decision. Enter the title: Material master change not okay. Enter the decision text Back to Changer and End Workflow. Enter the outcome names Back and End. 2. The agent for the user decision should be the position of your manager, BIT601-MGR##. Task 6: Activate and test your workflow definition again. 1. Activate and test your workflow definition. Continued on next page 2007 © 2007 SAP AG. All rights reserved. 51
  60. 60. Unit 2: Workflow Definition in the Workflow Builder 2. BIT601 Start your workflow and test your modified workflow definition. After you select not_okay in the first decision step, call the Business Workplace of the manager. Execute the work item and select Back to person who made the change. Task 7: Check the workflow log for your workflow and check the execution steps of your workflow. 1. Call the workflow log Hint: The Workflow Log screen contains three tab pages The Workflow Chronicle view, Workflow Agents view, and Workflow Objects view. Workflow chronicle view: This view shows all the steps in a workflow that have already been processed or are currently pending, as well as subworkflows. By choosing the Details function for a step, you can find out: • • • Who carried out which detailed actions on this work item and the result of the action When this action was executed Which objects were affected This view is generally used to determine which activities were carried out. The Agents function displays the possible agents and selected agents for a step. The Graphic function displays the graphical workflow log. Workflow Agents View: This view shows the employees that were involved in this workflow up to now. A list is displayed for each employee indicating: • • • Which action was carried out for which step When this action was executed Which objects were affected Continued on next page 52 © 2007 SAP AG. All rights reserved. 2007
  61. 61. BIT601 Lesson: Structure of the Workflow Builder This view mainly indicates the role an employee has played in executing a workflow. Workflow Objects View: This view lists the objects that are related to the workflow or that have been called up to now when the workflow was executed. These objects are: • The “first” object of the workflow Attachments and objects that have been added to individual steps within a workflow A list is displayed for each object indicating: • • Who carried out which detailed action for which task When this action was executed This view indicates which information has been generated as well as how it was generated and processed. Select these tabs and functions to check the details of your workflow. 2007 © 2007 SAP AG. All rights reserved. 53
  62. 62. Unit 2: Workflow Definition in the Workflow Builder BIT601 Solution 3: Overview of the Workflow Definition Task 1: Implement a workflow-controlled business process. When editing a workflow template, you create the workflow definition. This is processed when the workflow is executed. While the basic data of the workflow represents the external relationship (triggering events, for example), the workflow definition describes a business scenario as a sequence of linked steps. In the following, create a workflow template for your workflow which will start as soon as changes are made to a material. Since you have not yet defined the required tasks, but you want to test the workflow template, integrate two user decisions into your workflow definition. 1. As user BIT601-##, create a workflow template. Enter the following abbreviation: ZWF_TEST1_##. Enter the following name: Workflow material master change group ##. Place the object into package Z001 and when prompted by the system, create a new request with BIT601-## as the short description. a) As user BIT601-##, create a workflow template. Choose Tools → Business Workflow → Development → Definition tools → Workflow Builder → Workflow Builder: Create Workflow (transaction SWDB) The system calls the Workflow Builder. b) Choose Save and save the workflow template with the following data: Abbr.: ZWF_TEST1_## Name: Workflow material master change group ## Generate an object catalog entry for the package Z001. Note: If the system asks you for a request, create one with BIT601-## as the short description. Continued on next page 54 © 2007 SAP AG. All rights reserved. 2007
  63. 63. BIT601 Lesson: Structure of the Workflow Builder Task 2: Create a user decision. Since no tasks are available yet, you should now incorporate a user decision into your workflow definition. At the beginning, the Workflow Builder displays an initial workflow definition with a default structure. The default structure consists of: • • 1. Two symbols indicating the start and end of the workflow definition One undefined step Create the user decision as the first step in the workflow definition after the workflow is started. Enter the following: Title: Material master change ok? Decision text 1: Change ok Decision text 2: Change not ok Outcome name for text 1: OK Outcome name for text 2: not_ok a) Create the user decision as the first step in the workflow definition after the workflow is started. • • • Double-click the first undefined step in the basic screen of the Workflow Builder. Double-click to select User Decision in the dialog box. In the User Decision step, enter the following: Title: Material master change ok? Decision text 1: Change ok Decision text 2: Change not ok Outcome name 1: okay Outcome name 2: not_okay Continued on next page 2007 © 2007 SAP AG. All rights reserved. 55
  64. 64. Unit 2: Workflow Definition in the Workflow Builder 2. BIT601 Determine the responsible agent for the step. Use the F4 help to choose the position for the employee BIT601-## as a responsible agent. a) Determine the responsible agent for the step. • • • In the Agents section, select Position from the drop-down menu. Select the input help (F4) in the field beside Position. Find Zpos_empl_##. Since there is only one position with this abbreviation, it is transferred automatically. • 3. Choose Back to return to the basic screen of the Workflow Builder. How has your workflow definition changed? Check the change you made in the Workflow Builder. a) The user decision Is it okay to change the material master? is the first step in the workflow. This is followed by an exclusive OR, leading to two events, “okay” and “not ok”. Depending on the user’s decision, the workflow continues in the “okay” or “not ok” branch. 4. Then activate your workflow definition. a) In the basic screen of the Workflow Builder, select Generate and activate runtime version. You receive the following message: Workflow definition saved and activated successfully. Task 3: Test your workflow. Display the work item in a parallel session in the Business Workplace. To do this, open another session and go to the Business Workplace. Arrange the windows so you can see both at the same time. 1. Start the workflow to test it and open a second session. Continued on next page 56 © 2007 SAP AG. All rights reserved. 2007
  65. 65. BIT601 Lesson: Structure of the Workflow Builder Go back to the first session and choose the Test icon in the Workflow Builder. a) In the basic screen of the Workflow Builder, choose Test. b) On the Test Workflow screen, choose System → Create Session. c) Arrange the windows so you can see both at the same time. d) Start your workflow template. • • Switch back to the test workflow session. Choose Environment → Refresh Organizational Environment or simply use the Refresh Organizational Environment button. The number of your workflow template should be displayed in the Workflow field. • Choose Workflow → Execute or simply use the Execute icon. Task 4: After you start the workflow template, you will be asked to make one of the following decisions: Change ok, Change not okay or Cancel and keep work item in inbox. You defined the Change ok and Change not ok decisions in the user definition. The system automatically generates the Cancel and keep work item in inbox decision. Do not specify any other decision. 1. Call the Business Workplace of the user in a second session. Switch to the other session and check the worklist of the Business Workplace. Does it contain a work item? If it does, do not execute the work item. a) On the SAP Easy Access screen, click on the SAP Business Workplace icon, or select Office → Workplace from the menu. b) Open the Inbox folder. c) Click on Workflow. A work item is displayed. 2. Return to the decision step in the other session and specify that it is not okay to change. (The decision text is: Change not ok) a) Return to the session that displays the user decision. Choose Change not ok for the workflow. 3. Switch back to the other session and check your worklist. Is the previous work item still in the second session? Continued on next page 2007 © 2007 SAP AG. All rights reserved. 57
  66. 66. Unit 2: Workflow Definition in the Workflow Builder BIT601 If the work item is still displayed, refresh the inbox. a) Is the previous work item still in the second session? No If the work item is still displayed in your worklist, you have to refresh the worklist. To do this, choose Folder → Refresh. Task 5: Enter a second user decision. Go from the test environment back to the Workflow Builder in change mode to add another user decision to your workflow definition. If you choose “Change not ok”, a work item is sent to the manager. The work item contains a user decision again. 1. Enter a second user decision into your workflow definition. This step should be specified for the undefined step immediately after the “not_ok” event following the first user decision. Enter the title: Material master change not okay. Enter the decision text Back to Changer and End Workflow. Enter the outcome names Back and End. a) In the basic screen of the Workflow Builder, select the not_okay outcome and click on Create Step. b) Double-click to select User Decision in the dialog box. c) In the User Decision step, enter the following: Title: Material master change not okay Decision text 1: Back to changer Decision text 2: Terminate workflow Outcome name 1: Back Outcome name 2: End Continued on next page 58 © 2007 SAP AG. All rights reserved. 2007
  67. 67. BIT601 Lesson: Structure of the Workflow Builder 2. The agent for the user decision should be the position of your manager, BIT601-MGR##. a) Define the position of manager BIT601-MGR## as the agent responsible for the step. • • • In the Agents section, select Position from the drop-down menu. Select the input help (F4) in the field beside Position. Find Zpos_head_##. Since there is only one position with this abbreviation, it is transferred automatically. • Choose Back to return to the basic screen of the Workflow Builder. Task 6: Activate and test your workflow definition again. 1. Activate and test your workflow definition. a) 2. In the basic screen of the Workflow Builder, select Generate and activate runtime version. Start your workflow and test your modified workflow definition. After you select not_okay in the first decision step, call the Business Workplace of the manager. Execute the work item and select Back to person who made the change. a) Choose Test. The number of your workflow template is displayed in the Workflow field. b) Choose Workflow → Execute or simply use the Execute icon. c) Select the Change not ok decision. d) Log on as manager BIT601-MGR##. e) Choose Workplace from the menu. Open the Inbox folder and click on Workflow. f) Double-click to execute the work item or select the work item and click on Execute. g) Select the Back to changer decision. Continued on next page 2007 © 2007 SAP AG. All rights reserved. 59
  68. 68. Unit 2: Workflow Definition in the Workflow Builder BIT601 Task 7: Check the workflow log for your workflow and check the execution steps of your workflow. 1. Call the workflow log Hint: The Workflow Log screen contains three tab pages The Workflow Chronicle view, Workflow Agents view, and Workflow Objects view. Workflow chronicle view: This view shows all the steps in a workflow that have already been processed or are currently pending, as well as subworkflows. By choosing the Details function for a step, you can find out: • • • Who carried out which detailed actions on this work item and the result of the action When this action was executed Which objects were affected This view is generally used to determine which activities were carried out. The Agents function displays the possible agents and selected agents for a step. The Graphic function displays the graphical workflow log. Workflow Agents View: This view shows the employees that were involved in this workflow up to now. A list is displayed for each employee indicating: • • • Which action was carried out for which step When this action was executed Which objects were affected This view mainly indicates the role an employee has played in executing a workflow. Workflow Objects View: Continued on next page 60 © 2007 SAP AG. All rights reserved. 2007
  69. 69. BIT601 Lesson: Structure of the Workflow Builder This view lists the objects that are related to the workflow or that have been called up to now when the workflow was executed. These objects are: • The “first” object of the workflow Attachments and objects that have been added to individual steps within a workflow A list is displayed for each object indicating: • • Who carried out which detailed action for which task When this action was executed This view indicates which information has been generated as well as how it was generated and processed. Select these tabs and functions to check the details of your workflow. a) Display the workflow log. Switch back to user BIT601-## and choose Workflow Log in the Test Workflow screen. 2007 © 2007 SAP AG. All rights reserved. 61
  70. 70. Unit 2: Workflow Definition in the Workflow Builder BIT601 Lesson Summary You should now be able to: • Create a workflow template with a workflow definition • List the possible step types in a workflow • Use the Workflow Builder 62 © 2007 SAP AG. All rights reserved. 2007
  71. 71. BIT601 Unit Summary Unit Summary You should now be able to: • Create a workflow template with a workflow definition • List the possible step types in a workflow • Use the Workflow Builder 2007 © 2007 SAP AG. All rights reserved. 63
  72. 72. Unit Summary 64 BIT601 © 2007 SAP AG. All rights reserved. 2007
  73. 73. BIT601 Test Your Knowledge Test Your Knowledge 1. The Workflow Builder displays warnings and errors that are displayed when a new runtime version is generated in a section for messages in the lower screen area. Determine whether this statement is true or false. □ □ 2007 True False © 2007 SAP AG. All rights reserved. 65
  74. 74. Test Your Knowledge BIT601 Answers 1. The Workflow Builder displays warnings and errors that are displayed when a new runtime version is generated in a section for messages in the lower screen area. Answer: True Problems are displayed directly in the tool, but only if the message line is visibly displayed . 66 © 2007 SAP AG. All rights reserved. 2007
  75. 75. Unit 3 Business Objects and Business Object Repository Unit Overview The activities that take place at runtime of a business process are related to business objects. This unit introduces the structure of business objects (object types) in the Business Object Repository, and explains how customers can adjust standard object types to suit their own requirements. Unit Objectives After completing this unit, you will be able to: • • • • • • Describe the use of the Business Object Repository Explain the difference between an object and an object type Describe the use of object types in workflow Create a subtype for a standard object type in the system Delegate the subtype, thus making it available in the standard system Extend the subtype by adding attributes, methods, and events Unit Contents Lesson: Structure of Object Types in the Business Object Repository ... 68 Exercise 4: Familiarize yourself with the Business Object Builder. ... 77 Lesson: Adjusting Standard Object Types to Suit Customer Requirements..................................................................... 81 Exercise 5: Generate a subtype for the Material Master supertype and extend it according to your requirements. Then create a delegation from the supertype to the subtype. ........................................ 93 2007 © 2007 SAP AG. All rights reserved. 67
  76. 76. Unit 3: Business Objects and Business Object Repository BIT601 Lesson: Structure of Object Types in the Business Object Repository Lesson Overview The basis for working with business objects in workflow is the Business Object Repository (BOR). Before the Workflow Engine can work with objects in a business process, the objects must be stored as an object type with attributes, methods, and events in the BOR. This lesson provides an overview of the Business Object Repository and the structure of object types in it. Lesson Objectives After completing this lesson, you will be able to: • • • Describe the use of the Business Object Repository Explain the difference between an object and an object type Describe the use of object types in workflow Business Example During your initial workflow design activities, you discover that SAP does not support all of the required functional steps with “standard tasks”. To create your own task, you want to know more about the basic components of a task. For the Workflow Engine, an object type is the basis for all standard tasks. Test and enhance the material master business object type BUS1001. 68 © 2007 SAP AG. All rights reserved. 2007
  77. 77. BIT601 Lesson: Structure of Object Types in the Business Object Repository Business Object Types and the Business Object Repository Figure 20: Business Object Type Using business objects, it should be possible to access object data over a standardized interface. The internal structure of the data remains hidden on the database. A business object is described by the following elements: Object ID Unique ID of the object type Key field Unique identifier of the object at runtime Object name Unique name of the object type Components Differentiated internal structure elements of the object Attribute Property of an object: Entered by, entered on, etc. Methods How can an object be edited? Events Which states can an object adopt? created, deleted, changed, etc. Information about the various ways to access data in SAP systems is covered in overview course BIT100, and also in the specific courses about BAPI programming (CA925/CA926/CA927). 2007 © 2007 SAP AG. All rights reserved. 69
  78. 78. Unit 3: Business Objects and Business Object Repository BIT601 Figure 21: Business Object Repository (BOR) The graphic displays components that use the Business Object Repository: • • • • Object tyoes are developed by the applications, stored in the Business Object Repository (BOR), and edited using the Business Object Builder. BAPIs, which are used to call external functions from the SAP system, are methods of a business object type. In the SAP Workflow, you access the data of an object using the corresponding object type. SAP ArchiveLink, the component used for storing documents in an archive system and linking them to business objects, also uses business object types. To display the Business Object Builder, choose SAP Easy Access → Tools → Business Workflow → Development → Definition Tools → Application Integration → Business Object Builder The Business Object Repository button enables you to carry out a specific search by application component. Each business object type is implemented using an ABAP program. You can use Program to call the program. You can use Utilities → Color legend to explain the various symbols and colors that appear when you display an object type in the Business Object Builder. 70 © 2007 SAP AG. All rights reserved. 2007
  79. 79. BIT601 Lesson: Structure of Object Types in the Business Object Repository Figure 22: Examples of Object Types The SAP Workflow Engine represents the concept and implementation of an object-oriented approach. The object type notification of absence, for example, is implemented as follows: • • • • Key: Number of the notification of absence Attributes: created by, entered on, status, and so on. Methods : Create, approve, edit, delete, and so on. Events: created, deleted, and so on. Objects are specific instances of an object type that can be identified by a unique key, for example, the notification of absence using the number 2000, or the notification of absence using the number 2010. Object types and their components are each assigned one of four statuses: • • • • 2007 Modeled: There is not yet a program for the object type Implemented: The program of the object type can be called, but the implementation can not yet be fully completed. Released: The program of the object type can be called by anyone Obsolete: The object type or the component has been permanently replaced by a different object type or another component. In this case, you must read the documentation for the object to ascertain which object type or component you should use in future. © 2007 SAP AG. All rights reserved. 71
  80. 80. Unit 3: Business Objects and Business Object Repository BIT601 Object Type and Object Instance Figure 23: Object Type and Instance Object types (classes) describe an abstract business object, the characteristics/attributes (data) that belong to it as well as methods and events. The above slide contains the “Aircraft” object type. Specific objects are instances of the object type. You can derive subtypes from object types. Subtypes inherit all of the characteristics (attributes), methods and events of the original object type. You can add characteristics (attributes), methods and events to subtypes. On the above slide, “Cargo plane” and “Passenger plane” are subtypes of the object type. At present, multiple inheritance is not directly supported by SAP business objects. However, SAP provides general interfaces. An object type can implement any number of these interfaces. Business object instances contain actual data (for example, a sales order). An object type can have any number of instances. The lower part of the slide contains specific instances of the "Cargo plane" and "Passenger plane" object types whose keys may be used for unique assignment. 72 © 2007 SAP AG. All rights reserved. 2007
  81. 81. BIT601 Lesson: Structure of Object Types in the Business Object Repository Figure 24: Addressing Instances in the Workflow When a workflow is executed, each of the objects in the workflow have a specific instance which can be used to access the attributes (material number, material description and material type on this slide) and object methods (create, display, change and delete on this slide) in the workflow. In the interface of the task that is currently being executed (a step in the workflow which executes methods), the object instance is always addressed using the _WI_OBJECT_ID variable. The interface of the workflow that is currently being executed does not have a unique name for the object instance. As soon as you create a workflow task in the Workflow Builder, the system usually creates an element automatically in the workflow interface (this element represents the object reference). The name refers to the object type in the BOR. You assign the name if you create an element in the interface. The current object is always addressed in the interface using this element, and not using the key field(s) of the object type. 2007 © 2007 SAP AG. All rights reserved. 73
  82. 82. Unit 3: Business Objects and Business Object Repository BIT601 Objects in the Workflow Figure 25: Objects in the Workflow Workflow are usually started using events. The event defined in the BOR then acts as a triggering event. Events can complete workflow steps. In this case, the event is a terminating event. Tasks call the object type methods and therefore determine the function executed at runtime. You can use attributes in steps (condition, loops, and so on), but you can also use attributes in texts (work item text and the long texts for a task). The definition of objects can be changed without having to modify workflow definitions. 74 © 2007 SAP AG. All rights reserved. 2007
  83. 83. BIT601 Lesson: Structure of Object Types in the Business Object Repository Figure 26: Material Workflow BIT601 Procedure for the Workflow – Business Objekt Repository linkage in the above workflow: First use the structure search ('Business Object Repository' button in transaction SWO1) to find a standard object type for material. Then check the attributes, methods and events of the standard object type to see whether all of the required components exist. The dummy workflow in course BIT601 uses a method “Display change documents” and an event “Material changed”. Neither exist in your standard Y##MARA object type. Since your workflow requires components in addition to those provided by SAP, you need to create a subtype. 2007 © 2007 SAP AG. All rights reserved. 75
  84. 84. Unit 3: Business Objects and Business Object Repository 76 © 2007 SAP AG. All rights reserved. BIT601 2007
  85. 85. BIT601 Lesson: Structure of Object Types in the Business Object Repository Exercise 4: Familiarize yourself with the Business Object Builder. Exercise Objectives After completing this exercise, you will be able to: • Find object types in the Business Object Repository • Request status information of object types • Test object types Business Example During your first workflow design activities, you establish that SAP does not support all of your required functional steps with predefined “standard tasks”. To create your own task, you need to know more about the basic components of a task. In the workflow, an “object type” is the basis for all tasks. In this scenario, you will check and enhance the material master business object type Y##mara (derived from BUS1001). Task: The Business Object Repository contains all of the object types defined in the SAP system. These object types are an important basis for workflow modeling. You must therefore familiarize yourself with navigating in the Business Object Builder. 1. Find the Y##MARA business object type for your group. What is the current status of this object type? 2. Test the Edit method for your T-BBD## material (## represents your group number). Change the values in the fields Old Material Number (View: basic data 1) and Lab/Office (View: Basic Data 2). Enter any value for the Old material number. Enter G## in the Lab/Office field. 2007 © 2007 SAP AG. All rights reserved. 77
  86. 86. Unit 3: Business Objects and Business Object Repository BIT601 Solution 4: Familiarize yourself with the Business Object Builder. Task: The Business Object Repository contains all of the object types defined in the SAP system. These object types are an important basis for workflow modeling. You must therefore familiarize yourself with navigating in the Business Object Builder. 1. Find the Y##MARA business object type for your group. What is the current status of this object type? a) Choose Tools → Business Workflow → Development → Definition tools → Application Integration → Business Object Builder. b) c) Choose Display, d) followed by Basic Data. e) 2. Enter Y##MARA in the Object/interface type field. The current status is displayed under Object Type Status. Test the Edit method for your T-BBD## material (## represents your group number). Change the values in the fields Old Material Number (View: basic data 1) and Lab/Office (View: Basic Data 2). Enter any value for the Old material number. Continued on next page 78 © 2007 SAP AG. All rights reserved. 2007
  87. 87. BIT601 Lesson: Structure of Object Types in the Business Object Repository Enter G## in the Lab/Office field. a) Return to the object type display. b) Choose Edit → Test/Execute or simply Test/Execute. c) Click on Create Instance. d) Enter T-BBD## as the material number and click on Continue. e) Scroll down and select the EDIT method. f) Choose Execute Method. g) Choose Execute in the screen Test Method EDIT: Maintain Input Parameters h) Choose Select view(s). i) Select Basic Data 1 and click on Continue. j) Change the value of the Old material number and Lab/Office fields. (The Basic Data 1 view contains both fields). Entry for the field Old Material Number: Any value Entry for the field Lab/Office: G##. (## represents your assigned group number.) k) l) 2007 Select Save. Select Back twice. © 2007 SAP AG. All rights reserved. 79
  88. 88. Unit 3: Business Objects and Business Object Repository BIT601 Lesson Summary You should now be able to: • Describe the use of the Business Object Repository • Explain the difference between an object and an object type • Describe the use of object types in workflow 80 © 2007 SAP AG. All rights reserved. 2007
  89. 89. BIT601 Lesson: Adjusting Standard Object Types to Suit Customer Requirements Lesson: Adjusting Standard Object Types to Suit Customer Requirements Lesson Overview SAP supplies standard object types, which can be enhanced according to customer requirements. To make an enhancement, a subtype must be defined for a standard object type. This lesson provides a definition of the different components of object types, and explains how a subtype can be used in standard applications by means of delegation. Lesson Objectives After completing this lesson, you will be able to: • • • Create a subtype for a standard object type in the system Delegate the subtype, thus making it available in the standard system Extend the subtype by adding attributes, methods, and events Business Example During your initial workflow design activities, you discover that SAP does not support all of the required functional steps with “standard tasks”. To create your own task, you want to know more about the basic components of a task. For the Workflow Engine, an object type is the basis for all standard tasks. Test and enhance the material master business object type BUS1001. 2007 © 2007 SAP AG. All rights reserved. 81
  90. 90. Unit 3: Business Objects and Business Object Repository BIT601 Definition of a Subtype and Delegation Figure 27: Object Type: Definition of a Subtype The analysis of an existing object type resulted in a need for additional attributes, methods, and events. A subtype definition is then used to adjust the object type in the customer namespace. The subtype inherits all attributes, methods and events of the super type and is open for new customer-specific attributes, methods and events. The key fields of the super type and subtype must be identical. You can only make changes directly in an object type provided by SAP if this modification is described in a SAPNet note. 82 © 2007 SAP AG. All rights reserved. 2007

×