SAP Solution Manager 7.2 · Graphical Process Modeling & Best Practices

How does the 7.2 change-management integration keep documentation in sync with software updates?

It aligns the technical-object lifecycle with SolDoc document changes.

After scoping SolDoc in a request for change / change document, the processor's dev/customizing edits update the scoped content in step. Customizing/code changes record into a transport and auto-attach to the change document; SolDoc changes record into the log. On release, the transport imports to production and the SolDoc changes auto-release into the production branch — so doc maintenance and software updates happen together.

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 Graphical Process Modeling & Best Practices

How does a documented business process get reused across the ALM phases?
Why can one process have multiple diagrams, and what's each one good for?
What are RDS / Best Practice Packages, and how do you import one in 7.2?
In SolMan's BPMN process editor, what does a lane represent when modeling by role versus by system?
What does the monitoring decorator show in the operational view?
What did 7.2's fully embedded BPMN 2.0 modeling change about SolMan's role?