3553846 - Replication from ABAP Source Systems Stuck in 'Initial' or 'Retrying' State - SAP Datasphere

Replication Flows from source ABAP-based systems are stuck in "Initial", "Retrying" or "In Progress" state and do not load any data into the target Datasphere.

In the "Metrics/Details" section of the Data Integration Monitor, one or more of the following messages may be observed for Initial loads:

• The source connector has accepted the initial load partitioning request. The next attempt will be after <datetime>.
  Retrying for initial load partitioning. The source connector has previously accepted the initial partitioning request.
  
• Initial load partitioning completed. Data transfer messages are available.
• Data for initial load is currently not available. Next check will be after <datetime>.
• Initial load stuck at status 'Transferring initial load'

Additionally, for "Initial and Delta" loads, it may be seen that the delta load partition status remains in "DATA_NOT_READY", even though the "Details" section shows that partitions are being added and the transfer count is increasing.

SAP Datasphere

• Check Replication Flow execution monitor screen.

There can be multiple reasons for Initial loads to stall: 

• Required SAP Notes may be missing on the source system
• Missing authorization for the corresponding users on the source system
• Required technical jobs are not running on the source system

As a prerequisite, please ensure that all relevant note corrections have been implemented in On-Premise source system. If these Notes are not fully implemented, subsequent checks such as authorization, technical jobs or job settings may not function correctly. Please follow How to check relevant note corrections in On-premise ABAP-based systems for Data Flows and Replication Flows | SAP Help Portal.

1. Ensure all authorizations are in place as described in KBA 3487621 - Replication Flow fails : "No source partition is available" due to Subscription authorization issues
2. Ensure the technical jobs are in scope and background jobs are running per SAP Note 3561739 - ABAP Data Integration - Technical Jobs.
3. Follow Guided Answer DATA_NOT_READY Troubleshooting in Datasphere Replication Flows 

SAP KBA 3508287- How to troubleshoot Replication Flow for CDS views from S/4HANA On-Premise to SAP Datasphere 

replication flow, stopped, hung, stalled, initial, initial load, retrying, source connector, WORK_ORDER_TIMEOUT, , KBA , DS-DI-RF , Replication Flow Runtime , CA-DI-IS-RMS , Replication Management Service , Problem