Skip to Content

Sales Contracts with SAP CLM – Part 2: First steps & implementation approaches

In our last blog post, I touched base on the business process of Sales Contract Management. With the help of our experienced SAP Consulting
group in particular Jagamohan Padhy, we will now expand our blog series with a lot of interesting topics around Sales Contracts deployment through CLM.


What is the process flow in SAP CLM ?

Following up on the more generic business process of sales contract management, the question of how the actual business process in SAP CLM would look like is coming to mind. Below is a diagram to explain (NOTE: bear in mind that the mappings through PI are non-standard and need to be custom created) 


What are the first steps ?

In order to guarantee that all the steps are in place, the following perquisites have to be taken into consideration:

  • Supplier Management & Customer Management Supplier management information has to be renamed considering that now the focus
    is on Customer Management information; this is typically done through changing all localized resources containing “supplier” in the system to “customer”.
  • Master Agreement types: The Sales Master Agreement should have custom fields/tables enabled to support business process and integration scenario for Sales Contract Management. This can be achieved through Page customization in SAP CLM.
  • Global Search: To take advantage of the full capabilities in SAP CLM, all sales contracts and master agreements need to be searchable by types which are typically achieved via creation of queries.
  • Data replication to integrated systems: When publishing master agreements on the buy-side, the information is going to ECC-MM whereas in the sales side scenario, the published information needs to go to ECC-SD. There is some custom work which needs to happen in PI to enable publish to SD.

What are the different deployment options?

There are four different implementation options in SAP CLM

  1. Standalone implementation for both sales and procurement contract
  2. Standalone implementation for sales contract and integrated for procurement contract
  3. Integrated implementation for sales contract and standalone implementation for procurement contract
  4. Integrated implementation for both sales contract and procurement contract


In a standalone scenario and non-integrated case, SAP CLM can be used for both procurement and sales contracts (case 1). Different sets of master data needs to be replicated into SAP CLM from workbooks, in addition to the standard set for procurement contracts, there would be a need to add also customer master data needs to imported e.g. through workbooks.

In the integrated scenario, once the contract management needs to be also published into the transactional systems such as ECC-MM for procurement and ECC-SD for sales contracts, there is some additional mapping to be done (for ECC-MM integration, please see these blogs). For sales contracts integration to ECC-SD, there is some custom design required.

You must be Logged on to comment or reply to a post.
  • Hi Armin ,

    I have done the POC on same model around 2 years back , has got some de merits as integration won’t be standard ,We need to write a scheduled script which puts all the values from the agreement into a csv file and the fields need to be mapped to SD agreements through PI,there will not be any standard integration as provided for SRM and ECC ,

    Just wanted to know if we can use UDO instead of customizing master agreement ,Because if we customize master agreement , it will be applicable to all master agreement type and it will be of no more use for procurement based contract as you mentioned in 4 th point above in deployment option.

    Appreciate you input


    Piyush Srivastava

    • Hi Piyush,

      given that UDO is basically a business document which comes with all the features of all other business documents such as Master Agreement, I don’t see a reason why this should not be possible.



      • Armin, I reffer to SD master data as Sales Area values ( Sales Area, Distribution Channel, Division) and Customer data ( like supplier data but reffer to Customers).

        This kind of data must be load from ERO to CLM vía PI custom mapping?

  • Hi Armin, in a “Standalone implementation for sales contract and integrated for procurement contract” scenario, I would like to know what about master data that belong to SD it means, does the standard CLM ( wave 7 or 9 ) support Partners creation from ERP both for Suppliers and Customers?

    • Hi Celeste,

      the integration into SAP-SD is not standard, only integration into SAP-MM is standard at this point. Master Data from SD would need to be integrated to CLM via PI and custom mappings.

      Which master data objects are you refering to ?



      • Hi, Armin.

        About the master data objects, we have a demand to bring the Customer Master from ECC to CLM. Any ideas on how we store this information on CLM?

        Furthermore, is it possible to change the Supplier Info tab to bring these Customer Master records instead of bringing the supplier records?

        We are using 7.0 OP here.


        • Hi Roberto,

          CLM has the option to import Custom Master Data, but as stated above the integration to SD is not supported in Standard but requires custom mappings in PI.

          The Supplier Info Tab can be changed to Customer via changing the Localized Resources in the UI.

          Hope this helps,