Have you ever configured the Buyer Completion workflow in your SRM journey, I am sure that you would have definitely wanted a different exit criterion. More control bundled with compliance via the appropriate workflow.
Whenever the shopping cart needed modifications after it reached the point where the buyer had to update the price/qty or other parameters, it was difficult and there was some kind of non-compliance to deal with the cart for further processing.
If I have to understand today’s innovation correctly, it would be around providing flexibility bundled with compliance and a more robust exit criteria for downstream processing of the Shopping Cart.
1.0 Overview & Challenges
In today’s blog we would be discussing this new innovation on shopping cart modification in the sourcing application by providing support to the buyer to control what can be changed in the shopping cart and also help trigger the right workflow to stay compliant with the Shopping process when inside the Sourcing ****-pit.
The challenge that typically this innovation goes out addressing are mainly around
- It was not possible for purchasers to make modifications to correct shopping cart data in sourcing application
- Triggering the correct workflow post shopping cart modification by the buyer when dealing with the shopping cart from inside the SOCO was not available.
2.0 Help me understand this feature / innovation?
- When assigning sources of supply to shopping carts in the sourcing application, operational purchasers are able to make changes to the shopping carts to correct any inaccuracies in requisition data.
- Ability to customize which fields in a shopping cart should trigger an approval workflow.
- Ability to control editable fields with metadata configuration.
- All standard Shopping Cart checks are performed before saving an edited shopping cart.
- External requirements transferred into SRM will not be available for editing.
I personally see the following benefits & business value of switching this feature
- Purchasers can now modify requirements in sourcing application and an appropriate workflow is triggered for approval.
- More accurate data result in better sourcing decisions
3.0 Snippets of how this looks inside SAP SRM 7.0 ehP2
Shopping Cart Modification in sourcing application change Shopping Cart
Shopping Cart Modification in sourcing application Metadata Configuration to make Fields Editable
Shopping Cart Modification in sourcing application Configure changes relevant for workflow
4.0How do I achieve it?
The following Customizing activity is relevant: SAP Supplier Relationship Management -> SRM Server -> Sourcing -> Activate/Deactivate Approval Workflow for Changed Shopping Cart Fields.
1. Switch: SRM_SOURCING_2: Enable workflow for Shopping Cart changes from Sourcing application (SRM_702_SOURCING_SC_WORKFLOW)
2. Switch SRM_702_SOURCING_SC_WORKFLOW is revertible.
Thanks for tuning into these sequels, am sure that with SAP SRM 7.0 EhP2, you will have more power in your hands as an SAP Procurement consultant to help deliver those go-to customer implementations. In our next blog, we will discuss more about the POWL reports for SRM analytics & more to keep emphasizing on the Streamlined Sourcing Innovations
5.0) SAP Procurement social_media outreach channels
Hope to see you sign-up and follow our via all our Social Media Outreach channels
6.0) SAP Procurement handles & Hash-tags to follow