SAP Solution Manager 7.2 · Solution, LCGs, Branches & Sites

A colleague scopes a new solution to cover only the SAP ABAP production systems. Why is that scope wrong?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Solution, LCGs, Branches & Sites

A customer runs separate production systems in three countries and wants them all under one solution. Sites or one-solution-per-country — which, and why?

On 7.0/7.1 you maintained many logical components just to handle mixed software versions. What does 7.2's LCG change about that, and why does it matter for EarlyWatch/BPMon/ChaRM?

You're trying to assign a parent branch to the production branch and the system won't let you. Is this a config problem to fix, or expected?

What do you lose by splitting your landscape across several solutions instead of one all-in-one solution?

In SOLADM, which tab decides whether a system is under ChaRM control, and what's the unit you actually toggle there?

You want changes to production documentation to require a change request first. Which branch gives you that gate, and what else must be in place?

Start learning today

Free to start — download the app or use it in your browser.