Workflow Development Procedure Model

1
Workflow Development Procedure Model
2

• Two views of workflow development
• (Building a workflow)
• General Procedure Model
• Role-based Procedure Model

3

• General Procedure Model
• Provides an overview of the development process.
• Identifies the activities that need to be
  completed to implement workflows

4

• General Procedure Model Activities
• Prepare Organizational plan
• Define Objects and object type
• Define Create Single-step tasks
• Develop and Test stage
• Define Standard roles
• Identify Events
• Multistep tasks assembled

5

• Organizational plan
• Prepare the enterprise-specific organizational
  plan
• describes the organizational assignment of the
  employees.
• determine the responsibility of employees for the
  execution of individual business activities in
  the form of activity profiles.
• The organizational plan is maintained on a
  client-specific basis.
• The organizational plan that was created for HR
  purposes in SAP Business Workflow may be used as
  well, as long as the workflow functionality and
  the HR application are used in the same client.
• In each client, map those sub-areas and
  organizational structures of the enterprise which
  will be coordinated using SAP Business Workflow.

6

• Objects and object type definition
• Identify all objects involved in your business
  process.
• which business functions you want to map in your
  scenario
• which attributes do you want to access for
  control purposes.
• Check whether the relevant object types with
  their methods, attributes and events are defined
  in the Business Object Repository.
• The grouping of object types in the application
  component hierarchy and the option of searching
  generically for parts of a name help when looking
  for object types.
• Object types whose definition meets your
  requirements, can be used without making any
  modifications.
• If an object type definition does not quite meet
  requirements, extend its definition.
• If a suitable object type is not found, define a
  new object type.

7

• Single-step tasks
• An activity that can be executed within a
  workflow definition or independently.
• Can be a transaction in the R/3 System.
• Identify the single-step tasks involved in the
  business process.
• Establish which object method is to be executed
• Establish who is responsible for executing it.
• Define the single-step tasks by specifying object
  type and method
• Determine the possible agents of the tasks.

8

• Development and Test Stage
• Specify all single-step tasks used as general
  tasks.
• This is for testing purposes
• Check whether single-step tasks are already
  defined.
• Those tasks available are not usually sufficient
• Define additional tasks to meet requirements.

9

• Standard roles
• Object used to determine possible agents for a
  work item.
• Identify possible agent roles in your business
  process.
• Use roles when agents are to be found using
  specific, business, functionally-oriented
  criteria.
• Specifying roles is optional.
• Roles are not required in the test and
  development stage.
• Check for any existing roles.
• If you cannot use any existing roles, define your
  own.

10

• Events
• An event is an occurrence of a change in status
  of an object.
• Identify the events required to initiate and
  control the workflow
• Check whether these events are defined for the
  relevant object types.
• If an event is not incorporated in the standard
  version, add the event to the relevant object
  type definition and ensure that the event is
  created.

11

• Multistep tasks
• A multistep task creates a formal framework for a
  workflow definition.
• Workflow templates can be used as a basis for
  design of new workflows.
• Definition tools can be used to define new
  multistep tasks from scratch.
• To describe a business process, create a workflow
  task and then reference a workflow definition in
  it.

12
(No Transcript)
13

• The Role-based Procedure Model

14

• Definition time
• The process consultant identifies the business
  processes in a company, which are to be mapped
  with workflow technology.
• The workflow modeler then implements these
  processes using the definition tools of SAP
  Business Workflow.
• The workflow programmer provides assistance in
  this task.

15

• Runtime
• At runtime, the workflow is evaluated and managed
  technically by the workflow system administrator.
  
• The process controller caters for this from a
  business perspective.
• The end user in the workflow context is the
  workflow agent, who processes the tasks assigned
  to them in the workflow inbox.

16

• A role-specific procedure model is described for
  each role
• The overall role-based procedure model is derived
  from the overview model and the individual models.

17
(No Transcript)
18
(No Transcript)
19
BOB Business Object Builder
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
Workflow Architecture

• SAP Business Workflow has a three level
  architecture
• Organization level
• provides the link to the organizational chart
• positions, agents (users responsible for tasks)
  are defined
• Process Level
• process level supports the workflow management
  system
• e.g. workflows and tasks are defined and executed
• Business Object Type Level
• provides all technical services e.g.. data,
  forms, and reports called during the execution of
  the Business Workflow

24
(No Transcript)
25

• Business Workflow Architecture

26

• SAP Workflow Symbols

27
(No Transcript)
28

• Demo example and tutorials
• Basic principles of workflow definition and
  execution are provided in a demo example for
  processing a notification of absence.
• There are self-teach tutorials that introduce one
  to selected functions.
• SAP Business Workflow - Tutorials