This depends upon the type of decommissioning and the current interface design. Although this is not complicated, some care should be taken. Here is what I recommend:
1. If it is just one interface with channel which is not reused, simply deactivating the channel should be enough. Make sure that both sender (if exist) and receiver channels are deactivated. Removing the interface from landscape should only be done if you are sure that this cannot be reused in future in any way.
2. I would suggest maintaining a list of such interfaces either through Solman or simply in some excel.
3. If the interface has lots of impacted objects e.g. ccBPM, enhanced or multiple receiver or interface determination etc., there shoudl be a thorough testing before the related objects are removed and this should be done only with transports.
4. Make sure you remove ID objects first and then ESR objects. This will ensure you don't have any inconsistencies in your landscape.
5. The decommissioning is not only about ESR/ID objects removal. You have make sure you remove any alert rule associated with it, any message prioritization related to it, any archiving rule setup for the interface, any value mapping related to interface, RFC destination in case of lookups - list goes on and on.
In short, decommissioning can be as little as deactivating channels, and as complex as removal of entire associated configurations. Refer to the original technical designs before designing the decommissioning process.
Regards.
Prateek Raj Srivastava
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.