Vous êtes sur la page 1sur 4

PRINT FROM SAP HELP PORTAL

Document: General Procedure Model URL: http://help.sap.com/erp2005_ehp_06/helpdata/en/c5/e4a964453d11d189430000e829fbbd/content.htm Date created: June 22, 2013

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

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

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 4

General Procedure Model


Purpose
With SAP Business Workflow you can map business processes in the SAP System and process them (several times if required) under the control of the workflow system. A workflow management system can process and monitor structured processes that: Encompass a sequence of activities Reoccur in the same or similar forms Involve several people of groups of people Require a lot of coordination In addition to this general procedure model for working with SAP Business Workflow, there are also role-specific procedure models. For descriptions of these procedure models, refer to Workflow Roles .

Prerequisites
Before working with SAP Business Workflow, you should have a clear idea of the areas in question and the extent to which you want to change and adapt business processes, and pass them over to electronic process control.

Process Flow
Use the following procedure model as orientation when working with SAP Business Workflow. Organizational plan The enterprise-specific organizational plan describes the organizational assignment of the employees. The aim of this is to determine the responsibility of employees for the execution of individual business activities in the form of activity profiles . You maintain the organizational plan on a client-specific basis. You can use an organizational plan that was created (or is still being created) for HR purposes in SAP Business Workflow as well without making any changes, as long as the workflow functionality and the HR application are used in the same client. Generally, however, in each client you (only) map those sub-areas and organizational structures of your enterprise, in which you also coordinate business processes using SAP Business Workflow. For further information, refer to Enterprise-Specific Organizational Plan. Objects and object type definition You identify all objects involved in your business process. You sort out which business function you want to map in your scenario and which attributes you want to access for control purposes. You 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 existing object types. If you find an object type whose definition meets your requirements, you can use it without making any modifications. If you find an object type whose definition does not quite meet your requirements, you extend its definition. If you do not find a suitable object type, you define your own object type. For further information, refer to Extending and Adapting Object Types . Tasks You identify the tasks involved in your business process. You establish which object method is to be executed with the task and who is responsible for executing it. You then define the tasks by specifying object type and method, and determine the possible agents of the tasks.

In the test and development stage, you should make all the tasks used general tasks. You check whether tasks are already defined. The tasks available are not usually sufficient, meaning that you have to define additional tasks to meet your requirements. For further information, refer to Single-Step Task . Rules for agent determination You identify possible agent rules in your business process. You use these rules when agents are to be found using specific, business, functionally-oriented criteria.

Specifying rules is always optional. You can initially do without rules in the test and development stage. You check whether you can use existing rules. If you cannot use existing rules, you define your own. For further information, refer to Rule.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 2 of 4

Events You identify the events required to initiate and control the workflow and check whether these events are defined for the relevant object types. If you require an event that is not incorporated in the standard version, you must add the event to the relevant object type definition and ensure that the event is created. For further information, refer to Event. Workflow To describe a business process usually comprising several steps, you create a workflow. You can use SAP workflows as templates for your own developments to help you make a start. You use the Workflow Builder for the definition. You can also create new workflows there directly. From a technical point of view there is a multistep task for every workflow. For further information, refer to Multistep Task . Demo example and tutorials You can learn the basic principles of workflow definition and execution in the demo example for processing a notification of absence. For further information, refer to Demo Example: Processing a Notification of Absence. There are tutorials that introduce you step-by-step to selected functions. See SAP Business Workflow - Tutorials .

General Procedure Model


Purpose
With SAP Business Workflow you can map business processes in the SAP System and process them (several times if required) under the control of the workflow system. A workflow management system can process and monitor structured processes that: Encompass a sequence of activities Reoccur in the same or similar forms Involve several people of groups of people Require a lot of coordination In addition to this general procedure model for working with SAP Business Workflow, there are also role-specific procedure models. For descriptions of these procedure models, refer to Workflow Roles .

Prerequisites
Before working with SAP Business Workflow, you should have a clear idea of the areas in question and the extent to which you want to change and adapt business processes, and pass them over to electronic process control.

Process Flow
Use the following procedure model as orientation when working with SAP Business Workflow. Organizational plan The enterprise-specific organizational plan describes the organizational assignment of the employees. The aim of this is to determine the responsibility of employees for the execution of individual business activities in the form of activity profiles . You maintain the organizational plan on a client-specific basis. You can use an organizational plan that was created (or is still being created) for HR purposes in SAP Business Workflow as well without making any changes, as long as the workflow functionality and the HR application are used in the same client. Generally, however, in each client you (only) map those sub-areas and organizational structures of your enterprise, in which you also coordinate business processes using SAP Business Workflow. For further information, refer to Enterprise-Specific Organizational Plan. Objects and object type definition You identify all objects involved in your business process. You sort out which business function you want to map in your scenario and which attributes you want to access for control purposes. You 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 existing object types. If you find an object type whose definition meets your requirements, you can use it without making any modifications. If you find an object type whose definition does not quite meet your requirements, you extend its definition. If you do not find a suitable object type, you define your own object type. For further information, refer to

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 3 of 4

Extending and Adapting Object Types . Tasks You identify the tasks involved in your business process. You establish which object method is to be executed with the task and who is responsible for executing it. You then define the tasks by specifying object type and method, and determine the possible agents of the tasks.

In the test and development stage, you should make all the tasks used general tasks. You check whether tasks are already defined. The tasks available are not usually sufficient, meaning that you have to define additional tasks to meet your requirements. For further information, refer to Single-Step Task . Rules for agent determination You identify possible agent rules in your business process. You use these rules when agents are to be found using specific, business, functionally-oriented criteria.

Specifying rules is always optional. You can initially do without rules in the test and development stage. You check whether you can use existing rules. If you cannot use existing rules, you define your own. For further information, refer to Rule. Events You identify the events required to initiate and control the workflow and check whether these events are defined for the relevant object types. If you require an event that is not incorporated in the standard version, you must add the event to the relevant object type definition and ensure that the event is created. For further information, refer to Event. Workflow To describe a business process usually comprising several steps, you create a workflow. You can use SAP workflows as templates for your own developments to help you make a start. You use the Workflow Builder for the definition. You can also create new workflows there directly. From a technical point of view there is a multistep task for every workflow. For further information, refer to Multistep Task . Demo example and tutorials You can learn the basic principles of workflow definition and execution in the demo example for processing a notification of absence. For further information, refer to Demo Example: Processing a Notification of Absence. There are tutorials that introduce you step-by-step to selected functions. See SAP Business Workflow - Tutorials .

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 4 of 4

Vous aimerez peut-être aussi