When you buy a subscription to C4C you are, whether you are aware of it or not, accepting what SAP views as best practice in the Marketing, Sales and Service arena. The system is largely pre-configured and you can make limited changes to the behaviour of the system through configuration. Furthermore, while enhancements are possible via the Cloud Application Studio (SDK) the enhancements are limited compared with what is possible with the on premise SAP CRM product.
These are not criticisms of the product, I'm a big fan of C4C. I am however, getting frustrated seeing projects that:
- Are resourced and managed like traditional SAP CRM on premise projects
- Kick-off with Blue Sky design workshops (it's too late for that!)
- Are based on assumptions that the SI and the Customer have made about C4C capability based on their knowledge and experience of SAP CRM.
Any one of the above points alone has the potential to be a project killer. Successful projects are the ones where both the SI and the Customer understand this.
I have a particular bee in my bonnet about the way in which SAP C4C projects are currently being resourced – hence the image at the top of this blog.
We've recently completed a successful implementation of SAP C4C with SAP America for a global retailer. The project was delivered with just two SAP C4C Functional Consultants an integration resource and couple of developers. Perfect resourcing.
By way of comparison, we were engaged earlier this year on a project with a tier 1 SI for a UK-based business with 6 SAP C4C Functional Consultants. More recently, I've heard of projects with more than 10 SAP C4C Functional Consultants. These are large numbers of Functional resources for an SAP CRM on premise project let alone a SAP C4C project.
What are these people doing? How many SAP C4C Functional Consultants does it take to change a lightbulb, anyone?
If you've not worked with SAP C4C, I understand that you may be unconvinced by my message. So I will illustrate my point by showing you the main SAP C4C configuration options relating to an Opportunity.
Step 1 – Add Opportunities to your Project Scope
The answers we provide to these Questions allow SAP to automatically preconfigure the behaviour of the Opportunity in SAP C4C.
In this example, we'll focus on the basic Opportunity so I'll skip the Sales Assistant settings which allows us to identify the tasks that need to be performed at each Phase of an Opportunity.
We'll drill into a couple of these just to give a flavour of the "depth" of configuration possible.
This is the SAP C4C equivalent of the SAP CRM Partner Determination configuration. Note that we do not have the ability to define new Partner Determination Procedures – there is just one. Furthermore, Access Sequences are not accessible although standard Access Sequences are being used behind the scenes by SAP.
Source configuration is similar to SAP CRM.
We don't configure Transaction Types in SAP C4C in the way that we would in SAP CRM. In SAP C4C we have Document Types. In our demo environment you can see that no Document Types have been configured. We are using the SAP C4C internal default. While I can define new Document Types the value is limited unless I am integrating with a back-end SAP system. The behaviour of the Opportunity in SAP C4C is not driven by the Document Type in the same way as the Transaction Type in SAP CRM. Note also, we can only define a Document Type and Description. There is no Partner Determination Procedure, Organizational Determination Profile, Actions Profile, Text Profile etc.
To return to my original point: SAP Hybris Cloud for Customer (C4C) is not SAP CRM in the cloud. Now, what are all those SAP C4C Functional Consultants going to be doing?