Professional Documents
Culture Documents
With SAP Business Workflow, SAP AG provides an efficient cross-application tool enabling integrated electronic management of business processes. SAP Business Workflow is a solution which has been integrated full in the !"# S stem and which enables customer-specific business process flows to be coordinated and controlled on a crossapplication and cross-work center basis. SAP Business Workflow therefore enhances $read -made$ application software. %he SAP Business Workflow definition environment can represent business processes simpl and can respond to changing e&ternal conditions 'uickl , even in a live s stem, b adapting the e&isting business processes. %he definition and e&ecution of a workflow can be divided into four main areas. A user e&ecutes workflows in their Business Workplace where the work items that the can e&ecute are displa ed. A workflow must be defined to be e&ecuted. %o this end, a workflow definition is created in the Workflow Builder. %his definition contains steps that are e&ecuted at runtime. %he step either control the workflow directl or the contain a reference to a task. %he task refers to a method of an ob(ect t pe in the Business Object Repository )B*!+ and can be e&ecuted at runtime either automatically )background task+ or b a user )dialog task+.
Tasks
%asks describe elementar business activities. %asks alwa s refer to a method of an ob(ect t pe. Possible agents are defined for tasks. %asks can refer to automaticall e&ecutable methods )background tasks+ or the can need a user to e&ecute them )dialog tasks+.
Process (low
An emplo ee enters a notification of absence )leave re'uest+ in the !"# S stem b filling out the relevant input template. %he direct superior of t*e employee is responsible for approving or re(ecting the notification of absence. %he !"# S stem determines the direct superior automatically on the basis of the organi0ational plan maintained. .f the re+uest is appro,ed the creator is notified b mail1 .f the re+uest is not appro,ed, the creator is informed and can decide whether to withdraw the notification of absence or revise it. .f the superior has given reasons for the re(ection in an attachment, the creator can take these into consideration.
.f the creator re,ises the re'uest, it is submitted to the superior for approval again. %he applicant can also add an attachment, which can then be accessed b the superior. %his c cle is repeated until either the superior approves the leave re'uest or the creator withdraws it. %he applicant can find out the current processing status at an time b looking in their workflow outbox.
%he tutorial is not intended to provide a full description of all functions and concepts. %his information is available in the documentation on SAP Business Workflow. %his tutorial does not deal with the definition of ob(ect t pes. .f ou want further information on this sub(ect, please work through the tutorial on Workflow Programming.
Process (low
Work through the individual units in this tutorial in the specified order. .mportant units are followed b tests that ou can use to test what ou have learned to date. Please make sure to complete these tests.
Result
E ample & t*e notification of absence
%he scenario in this e&le begins with the completion of a leave re'uest b an emplo ee )re'uester or creator of the notification of absence+. %he completed form is then forwarded automaticall to the head of department )emplo ee4s superior+. .f the head of department approves the re'uest, the emplo ee receives a notification and the workflow is terminated. .f the head of department re(ects the re'uest, the emplo ee can decide to revise the re'uest )possibl in accordance with the head of department4s wishes+ or withdraw it. .f the emplo ee decides to revise it, the re'uest form is resubmitted to the head of department after the revision is made.
%he diagram above shows that additional steps could follow the approval, such as updating the leave account, or notif ing the secretar . %hese steps, however, do not arise in this e&le.
Step&by&Step
!un %ransaction PP*@/ >. -ind our Aompan )A><9 will be used in this e&le+. -ind the Sales and @arketing *rgani0ational 3nit. We will assign SAP 3sers to the BP of Sales and @arketing and to Sales !ep Aentral positions. ;. !ight Alick on the BP of Sales and @arketing, and select Assign, from the menu. #. Select Colder-3ser from the menu. -ind and select our 3ser Account. 6. !epeat steps ; and # for the Sale !ep Aentral position )assign the same user so ou can receive all messages in this workflow e&ercise+. =. ,our screen will look like this1
!un transaction SW22 )Workflow Builder+ >. 2rag and drop the activit .con in the Step % pe are to the 3ndefined step in the Graphical @odel ;. .n the Aontrol tab, click the %ask field, click and arrow to Areate a 8ew %ask. #. %he Standard %ask window will appear. % pe the information as shown in the screen below )e&cept use our own numbers in place of ><9+
6. -rom the Additional 2ata menu, select Agent Assignment @aintain and assign the Sales !ep ><9 )central+ position )as shown below+
=. Save the data. .n the Areate *b(ect 2irector /ntr , click on the Docal *b(ect button. 7. Go back to the Workflow Builder and click on the Binding )does not e&ist+ button. %hen define the following binding1
?. Save our workflow. Give it a name like WS5.5><9 and make sure it is a local ob(ect. <. Det4s create another Activit and another task for the @anagerial step )approves or re(ects the re'uest+, as shown below1
>9. Save it )select local ob(ect as in the previous task+. >. ,ou need an additional container element in the workflow container to store the name of the user who will e&ecute this step. %his user name is to be used later in the notification te&t that is sent to the re'uester. Ahoose the Workflow Aontainer )left side+ and then select the entr E "ouble#click to create$ b double-clicking in the Workflow %ontainer. %he dialog bo& for entering a container element is displa ed. @ake the following entries and save1