---
title: "Integrating SAP Enterprise Continuous Testing by Tricentis with Syniti"
slug: "integrating-tricentis-tosca-cloud-with-syniti"
updated: 2026-11-10T17:04:28Z
published: 2026-11-10T17:04:28Z
canonical: "skthelp.syniti.com/integrating-tricentis-tosca-cloud-with-syniti"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrating SAP Enterprise Continuous Testing by Tricentis with Syniti

## Overview

As part of SAP's Business Transformation Management (BTM) and Integrated Toolchain methodologies, integrating the Syniti Knowledge Platform (SKP) with SAP Enterprise Continuous Testing by Tricentis (Tosca Cloud) allows you to combine the SKP’s data transformation, quality, and governance capabilities with the automated testing capabilities of Tosca Cloud for SAP system transformations, for example, SAP S/4HANA.

SAP business processes require highly interconnected data that maintains proper referential integrity across multiple business objects. For example, creating a sales order requires:

- A valid customer (sold-to) assigned to a specific sales organization, distribution channel, and division.
- Materials properly configured for that sales organization structure.
- Plants, pricing conditions, and inventory levels that support the transaction.

Traditional test data creation methods often fail to satisfy these complex relationships, causing test failures and project delays. This integration leverages the SKP's data transformation capabilities and access to production-grade SAP data snapshots to create valid test datasets for Tosca Cloud.

## Prerequisites

- An active SKP tenant with Administrator privilege.
- Request an SKP API User account from Syniti Support which must be configured in Tosca Cloud to enable integration between Tosca Cloud and the SKP. Refer to [Knowledge Platform API](/v1/docs/knowledge-platform-api) for more information.

> [!NOTE]
> Note
> 
> - Syniti Migrate Public API is tenant-specific. To access public API reference documentation, replace **<tenant_name>** in the following URL with your tenant name: https://<tenant_name>.migrate.syniti.com/swagger/index.html
> - If you need support accessing Syniti Migrate API and documentation, raise a support request. Refer to [Contact Support](/v1/docs/contact-support) for more information.
- An active Tosca Cloud tenant.
- Ensure that Tosca Cloud is integrated with the SKP using the SKP API User account. Complete the following steps in Tosca Cloud:
  1. Access **My Profile > Settings > Integrations > Syniti Integration** and click **Set Up Integration**.
  2. Enter the following details:
    - **Client ID:** Enter the SKP API User’s username.
    - **Client Secret:** Enter the SKP API User’s password.
    - **Token Endpoint:** Enter the appropriate endpoint based on your region.
      - **Americas:** https://api.syniti.com/oauth2/tokens
      - **EMEA:** https://api.syniti.eu/oauth2/tokens
      - **Australia:** https://api.syniti.au/oauth2/tokens
      - **Canada:** https://api.syniti.ca/oauth2/tokens
    - **Base URL:** Enter your SKP tenant URL, for example, https://<tenant_name>.migrate.syniti.com.
    - **Tenant ID:** Enter your SKP tenant ID. In the SKP, click **My Profile** and click the tenant name just below your user name. The tenant ID will be copied.
- Snapshot relevant tables from the SAP testing environment, for example, TGTS4H datastore.

## Integration Steps

To enable the Tosca Cloud integration with the SKP:

1. In the SKP, access the **Admin** module and select **Parameters**.
2. Turn on the **Enable Tricentis** **Tosca Cloud Integration** toggle.

The integration is now enabled in your tenant. The SKP automatically creates a Tosca Cloud system datastore and triggers a Tricentis - Setup Creation job in Migrate to create the required Migrate object configurations to support communication between the SKP and Tosca Cloud.

The following components becomes available:

- Tosca Datasource
- Testing Subject Area
- Tosca Test Dataset Type
- Complete Migrate project setup registration, including:
  - Dedicated migration project & release for test data activities
  - Release management and milestone tracking for test data deliverables
  - Deployment configuration for test data
  - Development Area for the working datasources
- ETL Target Export of Tosca Endpoint (Tosca Test Case) task type to expose the test data via an OData endpoint

These components complete the basic configurations needed to receive test case metadata from Tosca Cloud and allow Migrate Mappers and Developers to start their regular migration activities to create the required data exports.

## Understand Test Case Structure Reception

After enabling the Tricentis integration toggle, test case datasets can be created in the SKP directly from Tosca Cloud. Test cases are designed in Tosca Cloud based on business process definitions from SAP Signavio, then passes them as dataset definitions to the SKP.

