Solution Documentation: Solution Structure (Branches & Sites)

You release a fix to the production branch. A teammate asks whether they now need to re-apply it manually in the project/dev sub-branch so the next release also has it. What do you tell them, and what's the one release-time choice that can still trip you up?

A multi-region company wants each region to own its solution documentation independently, so they plan one solution per region. Why is that the wrong instinct, and when is the opposite actually correct?

Where must Business Process Monitoring live — and what is the one thing monitoring experts are NOT permitted to do in that branch?

An end-to-end process touches a non-SAP system. Can a Logical Component Group represent it, and what single property makes that possible — plus who else depends on that same property?

Two project teams will work in parallel. Should each get its own branch, or share one — and which way does the trade-off actually cut?

You need to update Solution Documentation that's currently in production. Which auto-created branch do you edit, and what happens if you try to change production directly?

A SolDoc element shows a 'conflict' state. What actually caused it (vs an ordinary edit), and why does the maintenance branch get priority when resolving it?

A customer runs multiple production systems from a global template that differ locally. They start tagging content with the Site attribute but it does nothing. What did they skip?

Within a Logical Component Group, what do the individual logical components represent — and how is that different from what the LCG name represents?