SAP Solution Manager 7.2 · Solution Documentation: Architecture & Config

What changed about Solution Documentation in 7.2 versus the old three-level BPM approach?

7.2 dropped the three-level business-process hierarchy and the need to build process-modeling integration (open API still supported) or multiple projects for to-be processes.

New: library reuse for lean docs, built-in free BPMN 2.0 graphical modeling, solution+branch lifecycle. Biggest win: tighter ChaRM↔Solution Documentation integration — processes and their docs release to production alongside the technical objects, keeping business docs in sync with system reality.

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: Architecture & Config

How can you extend Solution Documentation for better governance reporting?
How do digital signatures work for Solution Documentation documents, and what must be active first?
What does an authorization group control in Solution Documentation, and what are its rules?
Attribute-level authorization in Solution Documentation only checks one action — which, and what can't you do with it?
What three template users does SAP preset for Solution Documentation, and what can the admin one do?
What does 'Generate Library' do in Solution Documentation, and what does it distinguish between?