Hi,
So far a single instance of SolMan 7.1 is used for maintenance, monitoring, alerting and reporting on our SAP landcsape. Business is taking an interest on using more features in SolMan to benefit in areas like BPM, Projects, Sofware Logistics, IT Services .... A roadmap is being defined and a 2-tier SolMan landscape has been put in place : DEV/TST + QAS/PRD. My question is about software logistics for deploying SolMan functionality in projects.
What is best-practice ?
- consultants work in DEV using an IMG Project to isolate customizing and configuration changes between different projects ?
- changes need to be assigned to workbench/customizing requests, linked to a project, that can be released and transported ?
Other than technical basic configuration on the SolMan instances (making sure the managed systems are properly defined and RFC connected), there should not be any 'functional' configuration that needs to be redone on each SolMan system in the landscape, or ? As an example we had consultancy to set up QGM and CSOL on our DEV/TST SolMan conected to a test landscape of managed systems. Now we are ready to deploy to QAS/PRD SolMan. Our consultants tell us that only 50% of the work can be transported and 50% remains as manual configuration to be done in PRD ???
How do other companies deal with this ? How to avoid manual configuration on PRD to deploy SolMan functionality ?
Thanks & BR,
Johan