CRM and CX Blogs by Members
Find insights on SAP customer relationship management and customer experience products in blog posts from community members. Post your own perspective today!
cancel
Showing results for 
Search instead for 
Did you mean: 
nikhilwalsetwar
Contributor
SAP CLM (formally known as Callidus CLM) is not only a contract management system but also a valuable tool which can help business to track the agreement between multiple parties involve in a transaction.

Let’s consider an example where a spare part manufacturing company (ABC Spares Ltd.) is sending a quote to an airplane manufacturing company for 800 items. There should be some legal agreement done between these two parties before proceeding further. To get to the common conclusion on legal agreement, both parties need to communicate to each other for the same. During this process, some discussion or negotiation might happen between these two parties. In this case, if the sales representatives are using old school approach then it might be difficult to track the changes, and this will have an impact on sales representative’s productivity (as most of the time will be consumed by the documentation). SAP CLM offers the feature which can reduce the sales representative’s overhead to manage the documentation (may be legal, or quote proposal) and helps them to focus on more deals to generate more business.

Now let’s consider, in this case if ABC Spares Ltd. is using SAP C4C as their Cloud CRM solution then it will be very difficult to handle the quote negotiation and manage legal/contractual agreement with customers. Till 1908 release, it was very painful but now with beta release of C4C + CLM integration the missing piece is introduced, and the life of sales person is getting easy. Please refer this blog post for detailed CLM features.

After 1905 release of SAP C4C, we can configure two types of quotes. One for simple products which will be a standalone C4C quote and other for configurable quote by integrating SAP C4C with SAP CPQ.

Below is the pictorial representation of two different scenarios that will help you to understand the importance of this integration,

 



 

In scenario 1 – When the quote is created for configurable products in SAP CPQ then the quote negotiation can happen by using CPQ quote portal or CLM can be integrated if some legal documentation/agreement needs to be signed before proceeding further.

In Scenario 2 – Before 1908 release, the quote negotiation or any legal documentation must be done in different system, mostly it used to be over emails and adding different versions under attachment section of Sales quote Which was very difficult for anyone to track the change (Even it was difficult for customer to view the history) but after this integration is released in 1908 release cycle. All the documents can be managed centrally, and it has become easy to use

As stated above this is a beta release of this integration, and in this blogpost, we’ll see how we can integrate SAP C4C with SAP CLM,

Step 1 – As this is a beta release feature, it will require an incident to enable this feature in SAP C4C. After its final release, the scoping question will be available under path,

Business Configuration -> Implementation Project-> Edit Project Scope -> Step 4: Questions and navigate to path “Communication and Information Exchange -> Integration with External Applications and Solutions -> Integration Scenarios with Cloud Solutions from SAP”.

Step 2 – Enable the C4C sales document type for which you would like to use CLM document preview option. In this case, I’ve created a new document type ‘ZQ – Internal Pricing Sales Quote – CLM’.

Please follow below path to create it,

Business Configuration -> Select Project -> Open Activity List -> Search Sales Quotes activity -> Maintain Document types,



Step 3 – Create an admin user in CLM so that you can use embedded CLM administration console in SAP C4C. This admin console will be available under Contracts -> CLM Administration workcenter.

To create an admin please follow path Admin login ->Users ->Create new user, by following the pattern C4CUserID.C4CtenantID. for example, in C4C your user id is nikhil and your C4C tenant is ‘my123456’ then the CLM username will be ‘nikhil.my123456’



Step 4 – Enable the ‘CLM Administration’ view for admin user



Step 5 – Add C4C system details under provider settings in SAP CLM,

Navigate to CLM Administration view -> Setup -> Providers -> SAP Cloud for Customer,



 

Step 6 – Add C4C tenant URL and Tenant id in below settings as,



 

Step 7 – Create or map document types and fields. In this example we’ll be using a test example to show how to use tags so that SAP C4C Sales Quote Data can be passed to SAP CLM to proceed further. To create a new template, navigate to ‘Contract-> CLM Administration -> Contracts -> Contract Types’.



 

Step 8 – Add require details and upload the template under template section, in this example we’re using attached template.

 



 

Step 9 – Save the settings.

Step 10 – Create a sales quote with document type configured in step 2 by adding mandatory details and products. And Click on Actions -> Open Document



 

Step 11 - Now, this action will provide an option to select the template which you would like to use to generate document. Select the template which we have created in Step 8.



Step 12 – The related document is generated in CLM and you can take it ahead according to your further business process in CLM. You can see the assignee (like a document owner) in CLM is automatically determined based on the login user id in SAP C4C (as stated in step 3)



With this note I would like to conclude my blogpost around the benefits of SAP C4C + SAP CLM integration. Keep Integrating ?

References – Help Documentation - https://docs.calliduscloud.com

Product Feature and functionality blogpost - C/4 Sales Cloud: Common Business Scenario for Contract Lifecycle Management (CLM)

 

P.S. All business scenarios stated above are based on my understanding of the complete sales cloud solution capabilities. And it doesn’t hold SAP’s authorized documentation.

 

Thanks,

Nikhil Walsetwar
13 Comments