SAP Workflow Customization Settings
Embed Size (px)
Transcript of SAP Workflow Customization Settings
Developing a simple application using steps "User Decision" and "Mail"The workflow definition is the set of rules that determine the path that the process takes. For example, how a purchase requisition is processed, from the initial request to the creation of the purchase order A Workflow Instance, which is often simply referred to as the workflow, is a single workflow run. For example, the processing of a single purchase requisition for computers. The Tasks are the steps in the process, which have to be performed either by people or automatically by the software. For example, to check for the availability of the spare computers in the company. A Work item is the task instance that is performed as a single workflow step. For example, check that there are no spare computers available in the company. Agents are the people who process the tasks (via the work items). For example, requisitioner and a member of the purchasing department. Container is the place where all the data used in the workflow is collected. Binding is the set of rules that define which data is passed to which part of the process.
Building a simple workflow applicationThe central tool for creating, displaying and processing a workflow is the workflow builder (Transaction SWDD). Within the workflow builder you can create all components of a workflow, including all the containers you need for getting the data from one step to another. Generally, most of the workflows are started by an event (for example, when a material is created or when a new purchase requisition arrives). You define which data from this event needs to be passed to the workflow via binding. However you can also start any workflow directly. Let us create a simple workflow and start the workflow directly, using the testing tools. Call transaction SWDD. When the workflow builder is called for the first time, a newly created initial workflow definition appears or else last created workflow appears. In such cases you can opt to create a
new workflow by pressing Create New Workflow(ctrl + shft + F5). The following screen appears.
The initial workflow screen has the following parts:
a. The start of the workflow definition, indicated by b. The end of the workflow definition, indicated by
c. The area in which you insert the new workflow definition is indicated by
Now select the undefined step and select Create step or double click the undefined step. Now among the different steps chose the User Decision by double clicking on it.
Now enter the title for the user decision Please make a decision. Also enter the decision texts as Approve and Reject. On pressing enter, the outcome values default to the Decision texts but you can specify your own names, if desired. Now we need to select the agent. Agent is the person to whom the work item needs to be sent.. Since this is just a beginning, we would hardcode the user name. Select the User from the drop down list and enter the user name to whom the work item needs to be sent. In general, this type of agent assignment is not done. Agents are generally assigned using the expression, agent assignment rule or organization object (job, position etc.).
Transfer and to graphic button. Following screen appears:
Now we need to include a mail step to be sent to the requestor. Now select the line Approve and do a right click. Different options on shown on the context menu. Select Create.
Now select the step Send Mail from the list.
Now enter the subject and the body of the message for the mail to be sent.
Do not change the recipients. Our mail is intended for the persons who triggered this workflow. &_WF_INITIATOR& contains the value who executed the workflow. Since this is a test object, we are using &_WF_INITIATOR&. But we wouldnt be using this variable in real time scenarios. We would discuss about this in the coming documents. Now select Transfer and to graphic button.
A popup appears requesting for the abbreviation and the name for this task. Enter the same and press enter.
Now enter the package as local object and press enter. Follow the steps 5 through 9 for the step Reject. The following screen appears:
Press SAVE to save the workflow application. You need to enter an abbreviation and name for your workflow as shown below. You can change any of these at any later point. After saving, a number is assigned to your workflow starting with WS, as shown below.
To execute the workflow, activate it by choosing the activate button. Test the workflow by choosing Test. The following screen appears.
Execute to start the workflow.
Now the recipient would receive a work item in his SAP inbox (Transaction SBWP).
Now execute the work item by pressing Execute. The following screen appears:
Choose one among Approve or Reject as part of the user decision. He can select the third option to retain the work item in his inbox and make the decision later. Now suppose that the recipient has chosen one of the first options. Now a mail would be sent to the requestor with the status of his request.
Including custom text in the step "User Decision"Whenever we create a step User Decision (For creation of User Decision step, click here) and provide with our own options like approve or reject, the work item would appear as follows:
As marked in green in the above screenshot, the description available in the work item is a default one provided by SAP. In case we need to add our own text, do the following: 1. Identify the task being used in the step User Decision. In the step User Decision, click on the tab Control:
In the tab Control, the standard task that is being used is displayed. In this case, the standard task that is being used is TS00008267.
2. Go to transaction PFTC_COP to copy the standard task. Select Standard task in the task type and enter the task number (without the prefix TS) in the Task.
Click on Copy task. 3. Enter the abbreviation and the name as required.
Click on Copy Task. 4. Enter the package name as required. 5. A new task would be created. Please note the task number that is created now. 6. To change the task description, you can use the transaction PFTC. 7. Now go back to workflow definition, transaction SWDD. 8. Click on User decision and then click on the tab Control. 9. Here replace the standard task number with the custom task created above. 10. Do the agent assignment and generate the same. It is always advisable not to change any of the standard texts. The change would reflect in all the workflow definitions the task is being used.
Creating a Container elementThis document details about creation of a container element in workflow and using it in the step "Mail". Pre-requisites: It is assumed that the reader of this Tutorial is aware of creating a workflow definition with the step Mail. If not, please go through the document on creating the same available, by clicking here. Steps: 1. Create a workflow definition using the transaction SWDD.
2. Lets create a container element for Carrier id. Click on the Workflow Container on the left side of the screen (as shown in the screenshot below):
3. Now double-click on Double-Click to Create
4. Enter the details pertaining to CARRID here.
5. Click on tab Properties and select Import.
6. Click on Confirm (Enter). 7. Now the element created could be seen on the left side, below the Workflow Container.
1. Create a Mail step by double-clicking on Undefined step in the workflow.
2. Enter the recipient details in the Recipients box. 3. In the subject line, enter Carrid value entered is: and click on Insert Expression.
Select the element Carrid from the list.
5. Similarly enter the content in the Body area.
6. Save and activate the application. Testing the Workflow application: 7. Test the workflow by clicking F8.
8. Enter the value of the Carrid as shown above and press execute. 9. A mail would be sent to the recipient mentioned earlier with the carrid value entered.
SAP Workflow Customization Settings (How to do)This document details the basic workflow customization that needs to be done in any SAP system before activating the workflow definitions. Go to transaction SWU3.
The description or the help for each of the above steps are available on the right side of the screen. Configure RFC Destination This can be done automatically or manually. If done automatically, as mentioned on the right side frame, the logical RFC destination WORKFLOW_LOCAL_XXX is created (if not available). XXX is the client number. Also the user WF-BATCH is also created if not already available. The advantage of executing the above step manually is we can maintain another user and password as required. Select the step Configure RFC destination and click on F9. If you happen to get the following popup, click on Yes.
Once the RFC destination, you can see the Green Tick mark beside Configure RFC Destination (as shown in the screenshot below)
Maintain Workflow System Administrator Since the system being used for this demo is an IDES system, some user is maintained as workflow administrator. You can change this to the desired User using this step. Select Maintain Workflow System Administrator and click on F8.
Now you can change the Userid to the desired one. The steps Maintain Active Plan Version, Classify Decision Task as General, Document Generation/Form Integration, and Maintain Time Units are already in Green. If not in Green, select the corresponding step and click on F9. The automatic configuration would be done. Schedule Background Job for Missed Deadlines This is the job which checks if any work item has