What causes DF-SAPODP-SAPI-LIMITATION?

Delta extraction was requested for a SAPI extractor that only supports full extraction in ODP mode. The SAPI extractor requires a specific selection field (e.g. company code or date range) that is not being passed. The SAPI extractor was designed for BW-push mode and does not support direct ODP pull extraction. The extraction volume or selection criteria exceeds what the SAPI extractor can handle in a single ODP session

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

In the ADF error detail, check whether the message references delta mode — if so, switch Extraction mode to 'Full' in the source settings as a first step.. In SAP, run transaction RSA3 (Extractor Checker) for the SAPI extractor name and test extraction with the same selection parameters used in ADF — the error message will be more specific in RSA3.. Check whether the SAPI extractor requires mandatory selection fields (company code, fiscal year, etc.) by reviewing the extractor metadata in transaction RSA6.. If the extractor was designed for BW-push mode only, discuss with the SAP BW team whether there is an alternative ODP object (BW DataSource or ABAP CDS view) that can serve the same data via ODP pull.. Consult SAP Note 2752954 (ODP SAPI limitations) for known restrictions and workarounds.

Medium severitydata source

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

What does this error mean?

The ODP extraction using the SAPI context hit a known limitation. SAPI extractors were designed for BW extraction and have specific constraints when used for delta or certain extraction modes through ODP.

Common causes

1Delta extraction was requested for a SAPI extractor that only supports full extraction in ODP mode
2The SAPI extractor requires a specific selection field (e.g. company code or date range) that is not being passed
3The SAPI extractor was designed for BW-push mode and does not support direct ODP pull extraction
4The extraction volume or selection criteria exceeds what the SAPI extractor can handle in a single ODP session

How to fix it

1In the ADF error detail, check whether the message references delta mode — if so, switch Extraction mode to 'Full' in the source settings as a first step.
2In SAP, run transaction RSA3 (Extractor Checker) for the SAPI extractor name and test extraction with the same selection parameters used in ADF — the error message will be more specific in RSA3.
3Check whether the SAPI extractor requires mandatory selection fields (company code, fiscal year, etc.) by reviewing the extractor metadata in transaction RSA6.
4If the extractor was designed for BW-push mode only, discuss with the SAP BW team whether there is an alternative ODP object (BW DataSource or ABAP CDS view) that can serve the same data via ODP pull.
5Consult SAP Note 2752954 (ODP SAPI limitations) for known restrictions and workarounds.

Frequently asked questions

What is SAPI and how is it different from other ODP contexts?

SAPI is the classic SAP extraction framework for BW DataSources (e.g., 0FI_GL_14). SAPI extractors were designed to push to BW; ODP allows pulling from them but with more restrictions than ABAP CDS views or BW InfoProviders.

Can I replace a SAPI extractor with an ABAP CDS view for the same data?

Often yes — many SAPI extractors have ABAP CDS view equivalents in S/4HANA. Check with your SAP team for available CDS views; the ABAP_CDS context has fewer ODP limitations than SAPI.

How do I test a SAPI extractor in SAP before configuring ADF?

Use transaction RSA3 (Extractor Checker). Enter the extractor name, set Update mode to 'Full' or 'Delta', and run Extraction. An RSA3 failure message directly corresponds to what ADF will encounter.

Will downstream Power BI datasets be affected?

Yes — the pipeline fails without loading data. Dependent datasets will show stale data.

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