3787249 - Replication Flow performs a new initial load after changing the Maximum Parallel Delta Transfers parameter

After modifying the Maximum Parallel Delta Transfers parameter of a Replication Flow and redeploying it, the Replication Flow performs a new initial load instead of continuing from the previous delta position.

• SAP Datasphere
  
  

The Maximum Parallel Delta Transfers parameter is part of the technical runtime configuration of the Replication Flow.

Although this parameter only influences how delta records are processed in parallel, changing it modifies the Replication Flow configuration and therefore requires the flow to be redeployed.

During redeployment, Datasphere recreates the runtime artifacts associated with the Replication Flow, including the metadata that maintains the replication state and delta subscription.

As a result, the previous replication state cannot be reused and a new baseline must be established.

This behavior is designed to ensure data consistency and avoid potential issues such as missing records, duplicate records, or inconsistencies between the source and target systems.

This behavior is expected by design.

Any change to deployment-relevant Replication Flow parameters may require the replication state to be reinitialized, resulting in a new initial load.

Before modifying such parameters in production environments, evaluate the impact of a potential initial reload, including the additional data transfer, processing time, and resource consumption.

It is recommended to plan configuration changes during maintenance windows and validate their impact in a non-production environment before applying them to production systems.

DWC, datasphere, replication, flow, initial, load, deltal, transfer, parallelism, redeployment, reinitialization, subscription, runtime, configuration, reload, consistency, deployment, performance, slt, abap, odp, datasource , KBA , DS-DI-RF , Replication Flow Runtime , Problem