SAP Solution Manager 7.2 · Solution Documentation: Solution Structure (Branches & Sites)

What is a 'site' used for, and how do you enable it?

For customers with multiple production systems (each region/plant starting from a global template but differing locally in code/config/usage). A site categorizes systems by location/entity.

It's a built-in standard attribute on nearly all SolDoc elements, letting you mark content site-specific or global for reporting or process-manual generation. Disabled by default — enable via Solution Administration → Properties → Landscape with Sites, then build with Maintain Sites.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Solution Documentation: Solution Structure (Branches & Sites)

How do branch inheritance and releasing changes work in 7.2 Solution Documentation?
What is a 'solution' in 7.2 content management, and what's the best-practice number to use?
What does a classic five-system ERP landscape look like in LCG terms?
What's the best practice on how many branches to create, and why have multiple project teams share one?
How does a Logical Component Group let non-technical users connect a process to systems, and what do its logical components represent?
What does the product/version-independence of a Logical Component Group let you include in a solution, and who else reuses it?