SAP Solution Manager 7.2 · Content Activation (7.1→7.2)

When modeling for content activation, should you create one logical group per logical component or per application landscape? What single property decides — and why does the intuitive choice backfire?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Content Activation (7.1→7.2)

Your team realizes mid-way through the 7.2 content activation wizard that the activation mapping is wrong. Past which step is it too late to change in place, and what single safeguard lets you recover regardless?

You're scheduling the two content-activation processes around the 7.1→7.2 upgrade. One must run before the upgrade; if you defer it, the damage is unrecoverable, not just inconvenient. Which one, and why is the window one-way?

Your BPMon/Analytics objects are still in the legacy (non-MAI) format when you reach content activation. What happens to them, and what's the non-obvious reason it's not just a cosmetic gap?

How many solutions should you create during activation modeling — one, or one per business-process area? When is the exception legitimate, and what gate guards it?

The actual 7.2 content activation is a three-step guided process. List the three steps in order, and the prerequisites that must already be complete before step 1.

Three core concepts were completely redesigned in Solution Manager 7.2, and modeling on the old mental picture corrupts your activation. Which three — and what's the concrete failure if you carry over the pre-7.2 model?

Start learning today

Free to start — download the app or use it in your browser.