What causes DF-SAPODP-SLT-LIMITATION?

Delta extraction was configured for an SLT-based ODP object that does not support delta mode through the ODP-SLT interface. The SLT mass transfer ID is not correctly configured on the SAP side for the object being extracted. The ODP subscription or pointer for the SLT source was reset and ADF is requesting data that SLT can no longer deliver in delta. The SAP SLT version does not support the ODP extraction feature being used

How do I fix DF-SAPODP-SLT-LIMITATION?

In the ADF error detail, identify whether this is a delta vs. full load limitation — switch to Full extraction mode in the ADF source settings as a first step.. Consult your SAP Basis team to verify that the SLT mass transfer ID is correctly configured and that the source table is properly replicated in SLT.. In SAP, check the SLT Monitoring cockpit (transaction LTR) to verify the replication table status and any error messages.. Verify that the SAP SLT version supports the ODP interface — SLT-ODP integration requires specific SAP Notes applied to the SLT system.. If delta is a hard requirement, discuss with the SAP team whether a BW extractor or ABAP CDS view can serve as an alternative ODP source for the same data.

Medium severitydata source

Power BI Refresh Error:
DF-SAPODP-SLT-LIMITATION

What does this error mean?

The ODP object you are trying to extract is sourced via SAP Landscape Transformation Replication Server (SLT), and the specific extraction mode or feature you are using is not supported through the SLT-ODP combination. SLT has specific constraints when exposed as an ODP provider.

Common causes

1Delta extraction was configured for an SLT-based ODP object that does not support delta mode through the ODP-SLT interface
2The SLT mass transfer ID is not correctly configured on the SAP side for the object being extracted
3The ODP subscription or pointer for the SLT source was reset and ADF is requesting data that SLT can no longer deliver in delta
4The SAP SLT version does not support the ODP extraction feature being used

How to fix it

1In the ADF error detail, identify whether this is a delta vs. full load limitation — switch to Full extraction mode in the ADF source settings as a first step.
2Consult your SAP Basis team to verify that the SLT mass transfer ID is correctly configured and that the source table is properly replicated in SLT.
3In SAP, check the SLT Monitoring cockpit (transaction LTR) to verify the replication table status and any error messages.
4Verify that the SAP SLT version supports the ODP interface — SLT-ODP integration requires specific SAP Notes applied to the SLT system.
5If delta is a hard requirement, discuss with the SAP team whether a BW extractor or ABAP CDS view can serve as an alternative ODP source for the same data.

Frequently asked questions

What is SAP SLT and how does it relate to ODP?

SAP SLT (Landscape Transformation Replication Server) is a real-time replication tool that can expose data through the ODP framework, but this SLT-ODP integration has specific constraints compared to native BW or ABAP CDS ODP sources.

Is it always possible to switch from delta to full extraction for SLT sources?

For smaller tables, yes — full extraction reads all records each run. For large tables, full extraction is impractical; work with the SAP team to configure SLT for delta ODP or consider an alternative approach.

What SAP transactions can help diagnose SLT issues?

Transaction LTR (SLT Monitoring) shows replication status; LTRS shows configuration. Check both for errors at the time of the ADF failure. Engage the SAP Basis team managing SLT for interpretation.

Will downstream Power BI datasets be affected?

Yes — the pipeline fails without loading data. Power BI datasets refreshing from this source will show stale data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide