Skip to Content
Technical Articles
Author's profile photo Pradeep Velishoju

Customizing Synchronization by using Solution Manager 7.2

This blog gives you an overview of Customizing Synchronization process and how to achieve it by using SAP Solution Manager 7.2


When you have several SAP Components in your landscape eg, SAP ERP, SAP MDM or SAP MDG. Customizing settings which define business processes across systems must be synchronized.

Customizing must be synchronized include customer and product groups, sales areas, payment conditions, delivery conditions, commission groups, currencies, countries, regions and measurement units. etc.


To achieve this purpose, There are Standard Tools available within SAP Solution Manager which are, Customizing Distribution and Customizing Scout.

Below are the Steps for the configuration:

  1. Pre requisites on SAP SOLMAN, ECC and MDG.

Before going with setup, you need to fulfill the prerequisites like, Roles and Authorizations for the users involved.

you can find the required roles in below sap help URL.

       2.  Create RFC Connections

You need to establish connections to ECC and MDG from SAP SOLMAN.

Following connections required for the Customizing Scout:



Following connections required for the Customizing Distribution:



3.  Create IMG Projects from SOLMAN.


Here, Enter Source(ECC) , Target(MDG) SID and Client and hit the create button. this will take you to managed system by using trusted access and create an IMG Project.

Note: If you are using ChaRM in your landscape, you need to select No, when it is asking for to create CTS Project for the IMG Project.

You need to assign the CTS project which created from ChaRM to the IMG project by using the Report  /TMWFLOW/IMG_LINK_TO_CYCLE.








      4.   Define the Sync objects in MDG system 


Create Sync Object with the tcode SCDT_MAPPING and add the Tables/Views which you want to Sync from ECC system.

      5.   Build the Sync Groups in SAP SolMan 


Create new Sync group, fill all mandatory fields like, group name source and target components. select the Source and Target Logical systems from Search results (this will be searched from LMDB, you need to sync managed systems to LMDB properly and remove if any inconsistencies)

Enter the IMG project we created in step 3

then, click on Load object lists and save the changes.

Double click on created Sync group to add Sync objects which created previous step.

       6.   Setup Customizing Distribution in SOLMAN


Create new Distribution by adding Sync group and IMG project which created in step 5 and step 3.

Select Source and Target systems.  Select “Synchronization at Transport Release” this option will let you sync the objects whenever you make any delta changes in Source system  (On Going Distribution)

      7.    Run Customizing SCOUT for the comparison

Tcode: SCOUT

SCOUT tool compares the customizing objects in landscape that is differences in Source and Target systems.

The comparison helps you to synchronize the customizing settings when implementing or updating a system landscape.

You can use the comparison to eliminate differences in the customizing settings of the systems

      8.   Perform Distribution

Now you know the customizing differences in your system landscape, to sync the objects you can run the distribution.

There are 3 types of Distributions.

  1. Initial Distribution
  2. Automatic Customizing Distribution
  3. Distribute Individual Transport request Manually

Initial Distribution can be run from SCDT_SETUP, by clicking on push button “Initial Distribution” it ask you to schedule job and Transport request to which custom objects save in Target system.

once the job completed, you can see the changes in your target system. also logs can be viewed from the Tcode SCDT_LOG.

Automatic Distribution is useful to sync the Delta changes which are recorded in ECC System.

If you select the Distribution type as “Synchronization at Transport Release”  in SCDT_SETUP, when ever a Transport request released in ECC system with the sync objects which are defined in SCDT_MAPPING.

SOLMAN will notify the Transport request and Sync the object automatically to MDG system.

You can make Target transport request selection by enabling the SCDT_SETUP expert options (Edit -> Expert options)

This option let developer to select the Target system Transport request from pop up screen, when he release the Transport request from Source system.

Distribute Individual Transport Request Manually by using this we can distribute the objects manually by selecting the transport requests.

This can be done by Tcode SCDT_FETCH,  enter details like, IMG Project, RFC and Transport request and hit F8 to distribute the changes.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Syed Sulthan Ahamed
      Syed Sulthan Ahamed

      Hi Pradeep,


      Thanks for writing the blog, it's very informative.



      Author's profile photo Venkatesh Madanagopal
      Venkatesh Madanagopal

      Thanks Pradeep.. This document gives a good brief of the activity... Really helpful.....

      Author's profile photo SWAROOP V

      Thanks for sharing the details. Can you please answer the below question:

      This option let developer to select the Target system

      1.Transport request from the pop up screen, when he releases the Transport request from Source system. - will this pop comes in ChaRM screen when we release the TR?

      2.Create IMG Projects from SOLMAN -Do we still need IMG project for 7.2?

      Author's profile photo Faizal Ameenudheen
      Faizal Ameenudheen

      Good day Swaroop and Pradeep

      we are using ChaRM in our landscape and also wondering whether we will got a pop up when TR is released from the change document.

      your answers are highly appreciated



      Author's profile photo Martin Roszak
      Martin Roszak

      Good day colleagues,

      i am also struggling with Step3!

      i can use the transaction, i can also create IMG-Project, i am also forwarded into the source/target system i want to use at the end. But i am completely unsure about the next steps:

      do i need to create the transport request directly in the Project administration? do i need to activate CTS functionality?

      finally, the cycle i need to link to the img project, does is need to have the same LCG with the same source and target system in it?




      Author's profile photo Tilakraj Sandrasegran
      Tilakraj Sandrasegran

      Hi Pradeep Velishoju,

      Thank you for the blog and steps. We managed to implement based on your guide.

      Run Customizing SCOUT for the comparison was only running on single table for my system, issue fixed with note 3016481 implementation.

      Hope this helps others as well.