3808636 - Replication flow fails with "Subscriber is not registered as a subscriber for object" after system refresh in ABAP integration

SAP Datasphere

1. Open an existing replication flow in Datasphere Data Builder.
2. Start or restart the replication run.
3. Observe that the run fails with the error: "Subscriber is not registered as a subscriber for object

After a system refresh or system copy of the ABAP source system, client-specific subscriber mapping entries are lost. Missing entries in ABAP table DHAPE_RMSSUBSMAP (mapping replication ID, run ID, and subscriber ID) cause a mismatch, leading to the error "Subscriber is not registered as a subscriber for object."

1. Confirm whether the ABAP source system was recently refreshed, copied, or migrated.
2. If confirmed and the above error occurs, delete the affected replication flow(s) in Datasphere.
3. Create a new replication flow.
4. Add the required source objects again.
5. Start a new run, performing a full load and/or delta initialization as required.

For SAP Notes, Community and SAP Help, we use the below:

• KBA -3434834  SAP Datasphere - ABAP Integration - Restart of Replication Flow fails
• KBA -3643099  How to check CNV_NA_DI (Note Analyzer) in On-Premise ABAP-based systems for Datasphere Data Flows and Replication Flows
• KBA - 3498095 Note Analyzer for Datasphere Data Flows and Replication Flows (ABAP Integration)
• Help page - Working With Existing Replication Flow Runs | SAP Help Portal 

subscriber is not registered, subscriber not registered, Datasphere replication flow, ABAP integration, system refresh, system copy, DHAPE_RMSSUBSMAP, delta initialization, restart replication flow, scheduled replication flows, CDS source, replication fails, retry=false, subscriber ID mismatch, CNV_NA_DI, DS, RF , KBA , DS-DI-ABA , Datasphere - Data Flow / Replication Flow ABAP Integration , Problem