1) How to handle Exceptions in workflow 2) Steps in mind before transporting a workflow 3) Two workflows say WS1 FOR PURCHASE ORDER WS2 FOR PURCHASE REQUISITION. How to do both the workflows in a single one. 4) There are 2 managers say MANAGER1 AND MANAGER2. If there is a purchase order of more than 5000 then manager1 has to approve it, if PO>5000 then first MANAGER1 then MANAGER2 has to approve simultaneously. How is it done. 5) how to debug a WORKFLOW.

1. Is there a good book about this subject?Yes, "Practical Workflow for SAP" by Rickayzen, Dart, Brennecke and Schneider. Available from SAP press at the end of July. A german translation of this workflow book is also available directly from Galileo-Press, the publisher. 2. How do I convince my company to use workflow?Feedback from user groups emphasizes that although the competitive advantage gained by using workflow eclipses the financial savings, it is the financial savings that are the deciding factor when obtaining support from senior management. Projects getting the blessing at the CEO level are much easier to manage, and far more likely to reach their goal within the project time frame. So plan well, and don't neglect the business case. Because the following questions deal with the financial case in more detail, this section will finish by listing the competitive advantages. The quality of the process is assured by pushing the relevant information together with links to related transactions directly to the user. Managers don't have the time to search for information so give them what they need to reach the correct decision. Cycle time is reduced by pushing the process directly to the users. The users receive notification of a task immediately and can even be prioritized by the system. The tasks are performed consistently and diligently by the users. The workflow system pushes all the necessary information needed to perform a task, including a clear description of what has to be done, how to do it and the impact this task has on the business process for your company. At any time, the user can check the list of tasks pending and determine at a glance which are the important tasks, and which tasks can be completed the next day without any negative impact. The process instance is transparent. Any user can check at any time how far the process has progressed and which stage the process has reached. For example the call center can immediately see the status of a purchase order, an employee requisitioning a purchase would see at a glance if a colleague has been sitting on it for too long, the ad hoc notes made when approving an engineering change request are visible long after the request has gone into production. The process is flexible, allowing it to be changed on the fly without retraining everyone involved. The description accompanying the change takes care of on-the-fly process improvements. Deadline handing ensures that users perform the tasks within the time planned. Escalation measures ensure that the failure to meet a deadline can be corrected by other means. Intelligent reporting highlights the weaknesses of a process. Often there is a simple cure to such weaknesses such as reeducating the users involved in the bottleneck or providing additional information (automatically). The difficulty of a non-automated process is identifying such bottlenecks. The process definition is transparent. You can see at a glance how the process works and who will be selected to perform the different tasks. Think of the workflow as the process book. If you can spot the pattern and define the process without headaches, you can create a workflow definition effortlessly. However, don't forget that if a company has business processes that are erratic and lack a consistent pattern, the company is very likely to be losing a lot of money in terms of lost contracts, labor intensive administration and low customer confidence. It is my personal opinion that automating exactly this type of processes will yield the best returns, but only if you limit yourself to automating the basic skeleton of

the process first. Don't get bogged down in the detailed exception handling. That can be done in the next phase once you've checked the process statistics and determined which exceptions are worth tackling. As with most software the reasons for automating business processes are primarily to increase the competitive edge of your company and to cut costs. Although the increase in competitively gained by radically reducing process times is by far the most insignificant gain from workflow, you should not ignore the cost savings. The cost saving calculations are needed by upper management in order to approve workflow projects. This upper management signature will be very useful in different phases of the project and cannot be underestimated. 3. How do I calculate the cost saved by workflow?Calculate the cost of the manual process in terms of man hours. Don't neglect the time spent gathering information. Ask the following questions: Is the user forced to log into different systems, or scan through printed documentation....? Does a skilled user spend time on parts of a task, where less skilled (less expensive) user could do the groundwork? I.e. Can a single task be split into skilled and unskilled tasks to free the skilled worker for work where his/her skills are really needed? Is time spent researching the progress of a process (usually done by someone not involved in the process directly)? Is time spent determining who to give the task to next? Probably the most significant cost will the be the cost of failure? How often does the process fail? What is the real cost of failure? Loss of a contract? Loss of a customer? Law suit? If the failure can be rectified, how labor intensive is it? 4. What are typical costs saved by workflow? A manually processed accounts payable invoice will cost about 25 USD. After workflow enabling about 15 USD (one example based on customer feedback from a user group meeting). 5. What are typical reductions in processing time caused by workflow? A traditional paper based approval process involving three people will typically take seven days to complete. The automated process will take one day (results based on customer feedback). 6. What do customers say are the strengths of SAP WebFlow? WebFlow is the internet functionality of SAP Business Workflow. Based on customer feedback from the various regional users groups, the main strengths of SAP Business Workflow are: Robust production workflow system, (upgrade continuity with the rest of the SAP system, versioning, scalability, no gluing....) Standard workflow templates delivered by SAP can be used out-of-the-box or tweaked to deliver the optimum business process for your company. Workflows can be up and running including training in under a day (thanks to the knowledgeware delivered as part of the template packet). Seamlessly integrated into the SAP environment, be it R/3, Business to Business Procurement, CRM, APO, mySAP.com.... Examples of integration are: Business Reporting (WIS), Context sensitive availability at any time through the system menu (available anytime, anywhere) 

