SAP Solution Manager 7.2 · Requirements Management

Why was the RfC a poor fit for handling new requirements before 7.2, and what awkward workarounds did people use?

The RfC was designed for production support (break/fix) — it didn't fit a requirements flow.

Pre-7.2 there was no best-practice option, only workarounds: upload requirements as a Word document-type to a SOLAR01 project, or copy SMCR and reconfigure. 7.2's Requirements Management introduced two integrated processes (also integrated with ChaRM) to let IT + business plan/scope new functionality before implementation.

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?