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

What's the best practice on how many branches to create, and why have multiple project teams share one?

Create as few branches as possible; manage emergency corrections and minor-release changes in the maintenance branch.

Have multiple project teams share one branch — the benefit is that conflicts surface early, forcing teams to align rather than drifting apart silently.

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?
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?
What does a 'conflict' lifecycle state mean for a SolDoc element, and why does the maintenance branch take priority?