SAP Solution Manager 7.2 · Requirements Management

What's the final acceptance sequence in Requirements Management?

After the IT requirement is approved:

  1. Business manager sets the business requirement → accepted.
  2. Solution architect sets the IT requirement → implemented.
  3. This triggers delivery to the dev team → a change document generates (visible in the Related Transactions assignment block).

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?
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?
What's the business requirement flow from definition to final commit?