More and more standard SAP functionality is being provided by using SAP Business Workflow so your homegrown workflows fit the landscape exactly, More and more workflow functionality is available directly within the SAP transaction or Web MiniApp. WebFlow is becoming more and more important because companies are no longer being judged by their own performance but by the combined performance of the company AND its partners. In other words it is not enough that the business processes within your company run smoothly and faster than your competitors. You have to ensure that the processes between you and your partners are also as fast, efficient and flexible as possible. WebFlow delivers this. 7. How are users notified about their work pending? The users are informed by a work item which you may think of as being very like an e-mail. The difference is the work item contains intelligence and by executing the work item you will be taken to the form or SAP transaction that makes up the step in the workflow. This form or transaction could be a decision, a request for information or a request for confirmation that a particular task has been performed. The work item is usually accompanied by a description of what has to be done, where to refer to when assistance is needed (help desk, intranet...) and a summary of information about the business object or process which enables the operator to attack the task immediately. This work item can be received and executed in MS OutlookÒ, Lotus NotesÒ, mySAP Workflow MiniApp or the SAP integrated inbox. If this is not enough, the workflow system can transmit e-mail notifications directly to any mail system, informing the user of the need to log in to the SAP system to execute the task. The e-mail notification is done on a subscription basis so that users can de-subscribe from this service if they already check their work item inbox regularly. 8. What workflow reporting is available and is it useful? Standard workflow reports exist which allow the administrator to check statistics such as the frequency and average duration of the workflow processes. However the real strength of the workflow reporting is that it allows reports to be configured which analyze the process statistics in combination with the data involved within the workflow process and the organizational units associated with the process. For example you can determine the average time invested in a failed contract renewal request, the time taken to create material masters in different plants or the frequency of rejected purchase requisitions on a department to department basis. Often, big reducations in cost or cycle time can be obtained without touching the workflow definitions. Reeducating a particular group of users or incorporating supplementary information in a work item description can often cause dramatic improvements on the cycle times of particularly critical subsets of the process. It is not unusual that this may have a big impact on specific products, plants or organizational units. This will show up in the WebFlow reporting in LIS or the Business Warehouse but it might not show up in traditional statistical workflow reporting. Even though the average time does not change significantly, the impact on costs and profit can be dramatic. 9. How do I choose who to distribute the tasks to? A work item is assigned to one or more users. Whoever reserves or executes the task first wins and the work item vanishes from the other users' inboxes. This eliminates the need to assign the user to one single user. I.e. No need for complicated algorithms to determine which single user will receive the work item and no need to worry about what will happen when one user is ill for the week (also taken care of by sophisticated substitution mechanisms which can be linked to the SAP organizational model). Tasks can be assigned to an organizational unit but the strength of the workflow system is to enable business rules which select users according to the data being processed. For example, you might have one group of users associated with one quality notification type. The workflow can be configured to query the QM module directly to determine the users. You can define fallbacks using the default role associated with a task and allow agents to be specified on the fly by a supervisor. Tasks can be assigned to office distribution lists which is useful when you want your users to subscribe or unsubscribe to a particular task. A typical use of this would be where you have a work rote or want to reduce user maintenance to an absolute minimum. The users subscribe or unsubscribe by joining or leaving an office distribution list (one mouse click). 10. What happens when a deadline is missed? 

