A centralized and modular SAP Logon landscape management solution designed for multi-customer SAP environments.
The project allows SAP administrators to maintain one SAP GUI landscape file per customer while automatically generating a consolidated SAPUILandscapeGlobal.xml for distribution to all users.
- Modular architecture based on one XML landscape file per client.
- Automatic generation of a consolidated SAP Logon landscape.
- Centralized deployment through a shared network repository.
- Support for more than 100 customer landscapes.
- Automatic UUID management and validation.
- SAP system classification (S/4HANA, ECC, BW, Solution Manager, etc.).
- Excel-based system inventory and reconciliation.
- Automatic backup of previous configurations before deployment.
- Consistency checks between XML sources and Excel mapping.
- Search utilities for clients and SAP systems.
- Fully automated deployment through PowerShell scripts.
SAPUILandscape_sorgenti/
├── CustomerA/
├── CustomerB/
├── ...
└── _AVVALE_INTERNAL/
SAPUILandscape_globale/
└── SAPUILandscapeGlobal.xml
mappa_uuid_sistemi.xlsx
SAPUILandscape_sorgenti
Contains the modular source landscapes. Each customer is maintained independently through its own XML file. This is the only area that should be edited manually.
SAPUILandscape_globale
Contains the generated SAP Logon landscape used by end users. The content is automatically rebuilt from the source repository during deployment.
Extract the package into a network location accessible to all SAP users. Example:
\\fileserver\SAPLandscape
Users should have read access while administrators should have update permissions.
For a new installation, rename:
mappa_uuid_sistemi_example.xlsx
to:
mappa_uuid_sistemi.xlsx
and populate it with the required SAP systems.
Before deploying, regenerate the modular XML sources from the Excel mapping. Run:
Rebuild-SourcesFromMapping-Sostituisci.cmd
This rebuilds SAPUILandscape_sorgenti from mappa_uuid_sistemi.xlsx and, if the validation checks pass (no XML errors, no UUID collisions), automatically replaces the active sources (keeping a timestamped backup of the previous version).
Run:
Deploy-SAPLandscape.cmd
The deployment process:
- Rebuilds the global SAP landscape.
- Creates a backup of the current user configuration.
- Updates local SAP GUI landscape files.
- Deploys the centralized configuration.
SAP GUI must be configured to use the generated global landscape. This can be done either:
-
Automatically using:
Set-SAPLogonServerConfig.cmd -
Or manually in:
SAP Logon → Options → Configuration Files → XML Configuration File on Serverpointing to:
\\fileserver\SAPLandscape\SAPUILandscape_globale\SAPUILandscapeGlobal.xml
Open SAP Logon and confirm that the AVVALE Clients folder and all expected systems are visible.
Edit mappa_uuid_sistemi.xlsx
↓
Rebuild-SourcesFromMapping-Sostituisci
↓
Build-SAPGlobal
↓
Validate
↓
Deploy-SAPLandscape
↓
SAP Logon Refresh
| Utility | Purpose |
|---|---|
Deploy-SAPLandscape |
Build and deploy the landscape |
Set-SAPLogonServerConfig |
Configure SAP GUI integration |
New-SAPClient |
Create a new customer landscape |
Build-SAPGlobal |
Generate the global XML |
Find-SAPClient |
Search customers and systems |
Export-MappingFromSources |
Generate Excel inventory from XML |
Rebuild-SourcesFromMapping |
Generate XML from Excel inventory |
Compare-GlobalWithMapping |
Verify consistency between active landscape and inventory |
Restore-SAPLandscape |
Restore a previous local backup |
Maintain customer systems exclusively within SAPUILandscape_sorgenti, validate changes with Build-SAPGlobal, and distribute updates using Deploy-SAPLandscape. This guarantees that all SAP users consume a consistent, centrally managed SAP Logon landscape.