SAP Solution Manager 7.2 · Solution Documentation: Libraries & Process Model

What does the Executable Library hold, and how is it organized?

A structured set of directly callable executable objects (t-codes, Fiori apps) — no duplicates, each recorded once, with technical specs added (design shared).

Organized first by logical component group, then by the software's internal structure (SAP uses the application-component hierarchy SD/FI/HCM). The library-generation tool can build it automatically from actual ABAP production usage.

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: Libraries & Process Model

What is a composite interface, and what does it describe?
What is the Business Processes area, and what's the guidance on end-to-end versus modular flows?
What is the Alerting Library for, and why build alert objects in the Business Process area rather than in the library?
How is a modular process scoped and structured?
What does the Development Library hold, and how does its content differ from the Executable Library?
What does the Configuration Library centralize, and what's the best-practice folder structure?