SAP Solution Manager 7.2 · Requirements Management

How does Requirements Management integrate with Release Management?

An IT requirement is assigned a Change Cycle Phase.

When the IT requirement is accepted, a successor change document auto-generates (usually a normal change); the solution architect defines a feasible development window driven by ChaRM's change cycle, and the business manager accepts the proposal.

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 Requirements Management

What's the IT requirement flow in Requirements Management?
What's the final acceptance sequence in Requirements Management?
How does Requirements Management integrate with Solution Documentation, and why is that useful?
What are the two new transaction types in Requirements Management, and why do they resemble ChaRM transactions?
How does Requirements Management guarantee traceability across its documents?
When creating a business requirement, what's the difference between the Web Client UI and the Fiori launchpad views?