Hello All,

This blog explains about how to remove duplicate LCG that is created during the process of Content Activation when we upgrade from SolMan 7.1 to SolMan 7.2

Those who had worked in Solution Manager 7.1 would be very much aware that there were individual SOLAR projects with Logical components created for respective Technical SAP System. When multiple SOLAR projects with same technical system was created, SolMan 7.1 did allow the consultants to proceed.

For example : In SolMan 7.1, you can create multiple SOLAR projects say Project A and Project B with SAP systems like ECC, CRM, Portal. Project A can have LC1 for ECC whereas Project B can have LC2 for the same ECC system. Hence two logical components for same ECC system is existing.

Now while performing Content Activation GP 2, SOLAR projects which are to be migrated are included in the scope which thereby includes the Logical component as well. There is no possibility to rename or exclude the duplicate Logical components during the process of Content Activation.

As a result, multiple Logical components getting migrated, causing the creation of duplicate LCG in the new SolMan 7.2 solution called ‘Main Solution’.

List of duplicate LCG created due to Content Activation

We will now see how to remove these duplicate LCG after Content Activation.

We have created another solution called “Test Solution”, which is used during the duplicate LCG removal process.

For example: CRM_SERVER00001 and CS_CRM_70_CRMSERVER_REPOR00001 LCGs are merged into single CRM i.e., ZSAP_CRM LCG in the Test Solution.

Step 1: Take one SOLAR project at a time and create a separate scope – LCG wise

Creation of scope – LCG wise

Step 2: Export the contents of scope created in step 1, from the Main Solution.

Export the scope created in step 1

Step 3: Now, go to Test Solution -> Solution Administration -> Import

Here while doing the import into the Test Solution, make sure you assign & merge with the desired target LCG mapping as shown below

Perform the merging of LCG while importing

Based on my experience gained during this process, I have classified the work as below,

Case 1: If there are no Config units at Process or Process step level, it is a direct export & import of the BPML hierarchy with 1:1 LCG mapping.

Case 2: If there is a Config Unit at Process level, then check the elements of it and make sure all of them are assigned with same LCG. If so, then proceed with export & import into JSON files.

Case 2.1 : If the elements are of different LCG, then create a copy of the Process and in that copy, we need to create new Config Unit at the library level and split the elements of the Config Unit – LCG wise.

Now we should create separate scope with respective Config Units, perform export of scopes into JSON files & import of them. After import, we need to perform merging of the Config units & Processes at the Library level as well as Business Process level.

Case 3: If there is Config unit at Process step level, then proceed with steps mentioned in case 2.1

Below screenshot shows how the split of Config Unit is done before export and after import for your references.

Config Unit at Process Level named Managing Recruits

Expand the Config Unit to see the LCG of the elements

Now create a copy of the Process ‘Managing Recruits’ in the Business Process level and then create a copy of Config Unit at Library Level as shown below

Copy of the Process at Business Process level

Copy of Config Unit at Library level

Now split the elements of the Config Unit – LCG wise at library level is done as shown below and then create separate scope – LCG wise.

Split of Config Unit elements – LCG wise

Split of Config Unit elements – LCG wise

Now follow step 2 and perform export & import. After import, merge the Processes by right click -> Merge Process.

Merging of Process in Test Solution

Important Takeaways from this approach:

1. There is a limitation in this approach as the entire process is very much time consuming and complete manual effort – Creation of multiple scopes, Performing Exports of these scopes into JSON files, Importing Transport of Copies(TOC) before importing the JSON.
2. While exporting the contents, if either of the checkboxes are selected to include KW Documents, Test Configurations etc., then TOC has to be imported first before importing the JSON file.
3. Cross verify the contents across the solutions and make sure all the contents are migrated.

Comment and share this blog to your friends who have their customer solution with duplicate LCGs after Content Activation.