Symptom
When a new field is added to the table/CDS view in the source system, the replication flow in Datasphere is failing with the below errors:
"No source data is available for replication. Replication runs are retrying."
"Subscriber XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX is not registered as a subscriber for object"
Environment
SAP Datasphere
Reproducing the Issue
- Navigate to Databuilder
- Select the space
- Search for the Replication Flow
- Check the status of the replication flow in Data Integration Monitor
Resolution
- Ensure that all SAP notes required for running Replication Flows on Datasphere, are applied on the source S/4HANA On-premise system – per SAP Note 2890171 - SAP Data Intelligence / SAP Datasphere - ABAP Integration. In order to verify that all notes from the central note are applied on the source system, use the Note Analyzer tool – see How to check relevant note corrections in S4HANA On-premise for Data Flows and Replication Flows.
- Whenever there is an enhancement in the CDS view/table, perform the below steps before deploy/run the replication flow
1.Delete the target Local Table in Datasphere
2.Rename the target Local Table other than the existing ones in Replication Flow Data Builder
3.Add the missing column to your Local Table then deploy this Local Table
These can make the columns in the target match the columns in the source
See Also
3508287 How to troubleshoot Replication Flow for CDS views from S/4HANA On-Premise to SAP Datasphere.
Keywords
transform error, invalid transform table schema, column not found, field, column, replication flow, Datasphere , KBA , DS-DI-RF , Replication Flows , Problem
Product
SAP Datasphere 1.0