Modify Replication Flow Object Schemas and Settings
You can modify an existing replication flow after it has been created. The changes you can make depend on the current status of the replication flow and the kind of updates you want to make.
Add an Object to a Replication Flow
-
Open the replication flow in its editor.
-
Choose .
-
Select the objects that you want to add.
-
Choose Add Selection.
-
Select a Load Type and set other properties as appropriate.
-
Click Deploy to deploy your changes.
Remove an Object from a Replication Flow
-
Open the replication flow in its editor.
-
Choose Remove next to the object that you want to remove.
-
Click Deploy to deploy your changes.
Add a Column to an Object
-
Open the replication flow in its editor.
-
Add the required column to the target object using the table editor.
-
Choose Additional Options → Map to Existing Target Object.
-
Click Deploy to deploy your changes.
Rename a Target Object
-
Open the replication flow in its editor.
-
Select the replication object that you want to rename.
-
Choose Rename Target Object.
-
Enter a new technical name.
-
[Optional] Select Copy Columns from Source Object.
-
Click Rename.
-
Click Deploy to deploy your changes.
Change Delta Load Run Setting
-
Open the replication flow in its editor.
-
Select Edit Run Settings.
-
Under Delta Load Run, select one of the following options:
-
At Delta Interval: The replication flow runs continuously and queries for delta changes based on the specified delta interval.
-
At Scheduled Time: The replication flow processes the available delta changes and then the run completes. The next run begins at the next scheduled time.
-
-
Click Save to confirm your changes.
Review and Apply Schema Changes in SAP ABAP (SLT) Source Objects
You can enable source schema change detection for an existing replication flow that uses an SAP ABAP (SLT) source and a SAP Datasphere (HANA) target to apply supported source schema changes without reinitializing the replication flow.
Schema changes are not applied automatically. To apply supported schema changes:
-
Open the replication flow in the editor.
-
Select the affected replication object.
-
Choose Review Schema Changes.
-
Review the detected schema changes.
-
Select the supported changes that you want to apply.
-
Save and Deploy to apply the selected schema changes.
Change Source and Target Thread Limits
-
Open the replication flow in its editor.
-
Select Edit Run Settings.
-
Update the Source Thread Limit and Target Thread Limit values.
-
Save the changes.
-
Click Deploy to deploy your changes.
NoteChanges that are not deployed are not taken into account when transporting the replication flow to another tenant.
Change the Load Type of an Object
You can change the load type of replication objects in a running replication flow:
-
Open the replication flow in its editor.
-
Select the replication object whose load type you want to change.
-
In the properties panel, select the required load type.
-
Click Deploy to deploy your changes.
NoteChanges that are not deployed are not taken into account when transporting the replication flow to another tenant.
Changing the Content Type (ABAP-Based Source Systems Only)
When working with ABAP-based source systems, you can switch between Template Type and Native (See Creating a Replication Flow).
-
You can't change the content type for replication flows created before wave 2025.04.
-
You must consider the impact on other replication flows that use the same source objects.
-
You must be certain about the existing column data types in the existing target. Otherwise, the replication flow deployment or run will fail due to a column data type mismatch between the source and target.
-
Changing the content type selection will affect the source column data types (date, time, and timestamp) for all existing replication objects in the replication flow.
-
Open the replication flow in its editor.
-
Change the content type.
Data Types Native Type Template Type Date
String (length = native content length)
Date
Time
NoteTime is not supported if your target is a local table (file). See Unsupported Data Types in a Replication Flow
String (length = native content length)
Time
Boolean
String (length = native content length)
Boolean
Timestamp
Decimal (Precision = abapLength, scale = abapDecimals)
Timestamp
Raw
Binary
String
NoteIf you change the content type from Template to Native and the existing target table already contains a column of type timestamp while the corresponding source column contains a native content type of decimal, then the source column will be treated as timestamp: The Native configuration reuses the schema of the existing target table, and the target column's data type takes precedence over the source column's original type. This keeps the target table schema consistent and avoids a type mismatch.
-
Review any required data type conversions.
-
Click Deploy to deploy your changes.
NoteChanges that are not deployed are not taken into account when transporting the replication flow to another tenant.
When changing the content type, you must convert some data types to ensure that they are supported by the selected content type: