SAP Workflow Training Handbook
SAP Workflow Training Handbook
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 16
Course Duration: 2 Day(s)
e-book Duration: 13 Hours 30 Minutes
Material Number: 50146321
© Copyright. All rights reserved. iv
Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
● Application Consultant
● Business Process Owner/Team Lead/Power User
● Developer
● Development Consultant
● Enterprise Architect
● Executive
● Help Desk/CoE Support
● Industry Specialist
● Program/Project Manager
● Solution Architect
● Technology Consultant
Lesson 1
Workflows: Concept, Terminology, Example Use 2
Lesson 2
The Five Basic Characteristics of a Business Process 9
UNIT OBJECTIVES
The integration of Organizational Management into the Workflow Engine makes it possible to
link tasks to agents through organizational assignments.
Workflow concept: What processes are particularly suitable for using workflows?
A workflow cannot serve as a substitute for missing SAP functions. If it is not possible to carry
out a function manually, it cannot be carried out by means of a workflow, either. The function
must first be programmed in code before a workflow can use it.
A change in a customer master record can be used as an event that automatically starts a
workflow.
Entering a customer with a large order volume should automatically trigger a workflow that
proceeds through the three subsequent steps.
A workflow glossary is available to help you learn the relevant terminology. It can be found in
the appendix and in the online documentation.
LESSON SUMMARY
You should now be able to:
● Explain Workflows: Concept, Terminology, Example Use
● Use the basic terminology of the Workflow Engine
● Cite criteria that help determine whether it makes sense to use a workflow
LESSON OVERVIEW
This lesson covers the essential components of a business process ( “The Five Workflow
Questions”) and how they interact.
Business Example
The implementation team has gained an overview of how a demo workflow will proceed. As a
member of this team, you want to understand the basic elements of a workflow. To do so, you
need to have a grasp of the five essential components of a business process.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe the five basic characteristics of a business process
● When?
● Who is responsible?
● What?
● With which object?
● In what order?
● Post invoice
● Release purchase requisition
● Change material master
● Approve vacation
● Create customer
● Delete purchase order
● Create requirement coverage request over Internet
Tasks represent the steps in a business process. During definition, a process to be mapped
needs to be divided into individual tasks.
The definition of a workflow specifies the tasks to be carried out in a process, and in what
order.
A task references exactly one object type in the Business Object Repository and exactly one
of the methods defined therein.
In exceptional cases, a business process can involve just one task. A workflow definition can
also be created in these cases.
At the runtime of a workflow, a task is represented by a work item. This work item appears in
the inbox of the recipient.
Figure 10: Defining tasks: possible agents WHO will carry something out?
For each task, the possible agents must be assigned. This group of individuals should include
the employees at your company who are technically capable of carrying out the task at hand.
Figure 12: WHO will carry something out: recipients of a work item
Like methods, the possible events are defined as components of object types in Business
Object Builder. They describe the status changes of objects.
In the Business Object Repository, the event is only defined.
If an object’s status changes while a process is being carried out, the application must trigger
the specific event associated with the change.
Only then will the entire system be aware of the event, which enables a workflow to respond to
it.
● Who does
● When
● What
● By what means
● And in what order
LESSON SUMMARY
You should now be able to:
● Describe the five basic characteristics of a business process
X True
X False
X True
X False
X True
X False
1. An employee has submitted a vacation request. In the subsequent approval workflow, his
or her manager rejects the request. How can the manager include a reason for the
employee?
Before saving the rejection, the manager can create an attachment describing the
corresponding reason.
X True
X False
This is correct. A workflow calls methods that execute the code they contain.
3. One of the advantages of workflows is the ability to create an escalation procedure. This
makes it possible to ensure that a certain employee is notified when a deadline is missed.
Determine whether this statement is true or false.
X True
X False
This is correct. A workflow makes it possible to monitor both entire processes and
individual process steps.
X A A definition
X B A result
X C An action
X D An object
This is correct. In a workflow definition, a step describes the next action to be carried out.
Lesson 1
Organizational Management 24
Lesson 2
Creating an Organizational Plan 31
UNIT OBJECTIVES
LESSON OVERVIEW
This section provides an introduction to the concept and terminology of Organizational
Management in SAP. It also covers the interface and navigation options of “Simple
Maintenance”
Business Example
Your company is deliberating whether to base its agent determination in workflows on an
organizational model. The project members involved first need to get an idea of the basic
possibilities at hand.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain Organizational Management
● Use the interface and navigation options of Simple Maintenance
Organizational Management and the Workflow Engine are aware of the organizational plan
currently in place at a given company in a format called an “active plan version”.
The Workflow Engine uses the currently valid organizational plan to assign work items to the
correct recipients.
Employee changes and reassignments only need to be maintained on the organizational side;
workflow and task definitions are not affected.
The integration of Organizational Management and the Workflow Engine makes it possible to
link tasks and workflow steps with elements of the organizational plan as possible or
responsible agents.
These links enable the system to determine the “correct” agents at runtime; these agents
then become the recipients of the work item in question.
This ensures the greatest possible transparency in business processes and the
responsibilities they involve. Changes can be made to the company’s organizational plan
without needing to modify workflow definitions or reprogram an application.
If you configure the agent determination function based on organizational structures, your
workflow definitions will not need to be modified when employees are reassigned.
There are many ways to link your workflows to your organizational plan.
Example 1: Only one organizational structure is in place for HR for the entire company.
All workflows have to be connected to organizational objects from this struc-
ture. This option does not include any specific organizational structures for
the workflow alone.
Example 2: HR manages the general structure for all employees at the company. To sup-
port the workflow, there is also a small organizational structure for each busi-
ness process.
Example 3: A general HR structure has not (yet) been established for all employees. To
support the workflows, there is one small organizational structure for each
process.
The essential Organizational Management data is stored in customizing tables. This is why the
normal transport link can be used for these entries. Organizational objects are written to
normal customizing requests and transported as such: In the target system, an after-import
method then runs to read out the request and perform the necessary activation steps in the
same system.
This is implemented by means of distribution reports such as RHMOVE30 (manual transport
link); for more, please see Note 138411.
Organizational Management is also covered in the courses HR505 and HR506.
“Simple Maintenance”
Setting up organizational units, positions, and jobs with “Simple Maintenance” only factors in
the most important details. “Simple Maintenance” knows which relationships are required
most often and generates them automatically when you create an object.
Use “Simple Maintenance” to create the majority of the objects and relationships in your
organizational structure.
Menu path: Tools → Business Workflow → Development → Environment → Organizational
Management → Simple Maintenance → Organizational Plan Basic Data → Create
With “Simple Maintenance”, you can:
● Configure and maintain the basic characteristics required for an organizational plan
● Configure and maintain a hierarchy (a chain of command) for the positions in an
organizational plan
● Configure and maintain cost center assignments and standard settings
Since the procedures provided are limited to a minimum, some HR functions are not available.
You will not be able to create or maintain work centers, for example.
All the objects you create with “Simple Maintenance” will automatically be set to the status
“active”.
The maintenance tools in Organizational Management are available to all SAP users in the
basic component.
When using them, you will be working with a main window and three main functions. Each
function is designed 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.
Using the “Create Position” icon, you can create positions and assign them to organizational
units.
The search and selection window enables you to assign position holders by means of drag-
and-drop. Position holders can be SAP users or HR persons.
LESSON OVERVIEW
This lesson covers all the steps involved in creating a workflow-oriented organizational
structure.
Business Example
The implementation team has decided to use an organizational structure for agent
determination and now wants to implement it.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create an Organizational Plan
You have created a new organizational unit and now want to enter the corresponding
positions.
The details on each new position must be entered in the detail area.
Chief positions are marked with the “Head of own organizational unit” flag.
By selecting the organizational unit, choosing the “Create” button, and then selecting the
“Incorporates Position” option, you can create as many positions as you wish for the
organizational unit.
When positions are linked to a job, the positions inherit all the properties of the job. This
includes the tasks linked to the job. Linking positions to a job saves time in assigning tasks
because you no longer need to link each individual position to the respective tasks.
Jobs are not specific to organizational units.
Positions, however, are directly linked to an organizational unit.
During workflow definition, all the necessary tasks are incorporated (for approving requests,
creating purchase orders, updating customer masters, for example).
A user is only able to process a work item at runtime if he or she is defined as a possible agent
for the corresponding task.
In this diagram, you can see all the basic options at your disposal to create such links when
you use the organizational plan for these definitions. At runtime, the aforementioned users
will receive a work item.
● Task 1: User 1 (through manager job)
● Task 2: User 1, user 2 (through manager job / secretary job)
● Task 3: User 1, user 2, user 3, user 4 (through organizational unit)
● Task 4: User 1, user 3, user 4 (through FI manager position / FI employee job)
● Task 5: User 2 (through secretary job)
● Task 6: User 3, user 4 (through FI employee job)
Learning Assessment
X True
X False
2. The Workflow Engine can use the existing organizational plan to forward work items to the
correct recipients.
Determine whether this statement is true or false.
X True
X False
3. The chief position in an organizational unit is the position at the top of the unit. Through
reassignment within the organizational unit, you can designate another chief position.
Determine whether this statement is true or false.
X True
X False
4. In order to process a work item at runtime, the work item recipient must be entered as a
possible agent.
Determine whether this statement is true or false.
X True
X False
X True
X False
4. In order to process a work item at runtime, the work item recipient must be entered as a
possible agent.
Determine whether this statement is true or false.
X True
X False
This is correct. A user will only receive a work item if he or she is defined as a possible
agent.
X True
X False
X True
X False
X True
X False
This is correct. The holder of a position can be an HR person or an SAP user. The Workflow
Engine accepts only SAP users.
This workflow scenario supports your company’s activities in complaints processing by giving
you a fast and efficient way to process, monitor, and complete newly created or activated
quality notifications. This process is mapped in an SAP workflow (WS24500047) that triggers
and controls the execution of the following standard tasks.
● Notification of an authorized person (the notification coordinator, for example) that a new
quality notification has been created or activated and corresponding measures need to be
defined
● Notification of an authorized person that measures have been created for a quality
notification and need to be processed
● Notification of an authorized person (such as the notification coordinator) that all the
measures pertaining to a quality notification have been completed and the notification
needs to be closed (or further corresponding measures defined)
A lead is a business transaction that describes, records, updates, and manages the potential
business interests of a given business partner and the related interactions that take place
over a certain period. The aim is to provide the information collected to the “Sales” area as a
potential basis for deciding whether to create a corresponding opportunity.
The handover of the information contained in a lead to the “Sales” area is supported by the
workflow “Create opportunity from lead” (WS10001011). In this workflow, a distinction is
made regarding whether the opportunity is to be created manually or automatically. If the
lead-specific attributes indicating a lead’s priority and lead group meet certain criteria, the
workflow will automatically create an opportunity. Otherwise, the workflow will initiate manual
creation by sending a work item to the responsible sales employee. After checking the data in
the lead, the sales employee can either reject the lead or have an opportunity created.
Starting the workflow: The workflow starts automatically when the agent saves the lead.
X True
X False
This is correct. Implementing and using a workflow successfully requires the support of
the end users and the department manager in question.
2. In the structure search of transaction PFTC_DIS, you can find all the workflows included
with SAP’s standard applications.
Determine whether this statement is true or false.
X True
X False
This is correct. The structure search function enables you to find all the default workflows.
3. Among the other features of SAP workflows, possible agents are already maintained for all
the tasks they contain, and the event linkages available are already activated.
Determine whether this statement is true or false.
X True
X False
This is correct. Apart from the two characteristics mentioned above, SAP workflows are
finished workflows. Customers always have to maintain the “possible agents” and activate
event linkages themselves.
4. What steps do the tasks involve if you want to use a standard workflow at your company
without making any changes?
Choose the correct answers.
X C Activate the event linkage between the workflow and the application
This is correct. If you want to use the workflow just as it has been defined, carry out steps
A through C.
The workflow runtime system only operates with one client. Assigning a name to a logical
destination ensures that it is unique throughout the system.
As a default, no logical destination exists for the RFC calls of the workflow system.
Create a user with the name WF-BATCH, using the user administration function (transaction
SU01).
● Create this user with the user type “system”.
● Assign this user the authorization profiles “SAP_ALL” and “SAP_NEW”.
In doing so, observe the contents of Note 1574002.
● Other notes on this topic include: 73160, 149344, 547419, and 429938.
● Maintain the user address for this user.
● Also maintain a forwarding address in the user master data (sender address when sending
an e-mail).
The workflow administrator is notified automatically of errors that occur during the runtime
execution of workflow definitions. The administrator should be able to correct workflows with
errors, or find suitable contact persons who can.
Note the following:
Every workflow can have an administrator of its own.
The administrator of a single workflow is defined in the basic data of the workflow template.
The corresponding path is: Basic data → Version-dependent data tab page → Agents .
The generic decision task is the task with which the workflow system carries out a user
decision in the workflow. When you create a step of the type “user decision” in a workflow
definition, the task entered here is copied into the workflow definition. If you change the entry
here, it will affect all workflow definitions with user decisions that are created in the future.
The generic decision task is a task supplied by SAP.
Deadline monitoring for work items means that the scheduled background job is regularly
called at a determined interval to check whether deadlines have been missed since its last
activation. This constant deadline monitoring can be used in each client of your production
system through transaction SWWA.
You must schedule the job in every client that you want to use in the workflow.
The job can only be scheduled once for each client.
With this activity, you schedule monitoring and special handling for background work items
that could not be executed initially because of a temporary error in the underlying object
method. These background work items are then automatically restarted.
To activate monitoring of work items with errors, you must perform the following steps:
● Execute the customizing activity “Schedule Background Job for Work Items with Errors” .
Once all the valid attempts have been made, the work item will be set to the status “error”.
When set to this status, a work item can be found using the selection report, and the error can
be analyzed.
Starting a verification workflow checks the customizing activities that have been carried out.
The workflow checks basic functions in the workflow runtime environment.
A work item is sent to the user who started the verification. This tests that sending a work
item to be executed as a “user decision”, and sending of a notification to the user workplace
are functioning correctly.
While the “user decision” is being executed, you can check several functions at the task level
– for example, displaying or creating an attachment in the Business Workplace.
LESSON SUMMARY
You should now be able to:
● Perform basic customizing of the Workflow Engine
● Execute automatic customizing
Learning Assessment
1. Which of the following statements regarding the customizing of the Workflow Engine are
true?
Choose the correct answers.
X C Entries made through “automatic customizing” can be modified manually after the
fact.
X D Prefix numbers for rules, tasks, and workflows are always a required setting in the
development system.
X E Prefix numbers for rules, tasks, and workflows can be maintained manually or
automatically.
X True
X False
X True
X False
1. Which of the following statements regarding the customizing of the Workflow Engine are
true?
Choose the correct answers.
X C Entries made through “automatic customizing” can be modified manually after the
fact.
X D Prefix numbers for rules, tasks, and workflows are always a required setting in the
development system.
X E Prefix numbers for rules, tasks, and workflows can be maintained manually or
automatically.
This is correct. Most of the settings that are always required can be handled using the
“Perform Automatic Workflow Customizing” function. Existing manual entries (and those
made after the fact) always have priority. Prefix numbers must always be assigned, and
this can only be done manually.
X True
X False
This is correct. Automatic workflow customizing includes entries for the Workflow Engine.
X True
X False
This is correct. In the basic data of a workflow, you can maintain a workflow-specific
administrator who will be notified when an error occurs in an instance of the
corresponding process.
Lesson 1
Functions of the Business Workplace 70
Lesson 2
Alternatives to the Business Workplace 83
UNIT OBJECTIVES
waiting to be processed by SAP’s business applications. Once a task (that is, a work item) has
been carried out and completed, the respective process can continue.
By structuring the organizational units that define the functions and responsibilities within
your company’s hierarchy, you can ensure that the work involved in each process step will be
sent to the right agent.
The worklist contains all the work items (in other words, all the activities to be carried out)
assigned to a particular user. This makes the Business Workplace the most important
interface employees use in their everyday work.
Along with the worklist (containing work items), the Business Workplace displays an inbox for
documents (e-mail, Internet mail, and faxes). This makes it easier for employees to access
the information relevant to them.
You can adjust the work item preview to your needs by means of a user exit. The example
above depicts the work item preview of a demo workflow.
Note:
As of SAP Web Application Server 6.20, BAdIs can be used to control how the
Business Workplace behaves in connection with certain performance parameters.
This relates to concerns regarding large, slow worklists and the frequent need to
refresh worklists.
The feature also makes it possible to manage how the system works with dynamic
columns (see the explanations provided later on in this lesson) and deals with
problems in grouping content within the Business Workplace.
The different characteristics of these BAdIs are covered in the course BIT610; this
lesson focuses primarily on the programming aspects.
Work items can be executed directly from the worklist. Double-clicking one will open the
corresponding application and provide them with the necessary data.
Recipients can view the attachments to a work item and add their own. You can attach many
types of documents to a work item, including SAPscript documents, Microsoft Office
documents, and websites.
The Workflow Engine determines the recipients of each work item. All the recipients selected
can view and execute the work item in question in their Business Workplace. That said, only
one user can execute a work item. This means that other recipients will not be able to carry
out a work item once a user has begun executing it.
Function: Reserve/Replace
A recipient can reserve a work item. A reserved work item can only be executed by the user
who reserved it. If you choose Replace , the work item will be released from its reserved status
and made available again to all the agents selected. The status of the work item will then be
set back to “ready”.
Function: Automatic replacement of work items
If a user aborts the execution of a dialog work item, the item will remain set to In process in his
or her Business Workplace; no other user will be able to view or process it. To make the work
item visible again to all of its original recipients, the user who stopped executing it has to take
explicit action to replace it. As of SAP ERP 6.0 (enhancement package 7), this manual
intermediate step can be automated. You can also install this functionality through SAP Note
1676067.
Automatic replacement is defined for tasks in the maintenance dialog SWW_TASKCUST.
The feature only takes effect in the SAP Business Workplace.
Function: Completing work items manually
You can set the system to require explicit confirmation when a workflow step is complete.
When a work item has been executed, you will see a dialog box in which you can complete the
execution. If you choose Cancel here, the work item will remain in the worklist, set to
“Executed”. In your worklist, you can choose Set to completed for work items set to the status
“Executed”. If this is not done, the work item can be executed or forwarded multiple times.
Function: Forward
You can forward a work item to another user for execution. The manner in which the Engine
handles the forward function is defined within the task under “Properties”.
● If all the employees at hand are possible agents, you can forward a work item to all of
them.
● If the task in question has organizational objects, roles, or users entered as possible agents
and you forward it to a person who is not a possible agent, the Engine will ask you if you
really want to proceed. If you confirm the prompt, the work item will be sent to a user who
is not one of the possible agents.
● You can also deactivate the forwarding function for a particular task.
Hint:
For systems prior to SAP ERP 6.0 (EHP 7), you can install the 12 columns with
SAP Note 1659252.
Step 1:
Define the dynamic columns
→Tools →Business Workflow →→ Development →Definition tools →Worklist Client →Dynamic
Columns for Worklist
You can then select the fields you want from the interface variables of the task in question and
assign a name to the corresponding column.
Step 2:
In the “Grouped according to task” area of the workflow inbox in the Business Workplace,
select the task for which you created a dynamic column.
Then configure your personal layout by choosing the “Choose layout” icon.
In the columns available, you will find your dynamic columns, which you can then drag-and-
drop to the desired location in the display.
Recommendation: Every user should maintain a personal substitute. He or she can then stand
in when necessary – even if there was no time to actively maintain a substitute due to an
accident, for example.
Substitute rules can also be created in the universal worklist ( “UWL” ; see the lesson
“Alternatives to the Business Workplace” ).
The standard work item display hides technical information that is not required for day-to-day
business.
The system makes the user’s work easier by displaying attachments and providing the option
to call them up immediately. Work item descriptions are also integrated, which means they
can be formatted with SAPscript.
It is possible to make immediate changes to priorities.
All additional information (users, attachments) can be called up by clicking a link.
The default work item display contains the tab pages “Basic data” and “Available objects” .
It is possible to add a user-defined tab page to the work item display.
Different Inboxes
The workflow system supports various clients. Workflow users can opt for different clients
without making it necessary to redefine the workflow at hand.
For SAP power users who are responsible for processing all types of work items, the Business
Workplace (in SAP GUI for Windows) is the interface that provides the greatest convenience.
In this inbox, it is possible to configure personal settings in connection with dynamic columns,
previews, and layouts. It also provides access to essentially all the functions that deal with
work items.
Employees who seldom receive work orders as work items can view their work items in their
standard e-mail system. The necessary settings are covered in the lesson “Extended
Notifications”.
It is possible to integrate workflow information with web browsers by means of the universal
worklist (UWL). “Easy Web Inbox” is also available in combination with the Internet
Transaction Server (ITS).
The CRM inbox largely matches the standard inbox. It contains additional folders for:
● “Activities”
● “Overdue activities”
In SAP Supplier Relationship Management (SRM) 7.0, you can use either SAP NetWeaver
Portal or SAP NetWeaver Business Client.
● An e-mail containing descriptive text and links that enable the user to execute a work
item directly, display its contents, or switch to the Business Workplace
● An e-mail containing descriptive text and attachments that enable the user to execute
a work item directly, display its contents, or switch to the Business Workplace
● Sends a general text that informs the user of work items in his or her Business
Workplace (contains system and client details)
● Sends a short text on the work item (along with system and client details)
An e-mail notification can contain one or more work item notifications. The e-mail notification
also includes details on the sender and recipient.
E-mail addresses can also be read from the PD organizational structure (infotype 1205)
instead of from the user master in question. The language of e-mail notifications does,
however, depend on that same user master record.
These e-mails can be displayed in HTML, which greatly improves their appearance and
usability for your employees. E-mails can contain links to SAP GUI for HTML. It is also possible
to combine multiple work items in the same e-mail. Work items that are not based on SAP GUI
for Windows (WebFlow services or WebDynpro, for example) can be called up directly from
within the respective e-mail.
If Single Sign-On is activated, no username or password will be required. If Single Sign-On is
not activated, the user’s password will be required the first time he or she logs on; it will not be
required again until after the session is closed.
For generic decision tasks, e-mails can be sent that make it possible to carry out a decision
directly. Notifications can be forwarded and executed by users with sufficient authorization.
Most of the settings at hand can be configured on an individual or group-wide basis. One user
group can receive summary e-mails in HTML, for example, while another can receive specific
notifications as text-only e-mails.
Extended notifications enhance the methods users were familiar with in the past. Here, a
customizing framework is provided that facilitates the configuration of different types of
notifications in a user- and group-specific way (which was previously only possible using
corresponding variants of batch jobs).
For administration purposes, a browser-based BSP application is available through the
transaction SWNADMIN, which provides a very easy means of saving the necessary settings.
However, this function can only be accessed by one agent at a time.
In addition, SAP GUI-based cluster maintenance (transaction SWNCONFIG) is available,
which makes it possible to maintain additional functions. This is where alternative service
handlers can be stored (for example).
One customer’s demands prompted SAP to launch a campaign in which it implemented apps
for 25 functions in the space of eight months. These functions cover business scenarios
frequently used by a wide variety of users. These apps were rolled out at SAPPHIRE 2013.
Since then, SAP applications have realized more than 100 additional functions as SAP Fiori
apps.
You can output data of any level of complexity, including that which is not related to a
particular business object. To do so, create an OData service and use a UI extension.
You can use the following extension points:
● CustomerExtensionForObjectListItem
● CustomerExtensionForObjectHeader
● CustomerExtensionForInfoTabContent
● CustomerExtensionForNoteTabContent
● CustomerExtensionForAttachmentTabContent
● CustomerExtensionForAdditionalTabs
In approval inquiries, you can also use the UI control IDs ARNoteIconTabFilter and
ARAttachmentIconTabFilter .
Note:
For further details on implementing and using SAP Fiori, please refer to the course
SAPX03, “SAP Fiori Implementation and C”.
LESSON SUMMARY
You should now be able to:
● Cite the alternatives to the Business Workplace
● Put the use of the universal worklist (UWL) into context
● Describe the available notification functions
1. Every work item a user receives for processing is always visible in the Business Workplace.
Determine whether this statement is true or false.
X True
X False
This is correct, Yes, the Business Workplace is the main user interface.
2. Alternative workplaces – the universal worklist in the portal, for example, or receiving
notifications about a work item by e-mail – can also be used.
Determine whether this statement is true or false.
X True
X False
This is correct. Yes, other ways to receive notifications about a given work item can be
defined.
Users can configure their own worklist layouts by selecting columns from the column set
and/or defining their own (dynamic) columns.
4. A user can only forward a work item to the possible agents for the task at hand.
Determine whether this statement is true or false.
X True
X False
This is correct. The definition of the task at hand determines whether and to whom it can
be forwarded.
5. Once a user has reserved or executed a work item, it can only be replaced manually by the
same user or the workflow administrator. A new function in SAP ERP 6.0 (EHP 7) makes
automatic replacement possible.
Determine whether this statement is true or false.
X True
X False
This is correct. The Function was introduced with ERP 6.0, EHP 7.
6. What are the different views available in the end-user workflow log?
Choose the correct answers.
This is correct. The workflow container view is accessible through the technical log.
7. Through the workflow outbox, users can access work items they have already carried out.
Determine whether this statement is true or false.
X True
X False
This is correct. In the workflow outbox, each agent sees the instances he or she has
started and the work items he or she has executed or forwarded.
8. Using transaction SWNADMIN, you can access a Business Server Page application that
enables you to customize how e-mail notifications are handled for work items.
Determine whether this statement is true or false.
X True
X False
This is correct. Within transaction SWNADMIN, the BSP SWN_CONFIG gives you an easy
way to customize these e-mail notifications.
LESSON OVERVIEW
This lesson offers an introduction to the functional core, possible agents, and maintainable
texts of standard tasks.
Business Example
The implementation team starts out by exploring the characteristics and possible uses of
standard tasks.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain characteristics and usage of standard tasks
Tasks represent actions that need to be carried out. A task always refers to exactly one
method of an object type.
The action involved can be a step that the system executes on its own in the background. In
these cases, no possible agents are assigned.
The action can also be a dialog task. In these cases, the task has possible agents, which can
be assigned by following the menu path:
Additional Data → Maintain Agent Assignment
Work item text is the text found in the “Title” column of the worklist.
The task description appears in the work item preview and the work item detail display.
A notification can be sent to the corresponding recipient when a work item has been
completed.
If simple deadline monitoring has been set up for a given workflow step, a corresponding text
must be maintained for the respective deadline type.
In all texts, variables can be included that are supplied with values from the workflow interface
at runtime.
Texts for descriptions, notifications, and missed deadlines can be found on the Description
tab page.
Workflow Builder
Workflow definitions are created in the Workflow Builder and displayed in a graphical format.
The Workflow Builder is divided into the following areas:
● Steps: A tree structure showing the sequence of workflow steps. Double-clicking a step
displays the corresponding step definition.
● Containers: Variables of the workflow interface
● Tasks: Here, tasks and workflows are available for easy insertion and navigation.
● Document templates: Displays the available document templates
● Wizards
● Team working
● Overview: Displays the whole workflow definition
● Insertable step types: All the step types available for drag-and-drop into the workflow
definition
● Messages: All messages generated in where-used lists and workflow tests are displayed
here.
● Workflows with this definition
Triggering Events
As soon as a user creates a notification of absence, the application generates the event
“Notification of absence created”.
In the basic data of the workflow template to be initiated, this event linkage must be entered
and activated.
The “Notification of absence created” event then triggers all the workflows actively linked to
it.
Once a workflow is triggered by an event, all subsequent processing steps specified in the
workflow definition will be carried out in the sequence defined until the workflow is complete.
LESSON SUMMARY
You should now be able to:
● Explain characteristics and usage of workflow templates
● Cite the main characteristics of a workflow template
● Activate the event linkage of an SAP workflow
● Use the SAP workflow
● Describe the basic interaction between definition and runtime
X True
X False
This is correct. Yes; an object type describes an object at runtime. At runtime, the system
works with specific instances of the object type at hand.
2. Possible agents are the employees at a company that are technically able to execute a
certain task.
Determine whether this statement is true or false.
X True
X False
This is correct. Possible agents represent the overall pool of employees who are allowed to
carry out a given task.
Lesson 1
Exploring Specific Transactions for Runtime Monitoring 127
Lesson 2
Using the Workflow Log 136
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explore specific transactions for runtime monitoring
● Execute runtime reports for the administrator
● Execute runtime reports for the end user
Overview
The SAP database contains all of the information required for workflow processes. This
information can be evaluated using standard or customer-specific reports.
Runtime reporting has two main purposes:
Workitem Selection
Selecting the “Additional Data” indicator will also display the number and version of the
workflow/task, the system administrator, and the user who executed the work item.
Depending on your selection criteria, the report might display a list of work items. By double
clicking, you can display these work items to obtain detailed information.
You can only execute and change the work item if you are a possible agent of this work item.
LESSON OVERVIEW
This lesson takes a closer look at the different views and display options available in the
workflow log.
Business Example
Having gotten comfortable with a number of transactions for workflow runtime monitoring,
the implementation team now wants to use the further options provided by the workflow log.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use the workflow log
Different Logs
Figure 94: Workflow Logs from the Business and Technical Perspective
The workflow log offers different modes for different information requirements. Each mode
answers certain questions and is geared toward a particular user group. The following modes
are available:
● Modes for agents (no technical information)
● Modes that include technical details (those required by a workflow administrator, for
example)
The information you see depends on the mode you have selected in your personal workflow
settings. If you have selected the technical view, no information will be filtered out.
Workflow administrators should activate the technical view in order to avoid seeing a
simplified version. (When displaying a workflow’s log, this could prevent an administrator
from seeing all the steps at hand, which could lead to an incorrect diagnosis.)
Standard Log
The “View: WF Chronicle” tab page of the workflow log (ActiveX) shows a hierarchy of all the
workflow steps that have been processed or are awaiting processing. If the workflow at hand
contains a structure of (sub-)workflows, they will also be displayed.
The “Details” function lists the following details on a given step in the lower portion of the
screen:
● Who executed what detailed action with the work items in question, and what the results
were
● When this action was carried out
● Which objects were involved
● If you change a version of a workflow definition in a significant and incompatible way by:
- Adding steps
- Deleting steps
- Repositioning blocks (cut, paste, and so on)
- ...and no new version is generated,
● ...the graphical workflow log may no longer display the sequence that has taken place.
This problem mainly arises in the development and testing phase when a workflow definition
is modified, executed, modified again, and executed once more.
While the list-based workflow log only presents past values from the workflow runtime tables,
the graphical workflow log displays the version of the executed workflow according to its
current definition.
If the version has been changed significantly, the graphic will reflect the modified workflow
definition, but the workflow itself will follow a different sequence. As a result, the workflow
attempts to insert information from runtime tables into a workflow definition that looks
completely different. What anomalies can you look for to identify this problem?
● Steps that seem to have been skipped (this is especially apparent in a sequence of steps)
● All steps are displayed as “Executed”, even those in an alternative sequence (not a loop)
● The workflow is finished, but its execution appears to have had no direct result
LESSON SUMMARY
You should now be able to:
● Use the workflow log
Lesson 1
Enhancing SAP Workflows 144
Lesson 2
Configuring Workflows 148
Lesson 3
Using Workflows at Your Company 153
Lesson 4
Explaining Workflow Roles 159
Lesson 5
Explaining SAP Authorizations 161
Lesson 6
Explaining Steps of a Workflow Project 162
Lesson 7
Exploring Transaction Codes and Menu Paths 167
UNIT OBJECTIVES
LESSON OVERVIEW
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Enhance SAP workflows
Message texts (long texts and work item text) can always be modified.
It is also possible to redefine texts according to your needs even when you want to use
templates without other changes.
Through workflow configuration, you can modify a step in an SAP workflow without having to
copy it first.
Workflow configuration enables you to:
A workflow’s configuration does not allow you to modify the corresponding workflow
definition.
If you want to add a new step to an SAP workflow or modify a step in a manner not listed
above, proceed as follows:
Work item text is defined at the task level and displayed in the worklist at runtime.
SAP tasks are provided with standard texts that can be redefined according to each
customer’s needs.
Procedure:
It is possible to include variables in work item text; these variables supplement the text with
current runtime data. System information, such as the current date and time or the user who
initiated the workflow, will then be inserted in place of the entered variables at runtime and
displayed in the worklist along with the fixed text of the work item in question.
Procedure for including variables:
● Bring up the work item text in question
● Move the cursor to the place where you want to insert a variable
● Select the desired variable from the interface
Long texts in SAP workflows can also be redefined according to your needs.
Long texts can be found in each task’s definition on the “Description” tab page.
You can maintain the following texts:
● Task description (appears in the work item preview in the Business Workplace and the
detail display of the work item)
● Completion text (sent to a user to be specified when the work item is complete)
- Work item was not processed in the period specified
● Missed deadline text (sent to a user to be specified if the work item was not processed in
the period specified
You can include variables in long texts by following the menu path: Include → Expression .
LESSON SUMMARY
You should now be able to:
● Enhance SAP workflows
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Configure Workflows
Workflow Configuration
● Purpose
- Configuration enables you to incorporate your own specific data into SAP workflows
- SAP workflows do not need to be copied
- SAP workflows do not need to be modified
● Restrictions
- Only available for the workflow template type (WS), NOT for the workflow task type
(WF)
Configuration overwrites the information in a workflow definition. This is why the Workflow
Builder indicates whether a configuration exists in place of the workflow definition at hand.
You can find this information in the basic data of the workflow on the tab page
“Technical information” .
At runtime, the data in the configuration is used.
Structural changes cannot be made to workflow definitions.
If you want to add or delete a step (for example), you will need to copy the workflow template
in question.
You can then modify the duplicate according to your needs.
The old workflow task type (WF) cannot be configured.
If you want to make changes to areas that cannot be configured, copy the SAP workflow in
question to a workflow template of your own.
You can then modify the workflow template however you see fit.
Expression work items:
As in the case of express e-mails, a notification will appear to let you know when an express
work item has been placed in your inbox.
Here, the corresponding workflow step must be set to priority “1” .
Notification refers to the process of informing a specified recipient that a particular work item
has been completed.
Simple deadline monitoring refers to the process of informing specified recipients that a
particular work item was not processed within a specified period.
For each workflow step, the following deadline types are available: “Requested start”, “latest
start”, “requested end” and “latest end” .
You can access workflow configuration by calling transaction SWDD_CONFIG or following this
menu path: → Tools → Business Workflow → Development → Definition tools → Workflow
Configuration .
Double-clicking a step will bring up a detail view that provides all the available configuration
options.
Fill out the detail view according to your preferences.
Requested start:
● Earliest possible time for the start of processing
● Strictly speaking, a requested start is not a form of deadline monitoring; it is the time at
which a work item first appears in an agent’s inbox.
Requested end
● The time by which a work item should be processed
Latest start
● The latest time by which the processing of a work item must begin
Latest end
● The time by which the processing of a work item must be complete.
The different deadline types available in deadline monitoring can be used to assemble an
escalation procedure.
Example:
A purchase requisition is to be approved within two weeks. If it is not, the “requested end”
takes effect and the agent currently selected is notified.
If the purchase requisition has still not been processed after three weeks, the “latest end”
takes effect and the manager of the agent in question is notified.
It is possible to start any manner of subsequent processing using modeled deadlines. (Course
BIT601)
Deadlines can be defined to reference the start of a workflow, the start of a work item, or the
content of a variable.
If a deadline is missed in the context of simple deadline monitoring, the specified recipient is
notified.
critical processes with deadline monitoring, approval procedures, the archiving of incoming
documents (and automatic forwarding to the people responsible for them at your company),
and the issue of notifications when certain events occur.
After determining which process you want to implement, you will need to sketch out the flow
logic of all the steps in your chosen business scenario.
Each step must be assigned an SAP function.
For dialog steps, you will need to assign employees who are involved in the workflow at hand.
When planning agents, always be sure to specify a particular group (the clerk position in CO or
an organizational unit for major project consulting, for example) or individual names (Jones,
Miller, and so on).
In any case, avoid entering anonymous information.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain workflow roles
Workflow Roles
Overview of workflow roles:
● Prerequisites
- The system includes roles for all the typical workflow users. When you assign a role to a
user, a role-based user menu will appear on the SAP Easy Access screen.
- Each role has its own documentation
● Characteristics
- Workflow roles assume that the Workflow Engine will be used in a particular way. The
assumption is also made that the corresponding IMG activities have already been
completed.
- The workflow roles used are stylized, but you can still use them at your company even if
your working methods differ.
You can specify roles as possible agents for a task, or enter the agents responsible for a given
workflow step.
EBP deals exclusively with the assignment of roles.
LESSON SUMMARY
You should now be able to:
● Explain workflow roles
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain Steps of a Workflow Project
This decision will also help determine the components you will need to install in the process
(an ITS and a web server, for example).
Before getting started with training, decide whether all users will participate or only a select
group (“snowball” training).
If you can only train a select group of users, documentation is very important.
Make sure that the necessary facilities are available and that representatives from every
process phase receive training.
Even after all your system tests are complete, you should check whether the system is
running properly.
Success Factors
LESSON SUMMARY
You should now be able to:
● Explore Transaction Codes and Menu Paths