This depends on your workflow definition. In the simplest case an e-mail is sent to another user by the system (typically your supervisor so watch out!). However in more sophisticated scenarios a missed deadline can redirect that path that the workflow takes. One customer uses deadlines to automatically make an approval if the deadline is missed (at about the eighth approval level!!!). This gives the user the chance to make rejections but does not force him/her to go into the system to approve the other 99.9% of the requests. In safety critical environments the workflow might trigger off preventative action when a deadline is missed or might put other processes on hold. There is no limit as to how you can use this functionality. 11. What deadlines can be monitored? Many different types of deadlines can monitored. At the single workflow step level you can define deadlines which trigger when the work item has not completed within a certain time and other deadlines when no one starts working on the work item within a given time. You can specify the task deadline statically (e.g. 1 week) or dynamically (e.g. 1 week for material type A and 2 weeks for all the other materials). The offset can be related to the step (e.g. you have 1 week to complete this step) or related to the process (e.g. complete within 2 weeks of the complete process starting, irrespective of how long your colleagues have hogged the previous steps). Last but not least, deadlines can be set for sub-processes, which is often more important than the deadline of a single step in a workflow. 12. How can I check the status of a workflow? This is one of the very cool features of SAP Business Workflow. You can usually navigate directly from the business object to check the workflow progress. For example, while viewing a purchase order you can select "workflow" from the system menu or toolbar and you will see a list of workflows related to the purchase order. Usually just one, but if you have created a few of your own and these have been triggered you will see the status of these too. And that is not all. You also see a simplified summary of all the steps that have taken place so far including who performed them, when they were executed and which ad hoc notes were attached. 13. How are workflows triggered? Workflows can be triggered automatically by changes in the system or manually by an operator. Manually triggered workflows are good for processes that remedy a problem the operator has noticed or for dealing with a forms-based requests (E.g. my PC won't boot). Automatically triggered workflows are useful because the operator does not even have to be aware of the workflow's existence to trigger it. In addition to triggers embedded in transactions there are also generic triggering mechanisms such as a change in the status of a business object or a change in the HR data. Irrespective of how the workflow is triggered, it is linked to the business object as described in the previous answer and can be tracked easily. Because WebFlow is part of the basis system, this triggering is reliable and easy to implement. Workflows may be triggered by events but this is not essential. The event-handling makes it easy to trigger workflows from transactions and system changes without you having to make modifications. If you are creating your own report or transaction which triggers a workflow, avoid events and trigger the workflow directly with the WAPI function call. This is particularly important when triggering a workflow from outside the SAP system. This method reduces flexibility (the workflow ID is hard-coded) but increases performance if this is an issue (we're talking about 50 000 work items a day here!). Any exception handling workflows that are intended to be triggered manually can be triggered from the system menu when viewing the relevant transaction. The SAP system has the intelligence to suggest workflows that can be triggered manually based on the authorization of the operator and the context that the operator is working in. No additional customizing is needed here. 14. What open interfaces are supported? The most significant interface supported is the Wf-XML standard from the Workflow Management Coalition. This is an independent organization of which SAP is a funding member, along with most other major workflow vendors. The Wf-XML interface is based on XML and allows workflows from different vendors to communicate with each other. A detailed description of the interface is available on the WfMCs web site at www.wfmc.org. 15. What is Wf-XML used for? 

Although a company is far better off workflow enabling their system with SAP WebFlow when SAP software is used anywhere within the process, a collaborative process can take place between partners using different software platforms employing different workflow systems. To support SAP customers in this situation, WebFlow offers the open interface Wf-XML. This allows Business Processes enabled using different tools to communicate and control each other. Any workflow tool offering this interface can connect up with other tools that also offer this interface. Wf-XML is the only open interface for supporting interoperability of business processes, independent of what the business process being integrated. 16. Where does Wf-XML come from? Wf-XML comes from the Workflow Management Coalition, an independent body of workflow vendors, customers and higher education establishments. 17. How does the workflow call procedures from non-SAP systems? The Actional control broker integrates directly into SAP WebFlow enabling proxy objects to be called directly from the workflow step. When called, the proxy method will make a call to the outside system either as a background task or as a dialogue step. These proxy objects are generated in the SAP system using a converter which converts the objects interface (DCOM, CORBA...) to the SAP syntax. A syntax converter also lets developers view any object in any of the participating systems in the developer's preferred language. 18. How can I get the workflow initiator information in my task? 1) From your triggering event to the workflow, bind the event creator element to the workflow initiator element. 2) Create a workflow container element based on USR01. 3) Add a step based on USR01.FINDUSERFROMAGENTSTRUCTURE to convert your initiator to a USR01 object. 4) Pass the USR01 object to each task you want to display the details. Mailing 19. What differences are there between a work item and a notification mail?a) The work item cannot be used to notify several users.Mails can be routed to several users, just like work items. When a mail is sent, and one recipient reads and deletes the mail, all other recipients will still have access to their own copy in their own inbox. However, when a work item is processed by one of the recipients it will automatically disappear from all the other inboxes. So you can see that a work item is unsuitable for notifying several users. It is also worth noting that a mail can be forwarded in many different ways (fax, internet...) whereas the work item cannot. b) The work item holds up the workflowWhen the workflow sends a mail (usually as a background step) it continues with the process immediately after transmitting the mail. When a work item is generated, the workflow will not continue until the work item has been processed. This slows down the process. Occasionally this is what is intended (using the work item as an approval step without the ability to reject) but usually you will better off using mails for notifications.Note: You can send business objects as references with the mail either as a business object reference attached to the mail or as an URL (ABAP required). What is the difference between sending a mail to a recipient list compared to sending individual mails via a dynamic loop?Performance. Sending 1 mail to 20 recipients will cost considerably less performance than sending 20 individual mails. If the mail is sent as a SAP Office mail (as opposed to e-mail, fax...) disk space will also be a factor because the SAP office mail will only exist once in the database, with references being created for each of the recipients. The only time you need to consider individual mails with a dynamic loop is when the text of the mail varies from one recipient to another. 20. How do I send a standard text as an e-mail from workflow?

It is very easy sending standard text , which may include data from the workflow. You simply create a background step which sends the work item description. This may include variables which will be substituted when mail is sent. In early releases you have to create your own task based on the method SELFITEM SendTaskDescription. In later releases a wizard is available for creating the step and in release 4.6 there is even a step type which does this all for you automatically. Whichever path you take, there is very good online documentation describing exactly what has to be done. 21. How do I send a complex text from the workflow?You may create mails using SAPscript. These mails can include conditions which are evaluated in order to determine which text blocks which are used in the mail. Workflow variables can be used in these conditions and workflow variables can be substituted into the body of the e-mail text. 22. How do I send really complex mails from the workflow?If you this is not enough for you will probably want to write your own ABAP routines for generating the text and generating the attachments to go with the text. Use the function group SO01 which contains functions of the form SO_*_API1 which are ideal for creating your own sophisticated messages. There are plenty of advantages of how these are used within the SAP system. 23. How do I send reports?There are wizards (Release 3.1) which will create workflows for you to send reports to a distribution list. You can specify whether the results should be transmitted or evaluated at the time the recipient wishes to view the report. It is usually better to send the evaluation because this allows the recipient to see the results instantaneously, without having to wait for the report to execute first. Deadlines 24. How can I configure the workflow so that different types of messages are sent out to different people depending on how late the processing is?Follow these steps: 1. Specify a deadline period for the step. 2. Specify a name for the event. This adds new branch from the step. 3. Add a new step to the branch which sends a mail message. 4. Add another step to the branch which sends out the second deadline warning (see mail steps above). Use deadlines in this step to configure an earliest start so that the second message is not sent until a further time has elapsed. 5. Repeat step 5 as often as you like. 25. How can I configure the workflow so that when the deadline is missed the workflow step is simply skipped?This is tricky to explain but easy to implement once you know how. Follow these steps (in later releases there is a wizard which takes you through the steps): 1. In the terminating events view of the workflow step activate the "obsolete" event and give it a name. 2. Specify a deadline period for the step. 3. Specify a name for the event. This adds new branch from the step. 4. Add a new step to the deadline path. This step must be of type "process control". 5. Select the control "Make step obsolete" and use the search help to specify the workflow step that has the deadline. Only steps with obsolete paths defined will be displayed (see step 1). 26. How do I trigger a workflow with an e-mail?

You can customize the system to call a BOR method when an external mail (fax, e-mail...) arrives in the system. You BOR method should either trigger the e-mail directly or trigger an event. To customize this user exit use the transaction SCOT. 27. How can I make sure that user's access their tasks via the workflow and not via the menu or launch pad?The routing mechanism for work items uses roles and organizational assignments to determine who receives which work item. However the routing does not provide extra authorization checks based on the routing configuration. If you want to ensure that the tasks are executed within the workflow, and not via the standard transaction, service or MiniApp, then you will have to apply your own protection. The simplest way of doing this is to remove the standard transaction from the user's menu or Workplace role (but include it in the supervisor's role, just in case). If you want to allow the user to execute the task from the menu if and only if they have received the work item then you should replace the standard transaction with your own custom built transaction. Your own transaction simply calls the standard transaction but performs it's own authorization check first, based on the routing mechanism used in the workflow. Tip: Add a second (ored) authorization check to make sure that a supervisor can execute the transaction in an emergency. 28. What is a workflow? What is a single-step task? A single-step task is based on an object type from the object business repository (BOR) (for example, a purchase order) and a method for the object (for example, change). A workflow can contain several single-step tasks and activities such as loops and forks. Through a workflow, you create a logical sequence for the single-step tasks. The tool for creating or changing these types of workflows (workflow template) is the Workflow Builder (transaction SWDD). 29. What is a work item (important terms)? A work item is the runtime object of a workflow or of a single-step task.You can execute dialog work items with the inbox (transaction SBWP). Each workflow and single-step task started is assigned a unique number known as the work item ID. 30. How is an event triggered from the application and a workflow then started? An event can be triggered from the application in three different ways: Directly:Within the application, the SWE_EVENT_CREATE function module or the SWE_EVENT_CREAT_IN_UPD_TASK function module, for example, generates an event in the update. With a change document:Change documents are written within the application when you change application objects in the update. You can link events that have the same key with these types of change documents via transaction SWEC. With status management:The SWE_EVENT_CREATE_STATUS function module triggers an event in the same way as the direct method when a status is changed. This event contains the object type (for example, purchase order), the object key (for example, purchase order 4711) and other information. Using transaction PFTC, you can assign the event to a specific workflow or single-step task. More settings are available in transaction SWE2. 31. How are the responsible agents determined? You can assign agents to a single-step task in transaction PFTC. For example, you can do this using organizational units, work center roles or positions. Within a workflow pattern, you can assign specific agents for this workflow to a single-step task. The overlap between both numbers of 'possible agents' represents the number of agents ('selected agents') who have the work item in the inbox later. 32. What is the difference of between an e-mail and a work item? E-mails and work items are two completely separate things. They just happen to be displayed in the same inbox. An e-mail is a message sent to one or several people. However, a work item is a runtime object of a single-step task or workflow. Consequently, a work item cannot be deleted from the inbox of a user. In this case in fact, you have to adjust the agent assignment or delete the work item as described in note 49545.

 33. PFAC no longer works for my role responsibility setup... Use tx: OOCU_RESP 34. How do I transport workflow definitions and agent assignments? When transporting workflows, you have to differentiate between the workflow definition and the agent assignment. A workflow definition is a workbench request. When you save the workflow, a workflow version is created and a request written. Further information about the transport or about the status management is provided in note 378487 and in the notes mentioned there under related notes.However, where the agent assignment is concerned, this is a Customizing request. To allow transport of agent assignments, the value of the semantic abbreviation CORR for the TRSP group name must be empty in table T77S0.35. How do you debug a background workflow process? In your method write the following code: data exit.Do.if exit = 'X'.exit.endif.enddo. Run the workflow, causing an infinite loop on that step, and then go to SM50.Here you can debug the process. 36.What is the Workflow basic Customizing? Before you can use the Workflow module, you must first execute the basic Customizing in transaction SWU3. All of the listed points should be green (the number range for customer tasks is no longer required). A detailed description of the activities is provided in the relevant information buttons. You can also execute some (but not all) of the points using the Automatic Customizing button. See the online documentation for an exact description of what happens there. The RFC destination must work correctly and the user (usually WF BATCH) should have the SAP_ALL profile. 37.: What options do I have as a user to configure the inbox individually? You have the following options: You can create separate user-dependent or user-independent layouts so that you can adapt the displayed columns individually. You can access the function in the Workplace via an application function key.You can set filters to set certain criteria for individual columns or several columns simultaneously, according to which specific work items are then filtered.You can add dynamic columns in the layout that then display dynamic elements for certain tasks and users from the work item container. However, this is only possible if all tasks in the inbox belong to just one task. If they have several tasks in the inbox, filtering serves no useful purpose because all tasks are first completely read once. You can define these dynamic columns using transaction SWL1.38. What does the substitute rule system look like in the workflow? You have a choice of two different substitute rulings: Active substitute ruling (for example, for absence due to vacations): In this case, the items belonging to the absent person are automatically assigned to the substitutes inbox (in addition to his own work items).Passive substitution (for example, for absence due to illness): the substitute must explicitly assume the substitution and can only view the items of the absent person in this mode.For other questions, you must also refer to note 74000. 39. How can users be automatically notified that new work items are available for processing? 

Unfortunately, the dialog box that informs users of new work items which appears in SAPoffice is not available within SAP Systems.However, the following two options are provided: In the Workflow Builder, you can designate the item as an express item via additional data. The user then receives a corresponding express dialog box.The RSWUWFML report (note 131795) is a more flexible option. This report sends an e-mail to an external Internet address to notify the user of new work items.40. Can I set deadlines for the latest processing of work items? this is where you can use deadline monitoring for work items. In the Workflow Builder, you can set dates for a requested/latest start/end date for each individual step. You must schedule the SWWDHEX job via transaction SWU3 for this. Schedule the job permanently in the production system otherwise it is difficult for the job to schedule individual deadline monitoring scenarios when workflow is heavy. 41. Can I also execute work items with external programs such as Outlook? You can use the Web GUI for HTML instead of the Windows GUI. However, note that some functions do no work in the WEB GUI, due to technical restrictions in the browser. You must refer to note 487649 on this subject.SAP also provides interfaces which allow you to process work items with external programs such as Lotus Notes or Microsoft Outlook. Refer to notes 77099, 98408 and 454845 for details. 

The Part I of Workflows Introduction gives the basic details about the workflow usage as a tool and the features involved. In Part II, the details about the workflow builder will be

covered. In the subsequent parts, more details about the runtime analysis tools of workflows will be discussed.What are SAP Business Workflows:

Using SAP Business workflows, one can define the business processes that are not yet mapped into SAP system. Workflows are suitable for the situations where the given task is

executed repeatedly or when the large number of people is involved in the completion of that work. Workflows can be used in conjunction with the existing business scenarios e.g.

during the standard functionality errors or exceptions occurs then workflow can be triggered on these actions.

There are lots of standard workflows available from SAP for different areas like Sales & Distribution (SD), Travel Management (TV), Treasury (TR), General Logistics (LO), and

Personnel Management (PA) etc.Why Workflows:

Following are the scenarios, which occur on daily basis in each organization -

Finding out what work needs to be done

Planning of work that needs to be done amongst the group of people

The identification of roles & responsibilities on who will do what, when & in how much time

Working in coordination with others

Informing next person about his work to be done, when the earlier one has finished his own

Duplication of work that has been already done because of communication gap,inefficient knowledge transfer & the incomplete documentation in the central repository

Identification of delay in the completion of the work

Preparing status on this delay

Workflows help to optimize each of the above scenarios. In workflows the processes are linked to each other and flow one after the other. At each step, a right person (Agent) will take

care of the process. If the step doesn’t need any interaction then the process flows automatically.

Here deadlines can be set for the activities depending on the fair time that step needs to complete. Once this deadline is reached and the process is not performed by the concern then

the administrator (manager) gets the notification mail. Here as the right people can be kept in loop in this automated process so a disciplined work atmosphere is automatically

planned in the organization.

Due to this automated system, the process becomes transparent to all the users and the risk of manual errors is also reduced. Again the time required to complete any work manually

is simply reduced in this automated system. So this adds to the quicker completion of targets and hence leads to the financial growth of the organization.

Features of Workflows:

New business processes can be easily defined with the workflows.

Workflow uses the existing transactions and functions without changing them.

Workflow uses the Organization structure. This helps in the term of changes to organization structure, which will be immediately in effect in the execution of workflows.

Lots of tools are available in the workflow like tools for definition, analysis and monitoring of work processes.

Workflow template (transaction: PFTC) can also be created for the workflow definitions.

Workflow Builder is a very effective tool available for creation, change and display of workflow definition.

Agents can be easily maintained in the workflows. They receive the work item in their SAP Business Workplace, which they will process.

Deadline monitoring can be easily used against the tasks for the defined agents.

Using Business Object Editor (transaction: SWO1), we use the business objects in workflows. These business objects help to use the SAP standard functionality in

workflows.

ABAP Classes can also be used in workflows along with the business objects.

Business Workflow explorer gives the overview of all the tasks.

Workflow can also be used on Internet. This is especially useful for the managers, who might not be directly accessing the SAP transactions. So the approval forms

generated via workflows can be sent on internet. This is even useful for the people who mainly preparing SAP data and not knowing much about the SAP transactions. They can be

given a simple web form for entering data & on submitting data of this web form workflow can be started.

Several workflow wizards are also available for supporting the workflow definition

Version management is available for workflows. Only one version can be active at one time, which is referred while execution.

Lots of administrative tools are available for control and analysis of workflows.

Lots of diagnostic tools are also available in workflows.

Prerequisites of using Workflows:

System Requirement: R/3 Release 3.0 & above

Mail servers involved should be SMTP Compliant if the workflow involves email notifications.

As the workflow may execute lots of background jobs so it may require lots of system resources. Hence the hardware should be enough to fulfill all these requirements

along with the normal functionality of the server without affecting the speed.

Customization Settings:

o Following are the customizing settings needed to use workflows-

With the System Supervisor ID, go to transaction SWU3(Automatic Workflow Customizing)

Click on the button Perform Automatic Workflow Customizing (F9) from the application toolbar for performing automatic customization of

the workflow.

Once this is done, all the check marks below should turn green

Along with so many settings available in the workflow customizing, system automatically creates a batch user WF-BATCH. This user has SAP-

ALL authorizations to execute the workflow.

Now, go to table T78NR from Customizing SPRO transaction.

Click on Create button from the application toolbar to create a new prefix range.

Give the Prefix Number as 900 for custom development & click on Save button.

The newly created prefix appears as activated in the table.

o The user triggering the workflow should have his email ID maintained in the SU01 transaction.

oo SMTP Configuration:

From SAP WAS 6.10, SAP directly supports SMTP (Simple Mail Transfer Protocol). This means that the emails can be exchanged directly between SAP system and any SMTP compliant

mail server. From SAP WAS 6.20, faxes, pager & SMS can also be exchanged via SMTP.

Goto transaction SCOT.

Goto menu View -> Node

Goto SMTP node. Double click on the required node which is * in this case.

Click on the Maintain Node button.

Give the Mail Host & Mail Port for outgoing mails. Click on Set for Internet options to set.

Give the Address Area as * for the receipt addresses. Also set the Output formats for the SAP Documents as shown in the image below. In the

specified format the output will be sent as attachment in the email.

Confirm the settings.

Similarly Pager/Fax settings can be done. For Pager(SMS), the prerequisite is that in transaction SA14, the paging services should be defined.

Once this is done, the here in the SCOT transaction, click onSet adjacent to Pager (SMS).

Mention as * in the Address area for the receipt number and Domain name in the Domain input.

Confirm the entries. The SMS will be of the format SMS=+ReciptNumber@Domain

Transactions Involved:

Lots of transactions are involved in the Workflow tool. Majority of them are for runtime analysis and diagnosis. The details of these transactions can be found from SAP Easy Access

menu.

Following are the frequently used transactions -

Customization Settings:

o SWU3 - Automatic Customizing Workflow.

o SCOT - SAP to mail server Configuration

o SU01 - User Maintenance

Workflow Design:

o SE37 - Function Builder

o SE38 - ABAP Editor

o SWO1 - Business Object Builder

o PFTC - Task Maintain

o SWDD - Workflow Builder

Runtime Behavior/Analysis:

o SBWP - Business Workplace

o SWUD - Workflow Diagnosis

o SWU_OBUF - Synchronize Runtime Buffer

o SWPR - Workflow Restart After Error

Workflow Terminologies:

Workflow builder: Workflow builder is the business workflow tool for creating, editing and displaying the workflow definition.

The Workflow Builder provides a graphical modeling view, which gives a direct overview of the processes of the different steps. Also there is a tree view to shows all steps of the

workflow definition in a hierarchical view.

Workflow Container: The workflow container contains workflow-specific system elements as well as other container elements, which are defined explicitly.

Container elements for which the import or export indicator is set form the interface of the workflow. This interface is valid for all versions of the workflow definition. Container

elements for which no import or export indicators are set are local container elements of the workflow definition and are valid only in the versions of the workflow definition in which

they were defined.

Workitem: Workitem is runtime representation of a task or a step in the workflow definition. There are various types of work item.

The SAP System determines the recipient(s) of a work item i.e. Actual Agent from the intersection of responsible and possible agents. If this intersection is empty then no body will get

this workitem for further processing.

Dialog Workitem: A work item (type W) which at runtime represents a workflow step or a task that requires dialog with the user. Typically, dialog work items are

displayed in the Business Workplace. When a dialog work item that is based on a task is executed, the underlying object method is called. You can monitor deadlines for dialog work

item execution.

Triggering Event: Triggering event is the one, whose occurrence triggers or starts the workflows or tasks.

The event must be entered as a triggering event for the task or workflow that is to be started. The event linkage must be activated. The event must be defined as an object type

component in the Business Object Builder. A task or workflow can have several triggering events. Information from the event creation context can be passed in the binding from the

event container to the task container or workflow container.

Block: Block is an element of workflow definition. It contains the consistently arranged steps and operators. It has one start and one end. The consistency and robustness

of a workflow definition is ensured because a block is always created when a new step is created, or an undefined step is changed. Similarly, when individual steps are deleted, cut, or

inserted, the entire block in which the step is located is affected.

Step: A step is an entity, which can be inserted into the workflow builder. Whenever executed, step gives the predefined desired results.

The step is always defined in block. There are different types of steps available in workflow builder to perform different kinds of operations. These steps are Activity, Web Activity,

Send Mail, Form, User Decision, Document from Template, Condition, Multiple Condition, Event Creator, Wait, Container Operation, Process Control, Loop(Until), Fork, Undefined, Ad

hoc Anchor, Local Workflow & Block.

Task: Task (Standard Task, Customer Task) is used to define the Activity step in workflow definition. Task can be executed independently also.

Task Container: Task container is a location for storing data from the task environment. The task container contains the information about the object reference to the

object to be processed, the actual agent of workitem, necessary input parameters for the method. These parameters come from workflow container after the binding between

workflow container and task container. It also stores the information available after the method processing.

The task container contains some predefined workflow system elements. One can define more container elements in the task container. It is also known as a work item container at

runtime.

Responsible Agent: Responsible Agent is a user assigned to a step in the step definition. Expressions, organizational objects, or rules can also be used to assign the

responsible agents.

Possible Agent: Possible agent is a user who is authorized organizationally to start a task and execute the relevant work item.

Actual Agent: Actual Agent is the person who receives a work item for further processing. The agent can be directly assigned to step or agent determination can happen

dynamically at run time either from rule or from the organization structure.

Workflow Binding Concept:

There is three level of two way Binding concept involved in workflows. Here binding is meant by the interaction between two consecutive levels using variables (Import/Export

parameters). The first level of binding exists between the event triggering the workflow and the workflow’s container i.e. workflow gets the necessary inputs for processing.

The second level of binding exists between this workflow container and the step (task) container. And the third level of binding exists between the step (task) container and the

method inside this step (task).

Here the values in the variables are passed to workflows, which then flows to tasks & finally to corresponding methods as Import parameters. The outcome of these methods if needed

can be passed back to task & then finally to workflow. The outcome of one task can also be passed to next tasks using this binding concept.Workflow Builder in Brief:

Transaction for workflow builder is SWDD.

The workflow builder is divided into different areas like Information Area, Navigation Area, Step Types, Graphical Model, Results of Syntax check etc as shown below.

In the Information Area, the information about the workflows like workflow number, version and the status of the workflow are displayed.

In the navigation area, all the steps of workflow definition are displayed in sequence.

The Step Types appear in the Objects section of the workflow builder. This object section consists of following options in the dropdown, one which can be viewed in the

workflow builder. e.g. in the current case, Step Types are displayed.

o Step Types That Can Be Inserted

o Workflow Container

o My Workflows and Tasks

o Document Templates

o Workflow Wizards

o Teamworking

o Workflows of this Definition (Outcome)

o Note It!

At the bottom of the workflow builder, the syntax check results are shown as either informatory, warning or error messages.

In the Graphical view, the actual definition of workflow is build by dragging the steps from the steps list or by right clicking the step directly on undefined one. The

default steps in every workflow are Workflow Started, Undefined step and Workflow Completed.

Triggering Event for this workflow can entered in the workflow builder by menu Goto -> Basic Data. Here enter the relevant business object and the event name. Activate

the link and binding.

Once the workflow is built here. It needs to be activated so that it can be used further.

Workflows can be locally tested at the Builder level also.

Following types of steps can be inserted into the workflow builder.Symbol Step Name Function

Activity Activity is used to execute the methods of Business Objects. At runtime it does the execution of a task or sub workflow

Web activity

The content of container elements is sent to a URL unchanged or in the form of a generated XML document. The step can wait for a reply.

Communication with a process started by a Web activity is possible. A process started by an XML message can communicate with its caller.

Send mail This is used to send mails to SAP, Internet mail addresses. The text entered in this step type is sent as an e-mail.

Form The data in a container element that refers to a structure can be displayed, processed, or approved as a form.

User decision

The actual agent will be given choices to execute the workitem with different decisions. The process flow of the current workflow is controlled

on the basis of a decision made by the current agent.

Document from

template A document is created from a document template.

Condition

One of two branches defined in the workflow definition is processed. The system makes the decision based on defined conditions. When doing

this, this system takes account of information from the context of the workflow or the application objects processed.

Multiple

condition

One of several branches defined in the workflow definition is processed. To do this, the system checks the value of a container element in the

workflow container.

Event creator An event is created.

Wait for event

The system waits for a specific event. The work item is only completed if the expected event occurs. The event can also be triggered by the

occurrence of an XML document.

Container

operation

Elementary arithmetic operations or value assignments are applied to individual elements of the workflow container. E.g. Setting up flag values

for processing can be done here.

Process control The functions Cancel work item or Set work item to obsolete are applied to other work items of the current workflow.

Loop (UNTIL) A sequence of steps is processed repeatedly until the defined termination condition occurs.

Loop (WHILE)

A sequence of steps is processed repeatedly as long as the defined comparisons apply. The system leaves the loop when the basis of

comparison does not agree with any of the comparison values.

Fork

The processing that follows takes place in a fork. One can define how many branches have to be executed for the fork to be successfully

completed, or can define an end condition in the condition editor.

Undefined step No function at runtime. Undefined steps always have an outcome.

Ad hoc anchor

In the definition, one can save workflows that can replace this step. At runtime, an authorized user can select one of the saved workflows. The

ad-hoc anchor is then replaced by the steps of this workflow.

Block Steps can be grouped together in workflow block.

Local Workflow

Local workflow in the caller workflow has the local container and has full access to the workflow container as well. The local workflow gets

triggered by local events in the caller workflow.

How Workflow can be Started/Triggered:

Workflow can be triggered in following different ways –

Automatically By Triggering Events: Workflows can be triggered using events. Whenever this event occurs, workflow automatically gets triggered. For this, the event

must be specified as the Triggering Event.

Automatically By using Workflow: Workflow can be triggered if it is specified as the step of another workflow.

Manually:

o Workflows can be triggered manually in the standard environment where the necessary input data is given to workflow with triggering event.

o Also workflows can be triggered in testing environment i.e. in development environment for testing purpose.

o Workflow can be stared using Start Transaction. Start Transaction is the one whose execution allows all the import parameters of a workflow to be

entered. After the start transaction has been executed, the SAP System starts the associated workflow with this data.

o A user can start a workflow or task from a message issued by the system. A workflow or task must be assigned to the message. An appropriate function for

this is available to the user in the message long text.

The Part I of Workflows Introduction gives the basic details about the workflow usage as a tool and the features involved. In Part II, the details about the workflow builder will be explained. In the part III, more details about Workflow Builder will be covered. In subsequent parts Business Object Builder & details about the runtime analysis tools of workflows will be discussed.What are SAP Business Workflows:Using SAP Business workflows, one can define the business processes that are not yet mapped into SAP system. Workflows are suitable for the situations where the given task is executed repeatedly or when the large number of people is involved in the completion of that work. Workflows can be used in conjunction with the existing business scenarios e.g. during the standard functionality errors or exceptions occurs then workflow can be triggered on these actions.There are lots of standard workflows available from SAP for different areas like Sales & Distribution (SD), Travel Management (TV), Treasury (TR), General Logistics (LO), and Personnel Management (PA) etc.What is Workflow Builder:Workflow builder is the business workflow tool for creating, editing and displaying the workflow definition.The Workflow Builder provides a graphical modeling view, which gives a direct overview of the processes of the different steps. Also there is a tree view to shows all steps of the workflow definition in a hierarchical view. For graphical modeling view, the prerequisite is to have SAPGUI for Windows.Transaction for Workflow Builder:SWDDMenu path for Workflow Builder:SAP Menu -> Tools -> Business Workflow -> Development -> Definition Tools -> Workflow Builder -> Workflow BuilderFeatures of Workflow Builder:

Version management for workflows is featured. (Menu Workflow -> Generate Version).

Import/Export feature is available for workflows with some restrictions. This import/export happens through the XML version of workflows. (Menu Workflow -> Import/Export..).

Option of printing is available for the workflows. This option is for graphical display as well as for individual step details, which are selectable for printing. (Menu Workflow -> Print..).

Testing of workflows within builder is possible. (Menu Workflow -> Test). Block operations like Cut/Copy/Paste are available. (Menu Edit -> Block..).

Insertion an existing workflow/subworkflow into the current workflow is possible by selecting the appropriate node in the graphical display. This is same as creating steps according to the rules of block orientation. (Menu Edit -> Insert Workflow).

Triggering Event for workflow can be entered in the workflow builder by menu Goto -> Basic Data.

Here enter the relevant business object and the event name in the Start Events tab. Activate the link and binding.

Many times it so happens that changes are made but they don’t reflect in workflow results due to buffer synchronization. One can synchronize the runtime buffer from workflow builder directly. This synchronization happens for Tasks (single-step tasks, multistep tasks), Organizational environment (assignment of tasks), Workflow System Settings (RFC Destination, and so on).

From the menu Extras->Transport->Synchronize runtime buffer, one can goto transaction SWU_OBUF of buffer synchronization.

Clicking on Start Synchronization will refresh the buffer. There are different options available in workflow builder for Views/Default Settings/Hidden Step Types from

the Menu Extras -> Options. Here depending on the values selected in View tab, the modeling view of workflow changes as follows –

o L – Event Driven Process Chains: Goto menu Extras -> Options -> tab View. Select the value from the Display of Modeling View – View dropdown as L Event Driven

Process Chains (EPCs).

Click on Enter. The graphical modeling view changes to as follows where All triggering events, outcomes,

steps and operators are displayed. Steps are displayed as green rectangles, triggering events and outcomes as red

hexagons and operators as circles. The step name is displayed in the graphical symbols.

o C- Classic Event Driven Process Chains (ClassicEPCs): Goto menu Extras -> Options -> View tab. Select the value from the Display of Modeling View – View dropdown as C- Classic Event

Driven Process Chains (ClassicEPCs).

Click on Enter. All triggering events, outcomes, steps and operators are displayed. Steps are displayed as

green rectangles, triggering events and outcomes as red hexagons and operators as circles. The node number and the

node type are displayed with the step name in the graphical symbols. The step type area is not displayed.

o N – Without Event-Driven Process Chains (NoEPCs): (Default Mode of View): Goto menu Extras -> Options -> View tab. Select the value from the Display of Modeling View – View dropdown as N –

Without Event-Driven Process Chains (NoEPCs).

Click on Enter.

All steps, triggering events and the workflow start and end are displayed using symbols. Outcomes are displayed in text on the connecting lines.

There are lots of other display settings available in menu Extras->Options for Block Display, Tips & Tricks display at start, display of percentage progress of a syntax check, indicator for steps Drag & Drop by mouse etc.

In the menu Extras->Options->Default Settings tab, there is an option for workflow definition modeling as Use Top-Down Modeling.

If used this option, then one can model the workflow without actually defining the steps. So when a step is added to workflow, it is only added to graphics.

This way one can have the actual picture of the final definition of workflow. To use such type of workflows, all the inserted steps should be complete.

Other settings like hiding steps types etc are also available in menu Extras->Options. One can go to SAP Business Workplace directly from workflow builder from the menu Environment->Business

Workplace. There are lots of workflows available as examples, which can be reached via workflow builder. The menu path

isEnvironment->Start Workflow.

Select the required workflow from the list on the left side and click on either Start or Start with Details on the right side for execution. Once the workflow is started, the log can be viewed from the Workflow Outbox button from the application

toolbar.

One can directly go to the different development environment like ABAP Dictionary, Class builder, Business Object Builder, Correlation objects, proxy objects, Web Services etc. from workflow builder. The menu path isEnvironment->Development..

Workflow Builder Details: Go to transaction SWDD for workflow builder. By default, the builder shows the last workflow worked in the builder. To go to the required workflow, click

on Other Workflow/Version..(Ctrl+F5) from the application toolbar.

In the Task, give the name of the required workflow, following the F4 search help if needed.

The required workflow is now displayed in the workflow builder. The workflow builder is divided into different areas like Information Area, Navigation Area, Step Types, Graphical Model, Results of Syntax check etc as shown below.

In the Information Area, the information about the workflows like workflow number, version and the status of the workflow are displayed.

In the navigation area, all the steps of workflow definition are displayed in sequence.

The Step Types appear in the Objects section of the workflow builder. This object section consists of following options in the dropdown, one which can be viewed in the workflow builder. e.g. in the current case, Step Types are displayed.

o Step Types That Can Be Inserted are Activity, web activity, Send Mail, Form, User Decision, Document from Template, Condition, Multiple Condition, Event Creator, Wait, Container Operation, Process Control, Loop(Until), Fork, Block, Local Workflow etc.

o Workflow Container

o My Workflows and Tasks

o Document Templates

o Workflow Wizards

o Teamworking

o Workflows of this Definition (Outcome)

o Note It!

At the bottom of the workflow builder, the syntax check results are shown as either informatory, warning or error messages.

In the Graphical view, the actual definition of workflow is build by dragging the steps from the steps list or by right clicking the step directly on undefined one. The default steps in every workflow are Workflow Started, Undefined step and Workflow Completed

  -------------------------------------------

   More stuff on WORKFLOW Transactions AWUV Wizard for event creation Definition tools -> Event creation -> Set up with wizard MCA1 Workflow Information System Reporting -> Workflow Information System (WIS) OOAW Evaluation paths PFAC Maintain standard roles PFAC_CHG Change roles Definition tools -> Standard roles -> Change PFAC_DEL Delete roles Definition tools -> Standard roles -> Delete PFAC_DIS Display roles Definition tools -> Standard roles -> Display PFAC_INS Create roles Definition tools -> Standard roles -> Create PFOM Maintain assignment to SAP organizational objects Definition tools -> SAP org. objects -> Create assignments PFOS Display assignment to SAP organizational objects Definition tools -> SAP org. objects -> Display assignments PFSO Organizational environment of a user PFT Maintain customer task PFTC General task maintenance PFTC_CHG Change tasks Definition tools -> Task/Task groups -> Change PFTC_COP Copy tasks Definition tools -> Task/Task groups -> Copy PFTC_DEL Delete tasks Definition tools -> Task/Task groups -> Delete PFTC_DIS Display tasks Definition tools -> Task/Task groups -> Display PFTC_INS Create tasks Definition tools -> Task/Task groups -> Create 

PFTR Standard task for transaction PFTS Standard task PFWF Maintain workflow task (customer) PFWS Maintain workflow template PPOC Create organizational plan Definition tools -> Organizational plan -> Create PPOM Maintain organizational plan Definition tools -> Organizational plan -> Change PPOS Display organizational plan Definition tools -> Organizational plan -> Display SWDA Ongoing Settings Administration -> Settings SWDC Workflow editor administration data SWDM Business Workflow Explorer Definition tools -> Business Workflow Explorer SWE2 Display and maintain event type linkage Utilities -> Events -> Type linkages SWE3 Display instance linkages Utilities -> Events -> Instance linkages SWE4 Switch event log on/off Utilities -> Events -> Event/log -> On/Off SWEC Link change documents to events Definition tools -> Event creation -> Change documents -> Linkage SWED Assignment of change document objects to object types Definition tools -> Event creation -> Change documents -> Define workflow properties SWEL Display event log Utilities -> Events -> Event log -> Display SWF3 Workflow Wizard Explorer Definition tools -> Wizards -> Workflow Wizard Explorer SWF4 Workflow Wizard Repository Definition tools -> Wizards -> Workflow Wizard Repository SWI1 Selection report for workflows Utilities -> Work item selection SWI2 Work item analysis Reporting -> Work item analysis SWI3 Workflow outbox Runtime tools -> Workflow outbox SWI4 Task analysis Reporting -> Task analysis SWI5 Workload analysis Reporting -> Workload analysis SWI6 Object links Runtime tools -> Object links SWI7 Workflow resubmission folder From Integrated Inbox or Workflow Outbox SWI8 Error overview Part of administration of workflow runtime system (transaction SWUF) SWL1 Settings for dynamic columns Customizing, part of ongoing settings SWLC Check tasks for agents Utilities -> Consistency check -> Organizational assignment SWLD Workbench for Workflow 4.0 SWLP Copy plan version 

SWLV Maintain work item views Customizing, part of ongoing settingS SWLW Workbench for Workflow 3.0 SW01 Business Object Builder Definition tools -> Business Object Builder SW06 Customizing object types From Business Object Builder, choose Settings -> Delegate -> System-wide SWU0 Event simulation Utilities -> Events -> Simulate event SWU2 RFC monitor Utilities -> Workflow RFC monitor SWU3 Customizing consistency check Utilities -> Customizing SWU4 Consistency check for standard tasks Utilities -> Consistency check -> Task -> Standard task SWU5 Consistency check for customer tasks Utilities -> Consistency check -> Task -> Customer task SWU6 Consistency check for workflow tasks Utilities -> Consistency check -> Task -> Workflow task SWU7 Consistency check for workflow templates Utilities -> Consistency check -> Task -> Workflow template SWU8 Switch technical trace on/off Utilities -> Technical trace -> On/off SWU9 Display technical trace Utilities -> Technical trace -> Display SWUD Diagnostic tools Utilities -> Diagnosis SWUE Trigger event Utilities -> Events -> Generate event SWUF Runtime system administration Administration -> Runtime system SWUG Workflow start transactions Definition tools -> Workflow start transactions SWUI Start workflows From the R/3 initial screen, choose Office -> Start Workflow SWUS Start tasks Runtime tools -> Start workflow SWUY Wizard for message linkage to workflow Definition tools -> Wizards -> Create "Call workflow from message" SWX1 Create notification of absence SWX2 Change notification of absence SWX3 Display notification of absence SWX4 Approve notification of absence SWXF Form applications: Access point Environment -> Demo examples -> Fill out form Reports RSWWWIDE – Delete work items RHSOBJCH to fix PD Control Tables Tables SWW_OUTBOX - Lists Workflows in outbox together with status SWW_CONT - Container Contents for Work Item Data Container

 SWW_CONTOB- Container Cont. for Work Item Data Container (Only Objects) SWWLOGHIST- History of a work item SWWORGTASK- Assignment of WIs to Org.Units and Tasks SWWUSERWI - Current Work Items Assigned to a User SWWWIHEAD - Header Table for all Work Item Types