SAP Solution Manager 7.2
Solution, LCGs, Branches & Sites
15 flashcards · answers and review in the app — launching soon
In Solution Manager, what does a 'solution' actually represent?
Solution Documentation is the single source of truth for what, and how is it expressed?
Once you activate sites in a solution, what changes about a Logical Component Group?
What's the difference in how a Logical Component Group handles mixed software versions in 7.2 versus 7.0/7.1?
Why might you require changes to production documentation to go through a change request, and which branch enables that?
What is a 'branch' in a Solution Manager solution, and which branches exist by default in 7.2?
Why must a solution exist before you can use almost any SAP Solution Manager tool?
Which transaction manages solutions, and what must be true of a system before you can add it?
When a company runs production systems across several countries, what 7.2 concept lets them all stay under one solution?
You try to assign a parent branch to the production branch and can't — why not?
Where in SOLADM do you define which systems are under ChaRM control?
Under the 7.2 LCG model, how many LCGs does each major software component need?
What's a common four-branch setup for a Solution Manager solution?
In SAP Solution Manager BPMon, what is the operation branch used for?
Why manage your whole landscape under a single all-in-one solution rather than several solutions?