SAP Solution Manager 7.2 · Solution Documentation: Architecture & Config

SAP presets three template users for Solution Documentation — Display-only, Execution, and Admin. A project/change manager must edit process-doc settings, the roadmap, system-landscape info AND create incidents. Which template fits, and why not Display-only or Execution?

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 Solution Documentation: Architecture & Config

Governance reporting needs a field that the standard Solution Documentation element types don't capture. What do you configure, and what scoping choice does the guided process force on you?

You want object A maintainable by both the FI team's authorization group and the SD team's group in Solution Documentation. Why can't you just add it to both groups?

A stakeholder wants a sensitive attribute hidden from users who shouldn't see it. Can attribute-level authorization in Solution Documentation deliver that?

You configured a signature strategy for Solution Documentation documents but signing fails. What infrastructure precondition is most likely missing?

You schedule the Library Generation Cockpit job to pull actually-used transactions/programs into a solution's library, but it returns little or nothing. What setup step is commonly skipped, and how long should the capture run?

An element protected by an authorization area gets moved to a different branch of the solution structure. Does it keep its original area, and why does that matter?

Start learning today

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