Overview
This article answers the most frequently asked questions about the Syniti Knowledge Platform’s (SKP) Replicate Preview module’s capability and for customers migrating from the Syniti Replicate desktop version or Syniti Data Replication (SDR).
What is the minimum desktop version required to start the migration to Replicate Preview?
Existing customers using the Syniti Replicate desktop version must be upgraded to at least version 11.0.0.27 before migration can begin. The migration activity will be carried out by the Syniti Customer Support team.
New customers are provisioned with the SKP’s Replicate Preview module.
What is the performance difference between SKP’s Replicate Preview and Syniti Replicate desktop version?
The SKP’s Replicate Preview module is designed to provide performance that is equal to, or comparable with, the Syniti Replicate desktop version, and testing has validated this improvement. However, actual performance will vary depending on the customer environment and connection methods used, including system configuration, data volume and complexity, connection latency, cloud performance, available cloud bandwidth, and network traffic.
How secure is the SKP?
SKP is built with layered, enterprise-grade security controls. Customer data is encrypted in transit with TLS 1.2+ and at rest with AES-256, services authenticate with JWT-based identity and mTLS between components, and access is restricted through tenant isolation, RBAC, audit logging, and least-privilege controls. Syniti also maintains independent security attestations such as SOC 2 Type II, ISO 27001, and NIST 800-53 attestation, while the platform is being aligned to IL4 and FedRAMP High standards across regions.
For replication-specific flows, data is handled as part of a controlled pipeline, not stored indefinitely. In the replication cloud model, that temporary data is automatically deleted after the workflow finishes. Customers still control the connector, credentials, and login method, while Syniti runs the managed cloud environment under documented security controls.
How do I perform long text data extraction?
Replicate Preview supports the extraction of long text fields such as BOAQ_READ_TEXT (text stored via SAP's Read Text function module) from SAP source systems. The process is the same as scanning the SAP datastore to profile the long text table and creating a replication for it to snapshot data into a target datastore. Dedicated guidance is available for the following SAP system types:
RFC Connection:
HTTPS Connection:
How does RFC and SNC work now?
Replicate Preview supports SAP RFC connections similar to the Syniti Replicate desktop version. You just need to create a SAP NetWeaver datastore connection with/without SNC mode. Refer to Connecting to SAP Systems using SAP NetWeaver RFC and SNC Certificate Management in the SKP for more information.
How do I configure unsupported database connections?
To view the full list of databases supported by Replicate Preview, refer to Sources and Targets. If your database is not supported, submit a request through the Syniti Ideas portal. Refer to Contribute to Syniti Ideas Portal for more information on submitting a request.
Syniti regularly adds support for additional databases in Replicate Preview.
How do I run replications from ETL jobs?
There is no change to the process of registering a Refresh Snapshot Table ETL task type. Target datastores and replications configured in the Snapshot Management workspace will be available in Migrate to register the Refresh Snapshot Table ETL task type.
To run replications configured in a workspace, you can configure a new Execute Cloud Replication (Preview) ETL task. Alternatively, you can also create an Orchestrate workflow with a Run Replication (Preview) task and register the Run Orchestration ETL task type to execute replications through that workflow.
Note that the Target Export and Refresh Snapshot Table ETL task types are now executed using Replicate Preview that uses a cloud-based replication engine. For existing customers in the transition period, you can choose either the cloud-based or legacy replication engine for Target Export ETL tasks. Target export files can be stored locally or in Syniti Drive.
How does streaming work now?
Streaming functionality is not supported in Replicate Preview, and as an alternative, you can use the SAP NetWeaver HTTPS connection and configure the number of parallel workers to extract data concurrently, significantly reducing overall extraction time. HTTPS connections use pagination mechanisms (numeric offset or key set) to retrieve data in manageable chunks, improving performance for large datasets.
Refer to Connecting to SAP Systems using SAP NetWeaver HTTPS for more information.
How do I import/export a file?
File import and export in the SKP is handled through Syniti Drive, which provides personal and shared drive storage within the platform. You can:
Upload files: Click Upload File within any drive or folder, or drag and drop files directly.
Download files: Select a file and click the Download icon. Multiple files can be downloaded as a single .zip archive.
Organize files: Create folders and subfolders, move, copy, rename, and delete files and folders.
Refer to File Replications and Working with Drives for more information.
How will Snapshot Management work after the migration?
After migration, Snapshot Management is handled within a dedicated workspace in Replicate Preview. Source and target datastore connections and Snapshot (Refresh) replications are configured and executed directly in Replicate Preview’s Snapshot Management workspace.
A target datastore registered in the Snapshot Management workspace creates a datasource in Migrate > Catalog > Datasources (with Datasource Purpose set to Snapshot), making the target datastore available for existing Migrate workflows. Refer to the Key Changes section for more information.
How do I Snapshot MIG tables?
In the context of Syniti Migrate, the MIGRATE_APP system datastore is now available as OData endpoints and is automatically provisioned in the SKP’s Catalog module for new and migrating customers from the Syniti Replicate desktop version.
In the Snapshot Management workspace, creating the SRCCONSTRUCT target datastore automatically includes MIGRATE_APP as a source datastore. It contains a list of views prefixed with MIG_, which are used to store data for Central Relevancy tables, System Reports, and Rulebook views. Refer to the Add an SRCCONSTRUCT Target Datastore section for more information.
Are there any missing features in Replicate that SDR had?
The following features from Syniti Replicate desktop version are not yet available in Replicate Preview:
Change Data Capture capabilities such as Mirroring and Synchronization replications
Custom scripts
Global functions
How do I configure partitioning?
Replicate Preview supports both automatic and custom partitioning for Snapshot (Refresh) replications. Partitions split data into separate parallel execution units using source and target WHERE conditions, significantly improving performance for large tables.
Auto-partitioning: Enabled by default and automatically applied to tables with 500K+ rows or 100 MB+ in size.
Custom partitioning: Add partitions manually or select a primary key field and click Auto-Generate to define custom partitions.
Refer to Configuring Partitions for Refresh for more information.
How can I use replication groups in Snapshot Management?
Replication groups allow you to organize and manage multiple replications together — scheduling, executing, and monitoring them as a unit. Groups are especially useful when managing replications for different departments, systems, or business domains.
Refer to Adding Replications to Groups for more information.
How can I reprocess failed replications in Snapshot Management?
If a replication job fails (status: Errored or Completed with Errors), you can reprocess it by re-executing the replication job:
Filter the Progress Status column by Errored to identify failed replications.
Use the multi-select checkboxes to select one or more failed replications.
Click the Execute Replications icon to re-run them.
Refer to Execute Replication Jobs for more information.
Note: If any partition fails during replication, you can either re-run the failed partition or the entire replication based on your replication settings and partition strategy. Refer to the Replication Execution With/Without Partitions section for more information.
What customizations can be made as part of field mappings?
In the Field Mappings dialog box, when you map explicitly, you can modify the data type to match the target table, change the table name, and adjust the target table’s size, precision, and scale as needed.
Additionally, you can drop a target table, update field mappings, and rerun the replication to recreate the target table as needed.
How can I establish replication dependencies in Snapshot Management?
The Replication Dependencies feature allows you to specify which replications must complete successfully before a given replication runs. This is particularly useful for tables with foreign key or other referential constraints.
To configure dependencies:
In the Replications panel, select the replication and click the Replication Dependencies icon.
In the dialog box, select the checkboxes for all replications that must complete before the selected replication runs.
Click Save.
Dependencies are honored when replications are executed at the group, source, or target level. It is recommended to create a dedicated group for replications that share dependency relationships.
Refer to Configuring Replication Dependencies for more information.
Can I now optimize replication execution between groups?
Yes. Each replication group in Replicate Preview supports two execution modes that control how replications within the group are run:
Parallel Mode: All replications in the group are executed simultaneously, based on the concurrent replications count set in the workspace settings. For example, if you execute replications at a target level with more than 100 replications and the concurrent replication is set at 20, Replicate Preview executes 20 replications in parallel.
Series Mode (Serial Execution): Replications in the group are run one after another, even if the concurrent replications count is set to 20 (for example). They are ordered by their assigned priorities and replication dependencies. This is the recommended mode when the replications have interdependencies. for example, parent tables must be loaded before child tables.
You can set or change the execution mode by editing the group from the Groups tab. Refer to Working with the Groups Tab for more information.