Best way to manage different landscapes data in solman

[Former Member]

Hello,

We are interested in using certain solman functionnalities to our complete customers landscapes.

Our situation is that we manage the SAP landscape of many diferent customers. Each landscape is maintained individually from the others. We would like to enter the data of those landscapes into our solman.

But this causes some issues with duplicate SIDs for instance. Indeed several landscapes share the same SID for different systems. A direct consequence of this is that the wizard used to create system RFCs will have trouble with duplicate users, since it uses the SID to create the users on the solman (SOLMAN<SID>).

A way to workaround would be to define those users manually, but maybe that solman has a functionnality to handle these situations ?

Thanks in advance for sharing your thoughs.

aidan

[Paul_Babier]

Hello,

If you have customer A landscape with SID's XXX, YYY, and XYZ under Installation 12345678 and customer B landscape with SID's XXX, YYY and XYZ under installation 23456789. Solution Manager will have no problem distinguishing Customer A systems from customer Bs systems, even though they have the same SID. It is not the SID that needs to be unique, it is the installation Number + the SID that needs to be unique.

And Customer A would never have systems installed on Customer B's installations. Thus I do not see there is an issue here.

However If customer A has a duplicate SID under the SAME installation number, this can cause a number of problems, especially anything related to service sessions. In fact in regards to EWA's SAP Note 1257308 - FAQ: Using EarlyWatch Alert

mentions this in the section 5. Restrictions and Prerequisites, second point...

Identical SID and installation number:

EarlyWatch Alerts are identified by the key <Installation Number>

and <SID>. It is not possible to process EarlyWatch Alerts for

two SAP NetWeaver based systems with the same SID and

installation number in one Solution Manager.

But you could utilize a second Solution Manager to accomplish this if required.

The Note also describes how to deal with Stand By systems, where they would have the same name, for instance in a fail-over scenario or a disaster recovery situation.

You do realize that you can utilize clients to group users, so you can create a client for each of your customers, because the RFCs created by the wizard follow the format SM_<SID>CLNT<Client>_* (BACK, TMW, TRUSTED, READ, ETC). So the client will be unique to each customer.

So I hope this helps.

Regards,

Paul

[Miguel_Ariño]

Hello,

The SMSY transaction has got a functionality to sequentially add suffixes to the SIDs of duplicate systems, so they will be SID001, SID002, etc.

I would expect the users defined automatically for SID002 to have the full long system ID.

Best regards,

Miguel Ariñ