The SLD database, which stores the System Landscape Directory (SLD) data, forms the central technological control instance in the SAP Business One system landscape. Consequently, it manages the metadata, configuration information and security settings of all components involved. This database ensures standardised configuration and communication within the entire SAP Business One environment.
Function and content
In particular, the SLD database stores persistent landscape information and security settings. In addition, this database must be protected with the highest priority. The database stores information that is required for the correct functioning of the individual components:
- System-wide addresses: The SLD address must be set during the installation and configuration of all SAP Business One components, such as the client application, the DI API and B1i, should be used consistently. Furthermore, the virtual IP address (VIP) of the SLD should always be used for the installation of all other SAP Business One components.
- Protocols and security: The database stores the configuration of the authentication service. Furthermore, the superuser (Site User, B1SiteUser) is required for authentication at the SLD control centre.
- Component information: The EDS (Electronic Document Service) registers in the SLD on the Services tab.
- Proxy configuration: In addition, the SLD database saves proxy group definitions that are stored in the company database entries in the diProxyhost field.
Administrative and technical relevance
Business users access the SLD control centre via a specific URL in a web browser. The SLD plays a critical role in system administration:
- Database administration: The SLD allows administrators to define a dedicated database user ID for each company database. Once these accounts have been set up, SAP Business One no longer uses the database administrator account, but a read-only account provided by the SLD service for database access.
- Deployment and upgrade: The SLD also enables remote deployment of the system database (SBOCOMMON) and demo databases. Schema upgrades can also be carried out via the SLD.
- Troubleshooting: For example, an incorrect default value for the licence server property (such as "localmachine") in b1-local-machine.xml can cause delays when starting SAP Business One Clients which makes the correct addressing of the SLD essential.
The SLD database thus serves as a central directory that defines the technical landscape and is indispensable for the security and functionality of the entire SAP Business One installation.
In-Memory Databases / The SAP Future ?
Predictive maintenance: how to turn SMEs into smart factories
Versino Financial Suite V09.2025 for SAP Business One
Convert SAP Business One to camt.053 now
SAP Build Apps for SAP Business One
Mobile warehouse 2025 with Versino Warehouse Pro
Preparation for the introduction of CKS.EINVOICE
EUDAMED integration with SAP Business One
Budgets in SAP Business One