Symptom
When a new field is added to the table/CDS view in the source system, the replication flow in Datasphere fails with the following 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 Data builder
- Select the space
- Search for the Replication Flow
- Check the status of the replication flow in Data Integration Monitor
Cause
Structural changes to source objects are not supported.
Resolution
Whenever there is an change in source CDS view/table, it must be compatible with targe object in Replication flow.
Workaround (see SAP Note 3297105 - Important considerations for SAP Datasphere Replication Flows)
- Remove the replication object with schema changes from the replication flow
- Deploy the replication flow so the specific object is removed
- Add the same replication object to the replication flow
- If source/target names are different, please follow the below additional step:
- Select the replication object in the editor
- Map to existing target to fetch metadata of target schema
- Deploy the replication flow
- Only the replication object with structural changes will be re-loaded and initial load for the specific object will be re-executed.
- The structural changes supported through the workaround are below:
- New columns
- Remove columns
- Changes to compatible data types
- Add primary key
For more information, see Modify a Replication Flow | SAP Help Portal
See Also
- SAP Note 3297105 - Important considerations for SAP Datasphere Replication Flows
- Modify a Replication Flow | SAP Help Portal
Keywords
transform error, invalid transform table schema, column not found, field, column, replication flow, SAP Datasphere , KBA , DS-DI-RF , Replication Flows , DS-DI-ABA , Data Flow / Replication Flow with ABAP as data source , Problem