Strategy for System/Client Merge in SAP Landscape Transformation?

[former_member195698]

Hello,

I have two Systems A (client 100, 200, 300) and System B (client 100, 200, 300) which need to be merged together to have a single System B (with only Client 100).

What should be the strategy to be used for Merge of the Clients in the two systems to a single client in the target system?

Also, what should be the Implementation Phases? (No of Test Cycles recommended before the fina Go live)

Thanks & Regards,

Abhishek Jolly

[Former Member · Accepted solution]

Hello Abhishek,

You can use the Client transfer from SAP LT to create a multclient system.

And then use the customized client merge solution here.

You can find more details about client transfer and other solutions from SAP LT at the following location :

http://help.sap.com/saphelp_lt200/helpdata/en/4c/eea4775ee646978f4e92b656f953b1/frameset.htm

Thanks and Regards,

Tanu Mithal

[former_member195698 · Accepted solution]

Hello Tanu,

Thanks for the information but I would like to know the solution as to how the Merge/Transfer will be used for my sceario.

Will it be -- Merge all clients in system A and all clients in system B and then merge the two systems "or" any other approach.

[Former Member · Accepted solution]

Hello Abhishek,

Not an easy question to answer. As we need to analyze the systems involved and understand the harmonization requirements.

For client merge lot more objects would need to be harmonized than client transfer.

Thus this question would need some evaluation to be answered correctly.

Thanks and Regards,

Tanu Mithal

[former_member413267 · Accepted solution]

Hello,

what Tanu says is absolutely correct. There are a lot of things that need to be analyzed and decisions that need to be taken before the technical solution (tool etc.) can be discussed.

To be analyzed:

• Compare organizational structures in all clients
• Check and compare which SAP components are used
• Check and compare which processes are used
• Compare Customizing of clients
• Compare Repository (customer developments etc.) of both systems
• Check for duplicates in Master data
• Check interfaces
• ...

Decisions that need to be taken:

• Brown field (use existing client as target) or green field (use new system) aaproach
• Level of standardization (processes, org. structure...)
• Degree of master data harmonization
• With or without history
• ...

It is not just a technical exercise. A good consulting company can help you with the points above

Best Regards

Sascha Löffler

[Former Member]

Hi Abishek,

I fully agree with Sascha's recommendations. But for me, question number 1 would be:

What is the purpose of the one new system with 1 Client..?

The strategy to follow depends to a large extend on the answer to this question..

- Is it (just) a Sandbox system ?

- Is it going to be a sytem part of a development landscape ? And if so, how are the current Quality and Production systems/clients setup ?

In fact, i would advise to leave any kind of tooling behind, until you have a clear answer to the questions above. It might even be the case that you end up with requirements where no standard tooling from SAP can help you.. The only way out then is to ask the SAP Datamigration experts (former SLO-team) for advice. I worked together with them on a project in which we disentangled and rebuilt a 16TB SAP system landscape (IS-U solution). Anyway,.. i hope i could be of some help..

Best regards,

Jos Ouddeken