Skip to Content

how to implement sales contracts in clm

In our earlier blog posts, we touched base on deployment scenarios (standard and integrated both) of Sales Contract Management. (please refer to the below links)

o   Part 1: http://scn.sap.com/community/sourcing/blog/2012/07/31/sales-contracts-with-sap-clm–part-1-business-process-overview

o   Part 2: http://scn.sap.com/community/sourcing/blog/2012/08/28/sales-contracts-with-sap-clm–part-2-first-steps-implementation-approaches

In this blog our focus will mostly be on:

     –       Security model

–       Master Data Replication

In our next blogs we will details about integration aspects, activities at PI, SD side and set up in CLM.

Securtiy model

In case both the procurement contracts and sales contract exist on the same system; one should consider the security aspects based on the fact that sales organization users and procurement organization users should access the relevant data. To cater such kind of requirement there can be two implementation approaches that can be taken to support sales contracts. The selected approach will depend on the customers’ requirements.

  1. Single Context Implementation:-

  In this case, the customer implements a single enterprise context and makes the necessary adjustments to the supplier record (to support suppliers and customers).  

  • Probably two separate set of groups need to be designed to cater users belonging to procurement department and sales department.
  • Customers are encouraged to develop a script which would validate if persons belonging to a certain group are accessing the information relevant to them.

  Key points to be considered while adapting the above approach;

  • Single system does not provide for the necessary data segregation. As a result, some configurations along with developments are likely necessary.
  1. Multiple Context Implementation:-

In this scenario, CLM can be used for sales contracts as well as other contract types (e.g., procurement contracts) where multiple contexts need to be designed with two options;

  • The customer implements separate enterprise contexts for each contract type. This provides for a complete segregation of the data. It requires users to login to the different contexts to see the data.
  • The customer implements separate company contexts (sub-contexts) for each contract type. This provides for a complete segregation of the data. It requires users to login to the different contexts to see the data. Consolidated reporting is custom and maybe done outside the system. Master and configuration data are shared between the two company contexts.

           Key points to be considered while adapting the above approach;

  • Most users tended to be working with one type or the other, but not both. But there are a few users (e.g., Legal) that require the flexibility to see both. Unfortunately, with multiple context implementations user duplication might be required. As separate systems (or contexts) require separate logins.
  • There will not be any consolidated reporting on both procurement and sales contract. This requires reporting done outside the CLM system.

Master Data replication

In an integrated scenario for procurement and sales contracts; there exist 3 systems SAP Sourcing/ CLM, SAP ERP-SD, SAP ERP-MM in the landscape.

Procurement integration –> CLM to ERP-MM

As far as MM-CLM integration is concerned standard implementation should be followed; i.e;

  • Pull vendor and material as well as other relevant master data from SAP ERP-MM to SAP Sourcing/ CLM
  • In standard the above details are pulled through reports. In case of any custom master data pull through custom reports should be run at ERP-MM side.

Sales contract integration –> CLM to ERP-SD

As far as SD-CLM integration is concerned a custom implementation strategy should be developed; i.e;

  • Pull customer and other relevant master data from SAP ERP-SD to SAP Sourcing/ CLM. Custom reports should be run at the ERP-SD front to pull through the details.
  • Delta reports should also be run at the ERP-SD front to pull through the delta changes happening in ERP-SD.

Detailed master data enablement is as shown in below picture.

MD details.png

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply