3794125 - Resume/restart of failed partitions after initial load failure in Replication Flows in SAP Datasphere

• During the initial load of the Replication Flow, several partitions failed with an Error status, which caused the entire Replication Flow to fail. This issue has also been observed with several high-volume Initial Replications in SAP Datasphere.
   
• You would like to know whether there is a way to resume or restart only the failed partitions, rather than having to restart the complete Replication Flow from the beginning.

1. Check the Replication Flow in the data integration monitor

2. Go to Partitions

1. Resuming Replication Flow at the partition level is not supported. Even from ABAP.

   There are several reasons for this, but one prominent reason is that the cloud initiates the transfer request and sends that to ABAP, and not the other way around.

2. Submit an enhancement request via the Influence Opportunity Homepage - Customer Influence. This allows your suggestion to be visible to other customers as well, who can then vote on it. For instructions on how to create an enhancement request, please refer 0003332382 - How to create an enhancement request for SAP Datasphere?

3297105 - Important considerations for SAP Datasphere Replication Flows
3542106 - How to Re-trigger Failed Partitions in Replication flow

Replication Flow, Partition, Pause, Resume, Datasphere, Initial load , KBA , DS-DI-RF , Replication Flow Runtime , DS-DI-ABA , Datasphere - Data Flow / Replication Flow ABAP Integration , Product Enhancement