Cleaning up Old systems or marking obsolete after upgrade

[deidre_logan]

Hello there,

We have 80+ systems in our landscape. We have SAP R3 4.7 Enterprise to ECC 6.0 installations. We have BW systems. We have PI systems....

We just went through an upgrade of our oldest system that was 4.6C. We had manually placed these systems in the SLD. I have deleted the old 4.6C systems from the SLD but how to clean these systems out of Solution Manager? The SLD fed this system information to our Solution Manager so I can not update the system in SMSY because it is marked as the Source being SLD.

This system was in a Logical component and in Projects.

I see in the gateway logs that Solution Manager is still trying to talk to this system. How can I stop all the obsolete systems that we want to keep for documentation purposes in the projects and in the old logical components but tell Solution Manager not to monitor or try to get information from this system.

We have other instance where we bring up and sandbox and now the sandbox is gone.... so we are accumulating quite a mess in solution manager with out knowing a way to retire a system.

Thanks for your assistance.

Deidre Logan

[Paul_Babier · Accepted solution]

Hello Deidre,

In SMSY, the data source is the last data source used. This is a status and not where it is changed.

The SLD will update SMSY when the job landscape_fetch runs.

So if you removed the systems from the SLD, then when you delete them from SMSY they should not be recreated.

The systems must be physically retired, because if they remain up and on the network, they will continue to use the SM_<SID>CLNT<#>_BACK RFC.

If the systems are removed from SMSY, they should also be removed from the logicals, and projects. A logical can exist without a system assigned, but if that logical is in use, and has a retired system assigned, you will see activity when the logical is used, or checked by the system when that logocal is referenced.

So you need to remove the system from the logicals and the project. I don't know how ii might then affect your projects as a reference system. But then should you be using a productive system for this purpose? You can de-activate a logical in SMSY. Maybe that might help stop its use. The same would apply to projects, the system would have to be removed from any assignments.

Do you have a sandbox/test system where you could keep the old reference projects so you can properly define your system landscape? Really what you are doing by just pulling out the systems in SMSY is creating an incomplete configuration.

Regards,

Paul

[TomCenens · Accepted solution]

Hello

In my opinion it's not a great integration into all those parts of Solution Manager.

I heard they planned or already did an overhaul of SMSY transaction in the new Solution Manager version and it would be more than welcome.

To me it looks like most of those features were tested on rather small environment as when you have 100 - 200 SAP systems you get into a messy heap of content.

In your situation I think it's best you check where the SAP system is still integrated into (projects, business process monitoring etc) by using the "where used" on your SAP system. Depending on how far it is integrated into your Solution Manager I would either recommend to leave it in (if it's included in one of those) or remove it if it's not.

Another pain point can be the numerous places you might have to remove the SAP system (perhaps several SLD's) if you have a local SLD somewhere where the SAP system is included with a data supplier bridge to your central SLD. If it's included and auto generation is on (through landscape fectch), it will be regenerated in your Solution Manager.

Kind regards

Tom

[deidre_logan · Accepted solution]

Thanks for the input. So here are some more details.

We had a landscape that is 4.6c

DEV --> UNT --> QAS ---> PRD

So these systems exist in Solution manager and they created an upgrade project in solution manager.

Now We basis create a new development system that is upgraded...so during the upgrade we have a duplicate landscape.

Now the new landscape is

DV1 --> UN1 ---> QA1

then on go live weekend we upgrade production in place....

so the old landscape of DEV, UNT, QAS is retired...PRD is still valid... the old logical component and new logical component are in Solution manager as part of the upgrade project.

We want to keep the old logical component and old projects for reference for when we have to do another upgrade or whatever.

But I do not want my Solution manager trying to go to DEV, UNT, QAS...they have been taken down and will NEVER return in there old status.

I was just wondering how to limit RFC errors in the gateway....we have done 3 upgrade this year and now I have this situation times 3...so I have a Solution manager gateway busy doing unnecessary work...

I wanted to make sure I was not missing something in my configuration to tell Solution Manager that these were valid systems but now they are retired.

The old logical systems and is in many projects and it is too messy to clean up manually and the project team wants to keep the projects...

Let me know if there is a way to retire systems without a massive delete of the where used list...

[Paul_Babier · Accepted solution]

Hello,

If your objective is to limt RFC erorrs in teh Gateway, have you remvoed the old RFC conenctions?

If they are there, even if there is no system at the other end, the RFC's will be used, and because Solution Manager is

connected to the gateway when it tries to use it for RFC conenctiosn to systems that don't exist, you will get the errors on

the gateway. But if you remove the RFC's you will not get these errors. However you will get other errors because an expected RFC will now be missing.

WHy don't you explore these two links, as you may find there are better solutions for what you are wanting to do.

http://service.sap.com/saptao

http://service.sap.com/testing

Regards,

Paul

[deidre_logan · Accepted solution]

Thanks for everything. That was very helpful to delete the SM* connections in SM59 on Solution Manager.

It helps with the gateway errors but not on the solution of how to properly add and DELETE systems from an landscape during upgrades...etc...

thanks