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

What role does the System Landscape Directory (SLD) play in an SAP landscape?

It's the landscape's phone book — holding installed software components, clients, hosts, databases, and more.

Correctly configured systems periodically report their version and installation information to it.

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's the trade-off between having SolMan read a central/remote SLD versus using an SLD bridge?

When deciding where to run the SLD, what makes putting it on SolMan's own Java stack the preferred choice — and when is the decision trivial?