Setting Up Landscape Management

To integrate certain products or connect on-premise systems with SAP Cloud ALM, you need to create a service binding from the SAP Cloud ALM API instance.

Depending on the provisioning date of your SAP Cloud ALM tenant, different steps may be needed:

Only if your SAP Cloud ALM Tenant has been provisioned before June 12, 2023, you need to create one manually as described in SAP Help Portal: SAP Cloud ALM, Enabling SAP Cloud ALM API.

Once the service key has been created (automatically or manual), you can access it on the SAP BTP Cockpit of the SAP Cloud ALM Subaccount and, if applicable, on the SAP Cloud ALM Landscape Management App:

To view the service key in the Subaccount of the SAP Cloud ALM:

1. Open the SAP BTP cockpit.
2. Select the global account that contains your SAP Cloud ALM entitlement, and then open the Subaccount that contains your SAP Cloud ALM subscription.
3. Choose Services → Instances, and Subscriptions.
4. Under Instances, find the instance that contains your service key or service binding.

From here, you could view or download the service key.

To access the service key in the SAP Cloud ALM Landscape Management, perform the following steps:

1. Opening the configuration by choosing the gear icon.
2. Expanding the section SAP Cloud ALM Service Key. If no service key is available, you can upload it; if a service key is available, you can view, download, or delete it. In our case, we want to verify the existing service key.
3. If you confirm the Success Message, the Status changes to green.

Depending on the scenario, you might need the information stored in the service key. The following screenshot shows an example and the most important fields and what they are used for:

Services and systems must be set up in the Landscape Management app in SAP Cloud ALM as the final step of the required setup.

Landscape management in SAP Cloud ALM helps you manage information about your services, systems, and business services. This information serves as the basis for all SAP Cloud ALM applications.

The next slide shows the Landscape Management App:

Services

In SAP Cloud ALM, services are understood as subscribed cloud services, that is, solutions and applications that are offered on-demand from the servers of a cloud provider (SaaS).

Systems

are defined as on-premise systems, that is, solutions and applications provided by SAP but installed and run on the premises of the company or organization using them, or in a private cloud solution.

Business Service

Is a logical construct that represents a business capability or application your users rely on. It groups services and/or systems, allowing you to model and monitor business-facing capabilities (for example, Order-to-Cash or Payroll) as end-to-end services.

The most important buttons are the Select a Scope button, which looks like a dartboard, and the Configuration button, which looks like a gear.

You have full control over which data from managed services and systems is transferred to SAP Cloud ALM:  When you activate your SAP Cloud ALM tenant and register your systems and services in the Landscape Management app of SAP Cloud ALM, the collection of observability data is not started automatically. SAP Cloud ALM follows a central configuration approach; therefore, you must explicitly configure the data collection processes.

​Before we discuss how to connect services and systems, we want to talk about the so-called SAP Corporate Group (CCC) S-User Section.

If you have services assigned to a different customer number (for example, as a global ultimate customer) and want to use one SAP Cloud ALM tenant to monitor other customer numbers in the customer hierarchy, you need to enter an S-user with the authorizations to access the system data for all subsidiary customer accounts to ensure that the Landscape Management app has access to the data.

To be able to access the required system data, the S-user must be one of the following:

• A technical S-user that was created on top of the group hierarchy (for the main or parent account). By default, these technical S-users can see all subsidiary customer numbers of the corporate group.
• A standard S-user in the corporate group. You can manage the authorizations of standard S-users yourself and according to your requirements, which gives you more control over which customer numbers they can access.

To add the S-user, open the Landscape Management app and choose Configuration. Under Import of Subscribed SAP Services, choose + (Add S-User) and enter the credentials of the S-user.

You can verify that the username and password are correct and that the S-user has access to the customer number of the SAP Cloud ALM tenant by performing the S-User Logon Check.

The customer numbers you have access to will then be stored in the Imported Customer Numbers section. Please note that initially, the customer name may be missing in this table. If the customer is available in the cloud landscape directory, the name will be added with the next daily sync.

It's the customer's decision whether to use this functionality. Optionally, you could also provision a separate SAP Cloud ALM Tenant for each customer. Or group customer.

The import method of services in SAP Cloud ALM depends on the service type of your solution. We can distinguish between 3 different use cases.

Most service types are imported into SAP Cloud ALM automatically if they are assigned to the same customer number as your SAP Cloud ALM tenant. This import is done daily by the System Landscape Information service (internal SAP name SLIS).

To display the current status in the Landscape Management app, open the Configuration, expand the section Import of Subscribed SAP Services, and click on the first icon after Status of imports.

If required, you can also initiate an import on demand by selecting Import My Subscribed SAP Services. This is usually only necessary if recommended by SAP.

Other service types (such as SAP SuccessFactors and SAP S/4HANA Cloud) are push-enabled services that register themselves in SAP Cloud ALM. These services are created automatically in the Landscape Management app as part of the communication arrangement or registration (The single steps are provided in the slide):

For more information, consult the SAP Cloud ALM for Operations Expert Portal, SAP S/4HANA Cloud Public Edition, or the SAP Course ADM001, Unit Summarizing Monitoring options

Another method is registration using an ABAP report. Once a technical system has been registered, a default logical system (client) is created and displayed in the System Details. For example, using the /n/SDF/ALM_SETUP transaction for SAP S/4HANA and SAP Business Suite 7. For more details, check SAP Cloud ALM for Operations Expert Portal, Setup for SAP S/4HANA and SAP Business Suite 7.

Only some service types (for example, Unspecific Cloud Service (HTTP) or Managed Gateway for Spend&Network) must be added to the Landscape Management app manually.

Also, some system types (for example, SAP Focused Run and Cloud Connector) can't be registered but need to be set up manually.

For step-by-step guidance on the manual creation (if required), find your system in the SAP Cloud ALM for Operations Expert Portal – Setup Managed Components at the end of this lesson.

You may have already seen the video on the SAP Help Portal. If not, please take a look:

This and additional videos can be found on SAP Help Portal – Video-Guided Setup.

If  you face problems you cannot solve, please consult the Troubleshooting for Landscape Management page.