The following steps are all described in detail in the chapter Required Set up for SAP Cloud ALM  in the "Set up and Administration Guide" which you find in the Help Portal.

Be advised that SAP Cloud ALM requires a productive IAS tenant since it also supports the Operation of solutions and here we need to use the productive environment.

The Set Up of landscape management is not necessary at this point, but required once you start testing and deploying.

The following overview describes the required users you need to access SAP Cloud ALM:

 

Setup Central Business Configuration (CBC) Integration

The steps to set up the integration to SAP Central Business Configuration (CBC) are described in the Help Portal here.

What is SAP Central Business Configuration

SAP Central Business Configuration is a new solution that will make it possible to configure business processes that span across different SAP products from one central place. SAP Central Business Configuration will first allow the configuration of SAP S/4HANA Cloud, essentials edition.

You can start with an overview or read this blog post to know more.

 

Integrating SAP Central Business Configuration with SAP Cloud ALM

You can connect SAP Cloud ALM with SAP Central Business Configuration by following this setup guide.

Note: To perform the setup you need certain OAuth2Client credentials in step 6. You will need to create a ticket for component X4-CBC-SRV. We recommend the following title and description.

Title: OAuth2Client Credentials for Integration with SAP Cloud ALM

Description: We would like to integrate SAP Cloud ALM with SAP Central Business Configuration. Please set up and send us the required OAuth2Client credentials.

What happens after the setup

After you perform the setup, you see an option to select Integration scenario in your Project Setup in SAP Cloud ALM

 

 

After selecting this option you can find the Projects for the Starter or the Implementation system and choose the appropriate Project

On saving the Project you can navigate to SAP Central Business Project from SAP Cloud ALM Project.

You can navigate via the Project header or via the task navigation.

How SAP Cloud ALM Project is different from SAP Central Business Project

SAP Cloud ALM Project focuses on End to End Implementation experience powered by SAP Activate methodology. SAP Central Business Configuration Project shows the Project activities and configuration activities focused on customer's Business Configuration.

What is the benefit of this Integration

SAP Activate methodology offers customers end to end guidance on how to start and execute a Project e.g. an SAP S/4HANA Cloud Project. When this methodology is loaded into SAP Cloud ALM, it offers a structured guidance on when to use which system in the correct sequence.

After you perform this setup, you can use SAP Cloud ALM as the guidance system. You can understand the order in which the tasks need to be executed and seamlessly navigate to SAP Central Business Configuration when needed.

 

What is planned for future

SAP wants the customer to have a seamless experience using SAP products. So we will strive to continuously improve this integration in future. Stay tuned to know more.

Lets start a dialogue, feel free to leave a comment or give feedback.

You can visit the blog post below that is one central place for Project and Task management in SAP Cloud ALM.

Integrating the Test Automation Tool for SAP S/4HANA Cloud

How do I set up the “Test Automation Tool” in SAP S/4HANA Cloud?

SAP S/4HANA Cloud provides a test tool that can help customers automate their testing during various phases of the projects and also during quarterly upgrade. This blog will help you understand the steps to be followed for set-up of the test tool.

The test automation tool is available only in customer's quality systems (Q systems).You can start using test automation tool from the realize phase as soon as you are provisioned with the “Q” system.

Recommendation is to use the test automation tool starting from the realize phase. This helps customers to automate the regression testing phase after quarterly upgrade in run phase.

To use the test automation tool, you need access to test automation tool apps which are “Test Your Process”, “Manage Your Test Process” and “Analyze Automated Test Results”. The apps “Test Your Process”, “Manage Your Test Process” are accessible via role “SAP_BR_BPC_EXPERT” or “SAP_BR_ADMIN_TEST_AUTOMATION”. The app “Analyze Automated Test Results” is only accessible via role “SAP_BR_ADMIN_TEST_AUTOMATION”. The recommended browser is Chrome.

SAP_BR_BPC_EXPERT – Access to test automation tool app:

SAP_BR_ADMIN_TEST_AUTOMATION – Access to test automation tool apps

 

To use the test automation tool, you need to first set up the test tool via app “test your process”. You need to add a test user to the manage user section of the app. Open the app test your process and click on the manage user icon appearing at the footer of the screen.

The initial landing page would be empty as no user has been set up. Then click on the add button to add the test user.

 

This will open a pop-up window displaying the fields Role, Description, User Name and Password. Let's see details of each field.

 

Role:

The first entry should be with “DEFAULT”. This is mandatory for the test tool to execute. The role here does not mean you need to create a role name called DEFAULT. This role is only linked with standard automate for test execution purpose. To execute the standard automates this entry needs to exist. To do a role based testing you can create more roles and add user. The same role name should be added to the standard automate for test execution.

Description:

You can define the purpose of this role like test user or test administrator.

User Name:

 

The user name here needs to be an active business user with which user can log into SAP S/4HANA Cloud using the same user name. This field is a search help to select the users available in the system. Ensure the test users exist in identity provider.The maintenance of test user is mandatory for the test tool execution.

The recommendation is to create a generic test user specifically for the testing purpose with all the application specific role because if this user does not have roles then the test plans would fail due to no authorization to access the apps.

Currently test automation tool is supporting SAP Cloud Identity and Microsoft ADFS (Supports only basic authentication with login credentials on the one screen).Please note only single factor authentication is supported for the test automation tool to work. The single factor authentication is in which the user provides only one factor – typically a password. The test automation tool does not support a two-factor authentication methods which rely on users providing a password as well as a second factor, usually either a security token.

Any other IDP configurations can be evaluated for technical feasibility, please raise a request via mail to saps4hanacloudtesttool@sap.com.

In some customer IdP´s 2 factor-authentication is being used. Test automation tool currently does not support the 2-factor-authentification as stated in SAP note 2129147. Some customers could solve this issue via a workaround by:

1) Getting an internal exception from the 2-factor-authentication for a dedicated test user in Q-system

2) Disabling 2-factor-authentication for this dedicated test user within Q-system

3) Maintaining this test user in “test your processes” app as DEFAULT user

Below are the example screen shots:

 

If the workaround will work for you depends on the possibility to define user specific exceptions in your IdP, and of course if you get internally an allowance for this exception within Q-system.

Password:

The test user which you assign should have the same password with which test user log into SAP S/4HANA Cloud. If you change the password for SAP S/4HANA Cloud, then the password here should also be manually updated as the system does not update the password automatically. If the password is not updated or incorrectly entered, then the test execution will not happen.Based on the customer password policy the system passwords changes frequently depending on customers, it could a month or every quarter. Each time the password changes, it needs to be updated here as well.