How To Configure Tricentis Tosca With SAP Solution Manager 7.2?
4.9 out of 5 based on 16456 votesLast updated on 20th Nov 2026 25.3K Views
- Bookmark
Enroll in the Tosca Course to master model-based testing, test automation, and API testing through hands-on practice, real-time projects.
Tricentis Tosca along with SAP Solution Manager 7.2 is able to cooperate in SAP testing management. The Tricentis Tosca tool can help you automate the tests, while with the help of SAP Solution Manager it is possible to manage the tests, test plans, test cases and test results. But in order to work effectively, some extra actions should be taken. It means that some configuration, user permissions and test data should be set up. Otherwise the process of integration will fail, or test results won’t be sent to the right place.
Understanding How the Two Tools Work Together
Tosca can be used for the purpose of creation and execution of automated tests. It allows testing of SAP screens, field validation, entering of data, and verification whether a business process functions properly.
SAP Solution Manager 7.2 can assist teams in planning testing efforts. It provides opportunities for storage of test plans, linking tests with business processes, and tracking of testing efforts.
If the tools are integrated, the tester is able to organize his/her testing activities in accordance with the provided SAP Solution Manager workflow and execute automated tests using Tosca. Test results can be analyzed at the place where the team tracks its testing efforts.
Depending on the particular version of Tosca as well as the integration method applied, the procedure of integration is going to be different. The classic and the service based integration methods are not going to apply the same settings. Therefore, you have to make sure which approach is available in your project.
A Tosca Course on SAP Integration must cover the topic of test recording as well as connection, user access, test packages, and results transfer between tools.
Check the Requirements Before Starting
Before you change any settings, make sure the required systems and access are ready. This simple check can save a lot of time later.
You will generally need:
- A supported version of Tricentis Tosca.
- SAP Solution Manager 7.2 with the required setup and support package.
- SAP GUI installed on the machine where it is needed.
- Access to the correct SAP system and client.
- Permission to use the required Tosca workspace.
- The SAP host name, system ID, client, and instance number.
- Help from an SAP administrator for settings that need special access.
- Network access to the required SAP or Tosca services.
Do not assume the version specifics. Look up Tricentis documentation for your particular installation.
It will be helpful to find out if your project connects to the system using RFC connection or service connection. RFC stands for the possibility of SAP systems or some other authorized tools to execute functions over the connection. In case of the service connection, you might need web addresses, authentication options, and services of a server.
These ways of connection have their specifics and the combination of procedures can cause hard-to-understand problems. For learners considering Tosca Training in Hyderabad, ask whether the practical sessions cover SAP Solution
Prepare SAP Solution Manager 7.2
SAP Solution Manager should be prepared for collaboration with Tosca. It is essential that the SAP administrator will check the settings of Test Suite and register an external test tool.
For the classic integration, the registration can include these parameters:
| Setting | Value or purpose |
| Tool name | TRICENTIS TOSCA |
| Program ID | TOSCATESTSUITE.ECATTINTEGRATION |
| Tool database | Workspace key, commonly TOSCA |
| Tool run database | Workspace key, commonly TOSCA |
| User access | Required permissions for the connection and test work |
Make sure that these values match your installed versions according to the documentation before applying them. These settings will vary depending on how you integrate them into your system.
Also, the SAP administrator has to make sure that the user has appropriate access rights. A user may have enough privileges to log into SAP, yet still not have access to functions used by Tosca.
It is not wise to use an administrative account just to avoid access rights problems. Rather, you should request an account that provides the necessary access rights. If you are checking Tosca Certification Cost, confirm the latest fee with the official provider or training partner.
Configure the Connection in Tosca
After SAP is configured, launch Tosca Commander and choose the appropriate project.
Proceed as follows:
Launch Tosca Commander.
Select the desired project.
Right-click the root of the project.
Choose SAP Solution Manager → Configure SAP Solution Manager Integration.
Use the configuration wizard.
Fill in all required data about the connection and workspace.
Make sure that the configuration is completed successfully.
Names of some options may vary depending on the version of Tosca Commander.
Provide necessary information such as SAP host, client, system ID, and instance number. This information will allow the connection to the proper SAP system. In case something is wrong with the values, the connection cannot be established or the wrong environment will be used.
In case your project uses an RFC connection, make sure that the settings of the connection and login data are right. In case of using a service-based connection, provide necessary data according to server address and authentication procedure.
The same applies when choosing Tosca Certification preparation. A certificate can show that you have studied the tool, but practical experience helps you understand how the complete integration works.
Check SAP GUI and the Tosca Add-in
The SAP GUI and the Tosca add-in should also be configured properly, in case where the integration is supposed to use them.
Check the following:
- The SAP GUI is installed and supported by your version of Tosca.
- The SAP GUI connection points to the right system.
- The right Tosca add-in is installed and registered.
- The right desktop session is used.
- The user has access to both tools.
It is important because a connection can work in one computer and not work in the other one. This could be caused by different versions of software or other settings.
Also, it is important which desktop session is active. As per documentation of the integration, in certain cases, Tosca must be launched from the desktop that hosts an active session of SAP Solution Manager.
In case you start to learn Tosca Automation Testing, it would be good if you noted the version of Tosca, SAP GUI and the computer where you conducted the test.
Set Up Tosca Server Services If Needed
Some integration approaches require the use of services in the Tosca Server. Services allow SAP Solution Manager to communicate with Tosca when performing supported test operations.
First of all, verify whether you require the SAP Solution Manager Service and Notification Service. Each approach does not necessarily use the same configuration of services.
In case you have to use the above services, make sure that:
- the proper workspace is chosen;
- the service is enabled and operational;
- the service user has sufficient rights;
- the network and port configuration is set up correctly;
- there are no connection errors in the service logs.
For a service-based integration, some HTTP destinations may be necessary in the transaction SM59. Some installations use an API path like /sap-solution-manager/api/sap-sm-testsuite and an authentication URL like /connect/token.
Set Up Solution Documentation Synchronisation
Establishing the connection does not mean that all the information about the business process is going to be visible in Tosca. In case your solution makes use of Solution Documentation Synchronisation, then it needs to be configured independently.
Open Tosca Commander, and select the appropriate project or component folder. Choose the required integration preparation and define SAP Solution Manager as an external system.
Depending on the configuration, you may require this information:
| Setting | What it does |
| Server | Identifies the SAP server |
| Client | Selects the SAP client |
| System ID | Identifies the SAP system |
| Instance number | Identifies the SAP instance |
| User | Specifies the account used for access |
| Branch | Selects the Solution Documentation branch |
| Solution | Identifies the solution being used |
| API entry point | Identifies the required service endpoint |
Please validate these parameters with the SAP team. An incorrect branch or solution will lead to the loss of information on the expected business process information.
Furthermore, validate the direction of synchronization as well. There are scenarios where information is imported into Tosca, while there are other cases where information is exported.
There may also be situations where information can flow in both ways. It is important for the team to choose the source system for the requirement.
Before starting with the synchronization, verify the objects that need to be checked out in case the workspace is using a checkout control mechanism. Try with a small number of objects first and validate if the information appears properly.
A learner preparing for a Tosca Interview Questions should know that integration of tools and synchronization of information are two separate processes.
Create Test Plans and Test Packages
Once the connection and synchronisation have been set up, you will be able to work with test plans and test packages.
The SAP Solution Manager provides tools for organizing the testing process. Automated tests provided by Tosca can be used in the supported execution process.
In the improved workflow, the test package can be imported into Tosca as an Execution List.
The procedure is as follows:
- Make sure that all necessary test configurations are available in Solution Documentation.
- Create or open the test plan.
- Select the necessary test configurations.
- Prepare the test package.
- Import or synchronise the package into Tosca.
- Make sure that all expected tests are present in the ExecutionList.
- Execute the test package in the approved test environment.
- Review the results of executing in Tosca and SAP Solution Manager.
Check Whether Test Results Are Correct
After the test execution, verify whether the output of the test is where we expect it to be.
First, take a test which has a well-known result. For instance, you can choose a test scenario verifying that the value of the required field is right.
Consider these questions:
- Has the test started from the expected package?
- Was the correct test case executed by Tosca?
- Can you see the execution status in Tosca?
- Can the related result be seen in SAP Solution Manager?
- Can the details about the failure and error information be seen?
- Does the result relate to the correct test execution?
If there is no result in SAP Solution Manager while Tosca runs the test, then you should consider the test execution process and related service or communication log.
Do not continue running the whole test suite after the first failure. It is a waste of time and can obscure the cause of the problem.
It should be mentioned that the Tosca Course should also contain this stage of testing. The ability to execute a test is important, but the ability to trace the result is no less important.
Find and Fix Common Problems
Most setup problems can be checked one part at a time. Start with the connection, then check access, synchronisation, execution, and result transfer.
| Problem | What you should check |
| Tosca cannot connect to SAP | Host, client, instance number, and login details |
| RFC call fails | SAP permissions and RFC configuration |
| Add-in does not work | Installation, registration, and software versions |
| Requirements are missing | Branch, solution, and synchronisation settings |
| Test package is missing | Test plan and test configuration setup |
| Test runs but result is missing | Execution workflow and communication logs |
| Service request fails | Endpoint, port, authentication, and service status |
Conclusion
When configuring Tricentis Tosca and SAP Solution Manager 7.2, it helps to follow the process step by step. Firstly, the compatibility and access should be verified. Secondly, the connection configuration and preparation of the necessary services should be performed along with the synchronisation setting for your project if needed. Finally, a test should be carried out and checked whether the result arrives in the right place.
Subscribe For Free Demo
Free Demo for Corporate & Online Trainings.