SAP Solution Manager 7.2 · Landscape Data: SLD, LMDB & Maintenance Planner

How does the LMDB in Solution Manager relate to the SLD, and what does the LMDB require from the SLD?

The LMDB (Landscape Management Database) in Solution Manager synchronizes its landscape data from the SLD (System Landscape Directory) — SolMan depends on both and neither can fulfill its role alone. The LMDB requires that specific CR (Component Repository) content be present and up to date in the SLD to correctly resolve patch levels and component versions.

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 Landscape Data: SLD, LMDB & Maintenance Planner

How does each type of system register with the SLD?
How often should SLD content be updated, and what's notable about applying an update?
What replaced the Maintenance Optimizer, and when are customers required to use it?
What is the key output of the Maintenance Planner, and what tool consumes it to execute the planned upgrade?
What role does the System Landscape Directory (SLD) play in an SAP landscape?
What's the trade-off between having SolMan read a central/remote SLD versus using an SLD bridge?