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

What does a 'conflict' lifecycle state mean for a SolDoc element, and why does the maintenance branch take priority?

Elements have per-branch states: unchanged / created / changed / deleted / conflict. A conflict = changed in this branch and changed in parallel in the parent — resolve by release/discard/mark-resolved.

The maintenance branch has priority over sibling branches because it's production's natural change environment — a sibling's conflicting change immediately enters maintenance conflict state and must be resolved at once. Use Change Tracking Mode to see states.

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?