Integrating SAP LeanIX
You can integrate SAP LeanIX with SAP Cloud ALM to support landscape management, as well as project and task management.
Gain comprehensive and consistent transparency by discovering your SAP landscape through SAP Cloud ALM.
Set up SAP Cloud ALM and connect your SAP LeanIX workspace to SAP Cloud ALM via API, as described in the following slide:
For more information, please consult the SAP Help Portal, Integrating SAP Lean IX.
Integrating SAP Central Business Configuration
While an SAP Cloud ALM project applies the SAP Activate methodology to provide end-to-end procedural guidance on how to start and run an implementation project, an SAP Central Business Configuration workspace shows the activities focused on your specific business configuration.
SAP Central Business Configuration is a solution that supports the configuration of SAP S/4HANA Cloud Public Edition:
By integrating SAP Central Business Configuration with SAP Cloud ALM, you can import roadmap content into the Tasks app. This helps you understand the order in which the tasks need to be carried out, and lets you navigate directly to SAP Central Business Configuration as needed:
Caution
SAP S/4HANA Cloud Private Edition is not supported.
Find all necessary steps described in Integrating SAP Central Business Configuration.
Enabling Transport Management
Learn how to enable the transport management of different transport environments for SAP Cloud ALM.
The following different transport environments in SAP Cloud ALM are available:
- SAP S/4HANA Cloud Public Edition, by enabling the transport management with Adaptation Transport Organizer (ATO).
- SAP S/4HANA Cloud Private Edition using Change and Transport System (CTS)
- On-Premise Systems using Change and Transport System (CTS)
- SAP SaaS components using SAP Cloud Transport Management Service
Note
For a complete list, please always checkSAP Help Portal – SAP Cloud Transport Management.
SAP S/4HANA Cloud Public Edition
By enabling the transport management for SAP S/4HANA Cloud Public Edition with the Adaptation Transport Organizer (ATO), you can keep track of the deployment of transport requests through your implementation landscape:
Limitations
- Only released transports can be assigned to features
- Only transports exported after you established the connection of your SAP S/4HANA Cloud development and customizing system to SAP Cloud ALM are pushed to SAP Cloud ALM. Currently, there is no historic data available.
- If you have multiple SAP Cloud ALM tenants, you should only connect your SAP S/4HANA Cloud Public Edition tenants to your productive SAP Cloud ALM tenant.
The following list contains the outbound services that are currently available:
- Export: This outbound scenario reacts to exported ATO collection versions
- Import: This service notifies SAP Cloud ALM about imports that were performed by ATO
- Retry: Retries failed communication between ATO and SAP Cloud ALM
- Status Change: This service reacts to ATO status changes and sends these changes to SAP Cloud ALM
Note
The collector jobs can only react to future events once they are activated. Past actions before the activation are not collected.
Please find a detailed configuration description in SAP Help Portal – SAP S/4HANA Cloud Public Edition.
SAP S/4HANA Cloud Private Edition and On-Premise Systems
When you enable the transport management for SAP S/4HANA Cloud Private Edition and SAP NetWeaver Application Server for ABAP on-premise, you can orchestrate the deployment of transport requests through your implementation landscape.
SAP NetWeaver Application Server for ABAP (7.40 or higher) can be an SAP S/4HANA on-premise system, an SAP S/4HANA Cloud Private Edition, and an ECC system, where SAP Cloud ALM integrates with the Change and Transport System (CTS).
To use the Change and Transport System (CTS) for SAP S/4HANA Cloud Private Edition and SAP NetWeaver Application Server for ABAP on-premise in an SAP Cloud ALM environment, you have to establish a connection between SAP Cloud ALM and the CTS.
Note
By setting up the integration, you push Transport-related data to SAP Cloud ALM from your managed systems. This includes the transport owner's data. For more information, see SAP Note 3429058.
- Currently, any consistent Transport Management System (TMS) landscape is supported. The last system in a track is always treated as a production system.
- It's mandatory to set CTC=1 to enable the Export Transport Control for imports into different systems and clients other than the export system and client.
- TMS transport groups are supported.
- CTS+ is not supported.
The following steps show you how to create a test landscape to try out the SAP Cloud ALM Deployment Management scenario without interfering with the productive TMS landscapes. You can also follow the steps to create your productive landscape. For this, you just have to use your systems instead of the described test systems:
Please find all configuration steps on the following page, and please always check the limitations (Caution section) on this page: SAP Help Portal SAP S/4HANA Cloud Private Edition and On-Premise Systems.
SAP Cloud Transport Management Service
Several SAP Cloud Products use SAP Cloud Transport Management as an environment for transporting their development artifacts and application-specific content. The transport nodes of SAP Cloud Transport Management represent the landscape of those SAP Cloud Products. Connecting SAP Cloud Transport Management to SAP Cloud ALM makes that landscape and the respective transports visible for SAP Cloud ALM. Then, you can orchestrate the deployment of those transports in SAP Cloud ALM:
You can directly connect an SAP Cloud Transport Management service instance subscribed in your SAP BTP Global Account to SAP Cloud ALM.
Note
- We recommend running the SAP Cloud Transport Management service as a shared service, setting it up on a central administrative subaccount, to facilitate role management and allow strict access control.
- In case you've subscribed to several SAP Cloud Transport Management service instances, it's possible to connect all of them to the same SAP Cloud ALM.
- SAP Cloud ALM supports the parallel delivery of several transport nodes at once.
- Currently, deleted Cloud Transport Management transports can't be removed from the Features app. However, you can unassign deleted transports from features
Please find all configuration steps and prerequisites on the following page: SAP Help Portal – SAP Cloud Transport Management Service.
Integrating Test Automation Providers
In addition to manual testing, which is performed directly in SAP Cloud ALM, you can also integrate SAP and third-party test automation providers that have implemented our public Test Automation API.
By integrating automation providers with SAP Cloud ALM, you can reduce your manual testing efforts and take advantage of its test orchestration, execution monitoring, and reporting capabilities:
SAP Cloud ALM currently supports the integration with the following automation providers. For the configuration procedure, use the link on the Provider's Name:
- Test automation tool for SAP S/4HANA Cloud Public Edition: Conduct testing of all solution processes from the solution scenario SAP Best Practices for SAP S/4HANA Cloud Public Edition.
- SAP Test Automation by Tricentis for SAP: integrated with SAP Cloud ALM: Conduct testing of all browser-based SAP solutions and applications.
- Other Test Automation Providers: Conduct testing with other external test automation providers.
Note
The third-party vendor is responsible for ensuring the correct implementation of the Test Automation API and should be contacted in case of errors or for support
Related Information
Integrating the Cloud Integration Automation service (CIAS)
The Cloud Integration Automation service (CIAS) provides a guided workflow for integrating SAP cloud solutions with on-premise and other SAP cloud solutions. The workflow contains instructions for manual and automated tasks to enable easy and quick integration and configuration setup:
For additional information about CIAS and a detailed configuring description please consult:
Connecting SAP Document Management Service
You can integrate and activate the SAP Document Management service for document storage in SAP Cloud ALM.
Its possible to to upload External Files in the Documents app of SAP Cloud ALM.:
First establish a connection between your SAP Document Management service (SAP BTP DMS) and your SAP Cloud ALM tenant:
Note
Make sure you have entitlements for both the SAP Document Management Service, Repository Option, and the SAP Document Management Service, Integration Option.
SAP Help Portal - SAP Document Management Service
Repository Handling
During the initial communication between SAP Cloud ALM and the SAP Document Management service, the Documents app automatically creates a new repository in the SAP Document Management service.
Caution
Do not change this repository or any other repositories created by the Documents app. As previously stated, the choice of a repository is irreversible. You can lose your documents if you decide to change the repository at a later point in time. The property external ID of a repository is always identical with the tenant ID of the tenant that created it. With this information, the user can always trace which repository belongs to which tenant. Changes done in the repository directly aren't reflected in SAP Cloud ALM and they disrupt the integration.
The repository has the following characteristics, which you can't change:
- External ID: SAP Cloud ALM tenant UUID (unique): The external ID is always identical to the tenant ID of the tenant that created it. With this information, you can always trace which repository belongs to which tenant.
- Name: SAP Cloud ALM for Implementation
- Description: Internal Repository for SAP Cloud ALM for Implementation
- Encryption: enabled
- Virus scan: enabled
- Versioning: enabled
- Thumbnail: disabled (not possible with enabled encryption)
Files in this repository are automatically managed as follows:
- All files are stored in the ROOT folder. No new folders are created.
- For the file name (cmis:name), a UUID from the SAP database table is used.
- The cmis:name only contains a technical ID. The real file name is stored in the property cmis:contentStreamFileName.
- SAP Cloud ALM doesn't replicate any additional metadata, for example, the extension field sap:owner and other extension fields aren't filled.
- With every upload of an external file, SAP Cloud ALM creates a new major version in SAP BTP DMS: 1.0, 2.0, … X.0. No minor versions are created.
- The maximum size for files to upload is 120 MB.
- Which file types are supported, you can see in External Files.
Disabling the External File Feature
There's no process to discontinue the external file feature in the Documents app.
If you no longer want to use the feature, you need to manually delete the external files in the Documents app.
After that, you can delete the SAP BTP DMS repository and disconnect the configured destination.
Read Configuration, Caution and Prerequisites on this page: Connecting SAP Document Management Service.