Flexible Workflow For Sourcing and Procurement in SAP S4H
Flexible Workflow For Sourcing and Procurement in SAP S4H
Flexible Workflow For Sourcing and Procurement in SAP S4H
Even though both Release Procedure and SAP Business Workflow are still available in S/4HANA, it is
recommended that you use the new Flexible Workflow functionality in S/4HANA. The flexible workflow is
based on a set of predefined workflow scenarios and tasks. This provides the functionality to define condition-
based workflow for different processes in sourcing and procurement. It is possible to define single or multi
step approval processes, and the relevant workflow items are made available in the My Inbox Fiori App for the
approvers. Manage Workflows Fiori Apps are available for different purchasing documents, and these apps
allow the Business process specialist to set up workflows based on the business requirement
In this blog, I will explain the configuration steps and provide screenshots for workflows for Purchase Order.
The steps to implement workflows for other purchasing documents are similar, and the information provided in
this blog may be used as reference material.
Prerequisites:
Differences and Advantages between Classic Release strategy and Flexible Workflow:
SPRO => IMG => Material Management => Purchasing => Purchase Order => Flexible Workflow For
Purchase Order => Maintain Standard Settings
Runtime Environment
Definition Environment
Additional Settings and Services
Classify Tasks as General
Open the Manage Workflow for Purchase Orders. The application is blank with the message “There are
currently no scenarios available”.
SPRO => IMG => Material Management => Purchasing => Purchase Order => Flexible Workflow for
Purchase Order => Scenario Activation
Activate the workflow scenario ID as shown in the table below. Scenarios will become visible in the Manage
Workflows for Purchase Order Fiori App once activated here.
SPRO => IMG => Material Management => Purchasing => Purchase Order => Flexible Workflow for
Purchase Order => Activate Flexible Workflow for Purchase Orders
4. HR-BP-User synchronization:
It is the prerequisite to use HR and BP to assign the task of releasing PO for a user, assign a user to the
Personnel number with the communication type.
SPRO => IMG => Enterprise Structure => Definition => Human Resources Management => Personnel Areas
Click on Personal areas
Select the line item click on details
SPRO => IMG => Enterprise Structure => Definition => Human Resources Management => Personnel
Subareas.
SPRO => IMG => Enterprise Structure => Assignment => Human Resources Management => Assignment of
Personnel Area to Company Code.
Search in the APP Finder for which Process we have to create. Here I’m doing Manage Flexible workflow for
Purchase Order.
4. Manage Workflow for Purchase Order: Setup Required Pre-conditions and Step Sequence.
Click the Add button to create a new workflow for purchase orders. This will open the Nelw workflow page
Enter Workflow Name, Description, Valid From, Valid To. Enter the Start Condition for the workflow.
To add the Step sequence, click the add button in the Step Sequence Section. In the New Step page, Enter the
Step Name and Step Type as Release of Purchase Order.
5. For Recipients Select User for Assignment By. For the user field, select a user from the Search help.
1. One of the Recipients – If one Recipients is Approved the Flexible workflow is released.
1. All of the Recipients – If there are multiple Approvers all Recipients are to be released then only the
Flexible Workflow is released.
If we know the User ID, we can directly enter the username in the search box or else we can click on the Go
button to see the existing users in the system.
6. If we can’t get any User ID, then we have to check the below Configuration.
i. Activate HR Integration –> Goto SM30 –> Maintain table T77S0 –> search for entry group: HRALX,
sem. abbr.: HRAC and set the value abbreviation value to X
Exception Handling:
8. If the Approver Reject the workflow what is the action result is to be taken is maintained here.
9. click the Add Button to Add the above step to the workflow.
Click the Define Order button to ensure that the workflow gets triggered if the Start conditions are met.
12. Create a Purchase order in the Manage Purchase order application. We can see the Approval Details for
the Purchase Order in the Approval Details tab.
13. Open the My Inbox application for If the relevant task is not visible do the below steps.
14. Goto SAP Gateway Service Enablement –> Content –> Workflow Settings –> Maintain Task Names and
Decision Options.
ii. Select the above entry and click on Decision Keys and maintain the two Decision keys as below.
15. Assign Agents and Activate Event Linkages for Workflow ID WS 00800238 and TS 00800531
SAP NetWeaver –> Application Server –> Business Management –> SAP Business –>Workflow –> Perform
task-specific Customizing
ii. Click Assign Agents –> select line with TS00800531 –> Click Attributes and select General Task–>click
Transfer.
iii. Click Activate Event Linking–>Expand the hierarchy to display the relevant event for WS00800238 –
>Activate the linkage for the listed event by clicking on the Deactivated button.
iv. Once done the task will be visible in the My Inbox application, but still, there is no mail received by the
recipient.
16. Now let’s set up the Email transmission. The prerequisite to set up the Email is as below:
i. In Transaction Code S_ATO_SETUP, set up Adaptation Transport organizer with specific data using ZZ1_
as prefix and sandbox prefix as ZZ9_.
After maintaining the prefix and sandbox prefix click on the setup specific data to create setup.
ii. SOST and SCOT configuration should be in place
These are the initial screens of SOST and SCOT. These two transcations are done by the Basis team.
Transaction code SOST is used to display and administer of all messages sent using SAPconnect. The program
displays send requests that are being sent, or have already been sent by using SAPconnect. In this transaction, a
send request always contains just one recipient.
Mainly SCOT Transaction code is the one where we can get the notifications through Mail ID, FAX etc.,
17. Open the Maintain Email Template application. In the pre-delivered section find the template
SWF_CRT_NOTIFY_RECIPIENTS.
18. Copy the above-mentioned template for each of the workflow scenarios. e.g., YY1_00800238_CRT_ALL
for PO. This workflow template will be triggered to notify the recipients of the newly created PO, or whenever
there is a PO task for approval.
19. Copy the pre-delivered template SWF_WORKFLOW_COMPLETE_NOTIFY for each of the workflow
scenarios. e.g., YY1_00800238_COMPLETE_POSITIVE for PO. These workflow templates will be triggered
to notify the recipients of the completed POs, whether completed positively or negatively.
Test again by creating a PO. If the mail is still not getting triggered Report
RSWF_OUTPUT_MANAGEMENT needs to be executed manually with parameter productive in order
to release the emails manually.
With this, we conclude the configuration required for Flexible Workflow for Purchase Order including the
email trigger functionality. Please do share in the comments if there are issues apart from the ones mentioned
in the blog.
Conclusion: Flexible workflows can be customized through the scenarios that can be created and made
suitable according to the needs of your processes without needing any development. Also, key users can make
changes and edit these scenarios without needing developers.