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?

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?

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?

You're building a document status schema with a signature strategy. Which status must be Locked, which one can NEVER be Locked, and what extra step does remote storage add?

Teams coming from SolMan 7.1 still build three-level BPM hierarchies and separate to-be projects in 7.2. What did 7.2 drop, and which single change most reduces business-doc drift?

SolMan document storage for external content is client-specific. Can you therefore point different clients at different remote storage systems?

After upgrading SolMan 7.1 to SP03 you rebuild embedded search and results are broken/duplicated. What upgrade-specific step is easy to miss, and what are the standing prerequisites?

An admin can open Solution Documentation (SOLDOC) but is blocked from Solution Administration (SOLADM/SLAN). Which authorization object are they missing, and what extra field does it require that SM_SDOC doesn't?