Refer to the [Use test case design](https://docs.tricentis.com/sap-ect-cloud/en-us/content/testcase_design/overview.htm) for information on test case design solutions.

When the SKP receives a test case data request, it automatically creates a new dataset with the specialized Tricentis Tosca Test dataset type in Migrate. This dataset includes a Test_ID field which is the auto-generated primary key for OData test data exports.

Each test case structure defines:

- The business process being tested, for example, Create Sales Order.
- The dataset elements required for the test, for example, sales organization, customer, material.
- The test variations needed, for example, North American customers, critical materials, European sales.

## Create Test Data Exports

### Mapping

The [mapping](/v1/docs/mappings) process follows the standard migrate transformation workflow, with specific considerations for test data preparation:

#### Data Flow Overview

The overall data flow involves two transformation cycles:

1. **Initial migration**: Legacy source systems → SAP target system (standard migration process)

2. **Test data preparation**: SAP target system → Tosca Cloud format (this article)

#### Source Selection

In Mappings, import the Tosca test case dataset, create a target source with working tables, and then map data elements from the relevant datastores. For example, SAP target snapshot datastore (TGTS4H). This approach ensures:

- Test data reflects the actual SAP environment structure that was successfully loaded
- Data includes all necessary business object relationships as they exist in SAP
- Allows access to manually configured SAP Objects created outside of the SKP.

> [!NOTE]
> Note
> 
> The source data for Tosca Cloud mappings must come from the post-load validation process where Migrate extracts and verifies what was actually loaded into SAP target.

> [!NOTE]
> Note
> 
> Ensure that the datasource associated with the working tables has a schema defined according to the case-sensitive requirements of the working database. For example, the default schema for a PostgreSQL working database must be entered in lowercase, such as `dbo` .

#### Referential Integrity

Create mappings that preserve complex SAP relationships. For example, when mapping sales order test data:

- Join customer master data with sales organization assignments
- Filter materials to those valid for the specified distribution channels and divisions
- Include pricing conditions, plant assignments, and other dependencies
- Maintain parent-child relationships between related business objects
- Join back to the Migration staging tables where needed - for relevancy, filtering, legacy filter data, etc.

#### Manual Rule Creation

You’ll see a few migration process-specific fields appended to the testcase dataset. Write manual transformation rules and views to extract the appropriate data subsets that match Tosca Cloud test case requirements:

- The auto-generated Test_ID and ZlegacyTest_ID fields require a Rule map action and command (rule SQL) based on the working database to generate a primary key or unique IDs for each test case run. For example, `newId()` or `gen_random_uuid()`.
- For simple mappings, create export views directly against the generated Pass-through views (VBAK_S4H, VBAP_S4H).
- Use standard Transformation logic where necessary to produce more complex Export views, especially for complex relevance and org specific extensions.
- Create custom SQL views that filter data to specific test scenarios
- Apply business logic that matches the test case variations
- Transform data into the format expected by Tosca Cloud

Refer to [Mapping the Fields of a Datasource](/v1/docs/mapping-the-fields-of-a-datasource) for more information.

### Target Export Configuration

After completing the mapping process in the working databases, configure the target export:

- **D****ata Transform ETL Job**: Clicking the **ETL** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-F66RJQPM.png?sv=2026-02-06&spr=https&st=2026-11-13T09%3A04%3A19Z&se=2026-11-13T10%3A04%3A19Z&sr=c&sp=r&sig=J%2B7eO42GfZPL68V5sab9wxa1ubdDsn1rjvIDOIEVTiA%3D) icon at any level on the *Mappings* page auto-builds the required Data Transform ETL job and task registrations. Monitor task progress on the *Job Queues* page.
- **Rebuild and Execute ETL:** If any changes are made on the *Mappings* page for the Tosca Test dataset, ensure that you rebuild and execute the ETL Job to avoid job failures.
- **Target Export > Tosca Endpoint:** A new Target Export - Tosca Endpoint ETL task will be available for each test case dataset. This ETL task allows you to expose data in the format required by Tosca Cloud.
  - Switch to Target Exports ETL type and execute the Tosca Endpoint ETL task.
- **OData Endpoint Access**:
  1. To access the endpoint, click the **Edit** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-FI29Y7OI.png?sv=2026-02-06&spr=https&st=2026-11-13T09%3A04%3A19Z&se=2026-11-13T10%3A04%3A19Z&sr=c&sp=r&sig=J%2B7eO42GfZPL68V5sab9wxa1ubdDsn1rjvIDOIEVTiA%3D) icon to view the Tosca Endpoint’s ETL details.
  2. Turn on the **Expose for Consumption** toggle to generate and copy the OData endpoint for Tosca Cloud to import the test data.![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-1773072168611.png?sv=2026-02-06&spr=https&st=2026-11-13T09%3A04%3A19Z&se=2026-11-13T10%3A04%3A19Z&sr=c&sp=r&sig=J%2B7eO42GfZPL68V5sab9wxa1ubdDsn1rjvIDOIEVTiA%3D)
  3. Click **Save**.

### Import Test Data in Tosca Cloud

Complete the following steps to import the requested data for the test case:

1. In Tosca Cloud, access **Prepare > Test data** and click **Import from Syniti.**
2. Enter the copied OData endpoint URL and click **Import Data**.

The test data will be populated for the attributes in the test case datasets in Tosca Cloud.

## Data Privacy and Compliance

This integration enforces GDPR and PII compliance by ensuring that all created test data used in non-production environments is appropriately masked, traceable, and governed through the SKP's data management controls. This includes:

- **Data Masking and Anonymization**: The SKP's transformation capabilities enable a developer to apply masking rules to sensitive fields, de-identifying personal information before making it available to Tosca Cloud.
- **Audit Trails**: Data governance controls automatically track and log all test data creation activities, including mapping process, ETL export generation, and which test cases consumed specific datasets.
- **Access Control**: OData endpoints exposing test data enforce authentication and authorization, ensuring only authorized Tosca Cloud users and test environments can retrieve test export datasets.
- **Policy Enforcement**: Test data exports apply organization-specific data protection policies configured in the SKP, maintaining consistent compliance standards across all test export datasets.

## Related Articles

- [Dataset Design](/v1/docs/dataset-design)
- [Job Queues](/v1/docs/job-queues)
- [Mapping the Fields of a Datasource](/v1/docs/mapping-the-fields-of-a-datasource)
- [Mappings](/v1/docs/mappings)
- [Project Setup](/v1/docs/project-setup)
- [Target Exports](/v1/docs/etl-tasks-at-the-dataset-level#target-exports)