3784530 - table id mismatch (sql error 1969) on delta in managed data product replication flows, SAP datasphere

• All managed data product replication flows fail with a Table ID mismatch during delta processing.
• The initial load is successful; subsequent delta loads fail.
• The issue affects various functional data products (for example, product, supplier, sales order, billing document).
• Representative error: "failed to fetch next package: SQL Error 1969 - Table ID mismatch: The remote table ID does not match the source table ID at the time replication was initiated: Expected ID: , but found: . This may indicate the remote table has been replaced or recreated. Please verify the source table integrity and restart replication if necessary."

• Product: SAP Datasphere
• Replication Flow Runtime

1. Run an initial load of a managed data product replication flow and complete successfully.
2. Start or resume the delta phase; the replication flow fails with SQL Error 1969 (Table ID mismatch) during delta transfer.

• The underlying remote/source tables were replaced or recreated (for example, after re-onboarding the managed data product). The replication flow’s runtime retained an outdated table identifier, causing a Table ID mismatch when delta processing resumed.
• This requires resetting the replication runtime state when underlying tables are recreated.

The developer team is working on the fix.
Meanwhile, please use the workaround below:

1. Open the Replication Flow monitor for each affected managed data product.
2. If the flow is not running, start it and wait a few seconds until it is active.
3. Stop the run, and confirm "Replication task cleanup completed" in the log.
4. Start the replication flow again to reinitialize. Note: This restarts the initial load for all tasks in the flow.
5. Repeat these steps for all affected replication flows.

Do not rely on manual truncation of target tables. The cleanup resets runtime checkpoints and stored table IDs; it does not truncate target data.
After any re-onboarding or table recreation for managed data products, reset (cleanup) and restart the relevant replication flows before resuming deltas to avoid recurrence.

• refer to: 3643099 - How to check CNV_NA_DI (Note Analyzer) in On-Premise ABAP-based systems for Datasphere Data Flows and Replication Flows
• refer to: 3498095 - Guidance on CNV_NA_DI for Replication Flows
• refer to: 2891554 - How to create a Support User in SAP Datasphere

table id mismatch, sql error 1969, replication flow, delta failure, managed data product, datasphere, remote table replaced, recreated table, runtime checkpoint, stop run with cleanup, initial load restart, cds_extraction, abap source, data integration, replication fails , KBA , DS-DI-RF , Replication Flow Runtime , Problem