Landscape Data: SLD, LMDB & Maintenance Planner

A colleague wants to transport an SLD content update from DEV to PROD so all systems stay in sync — what's wrong with that plan?

You're tempted to manually edit Software in the LMDB to fix wrong data — why is that usually the wrong move?

How does each system type register with the SLD (ABAP, Java, HANA, Web Dispatcher)?

Your Basis team hits a wall calculating the software needed for an upgrade in the Maintenance Planner — where do you look first?

A team plans to define upgrade components using the in-system Maintenance Optimizer — why won't that work, and what must they use instead?

The LMDB is syncing fine from the SLD, yet patch levels and component versions still resolve incorrectly — what's the missing precondition in the SLD?

A newly built system is missing from the SLD. A teammate says "just add it to the SLD by hand." Why is that the wrong fix?

After planning an upgrade in the Maintenance Planner, what concrete artifact do you hand to SUM — and why does that artifact matter?

Your SLD doesn't recognize a freshly installed S/4HANA 1709 — what's the cause, and what fixes it?

Should SolMan read a central/remote SLD directly, or run its own SLD via a bridge — what does the choice actually trade?

On SolMan 7.2 you go to maintain a product system in the LMDB like you did before — why is that no longer where it belongs?

You need to decide where SolMan's SLD runs — what makes its own Java stack the preferred home, and when is the call trivial?

A teammate says one tool's wrong landscape info is a local glitch in that tool — why is that the wrong mental model, and what does it change about the fix?

SolMan is down for maintenance — why do landscape updates from systems keep flowing, and do you have to replay anything afterward?