Maintain and Support Your SaaS solution
Overview of tools to maintain the landscape and support consumers of the SaaS solution
Overview
You will learn
- About the available tools to support, maintain and operate the SaaS solution
Prerequisites
Prerequisites
- You are subscribed to the Landscape Portal
- You have a user with the Landscape Portal Admin role collection assigned
Steps
You can update your solution with patches, support packages, or new releases. Create a new branch from the main branch in test system TST in your 01 Develop subaccount for every support package or new release. For minor changes, continue developing in the respective active maintenance branch.
Patch versions are used to deliver unplanned and urgent corrections that are required to keep the application up and running.
Import maintenance branch v1.0.0 in ABAP correction system COR. This could be another system in the 01 Develop subaccount.
Implement the bug fix in the ABAP correction system.
Import maintenance branch v1.0.0 in ABAP quality assurance system QAS. This could be another system in the 02 Test subaccount.
Test the bugfix in ABAP quality assurance system QAS.
Maintain the corrections that have been developed and tested in ABAP correction system COR and quality assurance system QAS in the development system DEV (so called double-maintenance). For more details on the process, see Double Maintenance of Corrections into Development
Use the Build Product Version app of the landscape portal as described in previous tutorials of this mission to build a new patch version.
Support package versions are used to deliver planned functional enhancements outside of new major releases. They are often used to bundle multiple patch versions.
Implement the new feature in the main branch in ABAP development system DEV.
Make sure the main branch is imported in ABAP test system TST.
Test new feature in ABAP test system TST.
In the Manage Software Components app, create a new maintenance branch v1.1.0 (for a support package).
Use the Build Product Version app of the landscape portal as described in previous tutorials of this mission to build a new support package version.
Release versions are used to deliver new major, planned functional enhancements. Typically, they include multiple new implemented features. For example, multiple new apps could be introduced with such a major release.
Implement the new feature in the main branch in ABAP development system DEV.
Make sure the main branch is imported in ABAP test system TST.
Test new feature in ABAP test system TST.
In the Manage Software Components app, create a new maintenance branch v2.0.0 (for a release version) that is based on the main branch.
Use the Build Product Version app of the landscape portal as described in previous tutorials of this mission to build a new release version.
Navigate to the Landscape Portal as a Landscape Portal Admin.
Open the “Update Product Version” app
On the right side of the screen, you can see the Planning Calendar. The planning calendar gives an overview of planned and unplanned downtimes of service-relevant infrastructure as well as already scheduled product version updates. You can use the calendar to help you find a fitting time slot for your product version update so as to make sure that it doesn’t conflict with other downtimes
On the left side, under Product and Product Version Selection, select which product and version you want to update from the drop-down menu.
The product version can only be updated to a higher version. It is not possible to update the product version to a lower version
In the Available Systems section, select at least one system in which you want to update the product version. You can also select multiple systems at once

Update Product Version Click the Update button. Fill in the required details in the dialog
Click Schedule

Navigate to the “Systems Overview” app in the Landscape Portal
Click on the entry for the system that was created for your SaaS application You could identify it from the system description “ABAP Solution System for
appname” or via the SID. If asap_system_namewas defined in the configuration of the ABAP solution, systems are provisioned with same SID. If nosap_system_namewas defined, systems are provisioned with SID = AST or SID = AMT, depending on whether the solution was created withtenant_mode= single ortenant_mode= multi.Once the update scheduled in the previous step is complete, the “Software” section should reflect the new product version for the add-on

System Overview Under the “Requests” section, you could monitor the update process
To monitor operations processes like add-on update or tenant provisioning in your system landscape
- Open the “Operations Dashboard” app of the Landscape Portal as a Landscape Portal Admin
- Use the dropdown to select the system(s) for which you want to monitor operations.
- The Requests section displays a list of all requests triggered for your systems as well as their current status.
- In the Active Requests section, you can view all active processes, their request IDs, execution date, systems, and their progress bars

When a quarterly platform upgrade of the ABAP Environment is planned for your systems, the “Register Systems for Pre-Upgrade” app of the Landscape Portal allows you to select specific test or development systems for an early upgrade. These systems will be upgraded two weeks before the official roll-out, giving you ample time to test your solution as a provider prior to the actual upgrade.
Only pre-upgrade dedicated test systems. Pre-upgrading development systems or systems used for add-on build could result in issues with minimum platform version determined for add-on product versions.
Select the system that you want to register for a pre-upgrade.
Click the “Register System” button.
Refresh the page by clicking on the Refresh button. The status of your system has changed from “Not registered for pre-upgrade” to “Registered for pre-upgrade”.
If you change your mind and want to undo the registration of a system for pre-upgrade, simply select the system and click the “Un-Register System” button.

Log in to the Landscape Portal and open the “Systems Overview” app.
Select the system that contains the tenant for which you would like to create a support user.
Navigate to the tenant for which you would like to create a support user.
Click on the “Request Support User” button in the upper right corner of the page.
Once the user creation is done, you can log on to the Fiori Launchpad of the tenant via the link in the tenants overview.
You need to subscribe to the service “Web Access for ABAP” on the BTP cockpit in order to gain access

[OPTION BEGIN [Support via ABAP Development Tools for Eclipse]]
To logon to ABAP Development Tools and provide support, we broadly perform the following activities:
- Retrieve the service key for the targeted ABAP System.
- Retrieve the tenant GUID of the targeted ABAP tenant.
- Create a tenant-specific service key.
- Use the created service key to login to the target tenant using an ABAP Cloud Project in ABAP Development Tools.
Retrieve the service key for the targeted ABAP System:
Navigate to the provider account’s service instances.
Select the ABAP service instance.
Open and copy the SAP_ASP service key.

Retrieve the tenant GUID of the targeted ABAP tenant:
Sign in to the Landscape Portal.
Copy the link of the client column of the target tenant.
Extract the tenant GUID from the URL.
Create a tenant-specific service key-To do this, replace the GUID in the URL field of the service key from the “Retrieve the service key for the targeted ABAP System” step with the tenant GUID.
Use the created service key to login to the target tenant using an ABAP Cloud Project in ABAP Development Tools.
[OPTION END]
Resources
Discussion
Share feedback on this tutorial or join the conversation in SAP Community.