You are on page 1of 2

Creating Approval Workflows 

 
If you want to create your own approval workflows, you should always copy a standard workflow and
edit the copy or use the Workflow Wizard. You should not modify the standard workflows. You
can find the standard workflows in Using Standard Approval Workflows. (You can find Workflow
Wizards in the Workflow Builder [Transaction SWDD   Navigation Area   Workflow Wizards   
Approval Procedure  .)
Make sure that the following values are transferred to the subworkflow:

Element Description

ApprovalAgentList List of users who have already approved the item. If the approval process is
canceled and this list does not exist, the users are not notified by e-mail.

ApprovalResult Approval status. This element must contain 0 if the approval was successful and
1 if it was unsuccessful. If the element is empty, the requirement coverage
request is not transmitted to the back-end system.

UserRejecter The element must contain the user who last approved or rejected the item. If the
user rejects the item and the field is empty, his or her name is not included in the
e-mail sent to the creator of the requirement coverage request.

ReqReq Contains the requirement coverage request (Business Object Type BUS2121)

LastChangedTime Time of the last changes made

We recommend that you not change the subworkflow. In this way you ensure that functions such as
'Send e-mail to creator in case of rejection' or 'Call spooler' work correctly.

Activities
1. Copy a standard workflow, edit the copy, and activate the workflow.
2. Enter the new workflow as a start condition.
You do this in Customizing for SAP Supplier Relationship Management under   SRM Server   
Cross-Application Basic Settings   Business Workflow   Application-Controlled Workflow   
Business Process Configuration   Define Conditions for Starting Workflows  .

 NOTE
Use the following tasks to send work items for approval of confirmations to the inbox.
TS10007950 (Invoices)
Copy the following tasks to send work items for approval of requirement coverage requests to the
inbox.
TS10008126 (Requirement coverage request)
Creating Ad Hoc Workflows
You can generate your own workflows for approving requirement coverage requests and can allow
the creator of the requirement coverage request within such a workflow to change the processor, at
runtime (ad hoc workflow). You do the following:
1. Create the necessary SAP B2B Procurement workflow using the Workflow Wizard.
2. Maintain the possible processors for the workflow tasks, for which you want to offer the ad
hoc function.
You do this in Customizing for SAP Supplier Relationship Management under   SRM Server   
Cross-Application Basic Settings   Business Workflow   Application-Controlled Workflow   
Technical Configuration   Perform Task-Specific Customizing  .
3. Maintain the users that may change the processors of a workflow task.
You do this in Customizing for SAP Supplier Relationship Management under   SRM Server   
Cross-Application Basic Settings   Business Workflow   Application-Controlled Workflow   
Technical Configuration   Perform Task-Specific Customizing  .
4. To test the workflow, start it and change the processor when displaying the shopping cart
using the personal object worklist (POWL). As a result, the newly entered processor receives
the work item, which in turn is removed from the previous processor's Inbox.

You might also like