sap-gui-landscapelisted

# SAP GUI Landscape & Connection Configuration Two halves of one job: **SLMT** maintains the landscape centrally in the ABAP system, and the resulting **SAP UI Landscape XML** is what every SAP GUI client reads to know which systems exist and how to reach them. The connection strings and SNC settings live *inside* that XML — so a malformed connection string and a mis-distributed landscape file present identically to the user ("I can't see/reach the system"). > **Guardrail — this is user-facing configuration for a whole landscape.** > - **A bad central file breaks every user at once.** Validate against the XSD (**SAP Note 2112449**) > before distributing, and keep the previous version to roll back to. [G, VAL] > - **Never put a router password in a file you distribute.** `/P/<password>` in a connection string is > readable by anyone who can read the XML. Prefer SNC, or `/W/` (prompted) — see §3. > - **Renaming the "Local" workspace is mandatory** when building a server file. Skipping it collides with > users' local configuration. [G, DIST] > - Changing `LandscapeFileOnServer` is a **registry change on every workstation** — treat it as a > client-side rollout, not an SAP change. Verification legend: **[V]** verified against the live source during authoring · **[G]** cited to an SAP Note or guide. --- ## 1. SLMT — the central maintenance tool **Transaction `SLMT`**, or report **`RSLSMT`**. It lets an administrator *"centrally create, display, and edit SAP UI Landsc