SAP Solution Manager 7.2 · Solution Documentation: Architecture & Config

What does 'Generate Library' do in Solution Documentation, and what does it distinguish between?

In SOLADM/SLAN's Library Generation Cockpit you schedule a job to pull the transactions/executable programs actually used in the managed production system into a solution's library.

It distinguishes standard entities (programs + transactions → Executable Library) from custom entities (classes/objects → Development Library). Pulls via the SAP BW interface (RFC as fallback); prereqs: error-free basic + managed system config and the BW extractor activated in the Custom Code Management scenario. Capture at least 3 months; can schedule periodically.

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

How can you extend Solution Documentation for better governance reporting?
How do digital signatures work for Solution Documentation documents, and what must be active first?
What does an authorization group control in Solution Documentation, and what are its rules?
Attribute-level authorization in Solution Documentation only checks one action — which, and what can't you do with it?
What three template users does SAP preset for Solution Documentation, and what can the admin one do?
What does an authorization area protect, and how is its assignment determined?