What causes DF-SAPODP-SessionTerminate?

The SAP system hit a session idle timeout and terminated the RFC session during a long-running extraction. A SAP system restart or rolling upgrade interrupted an active ODP session. Network instability between the Self-Hosted IR host and the SAP application server caused the RFC connection to drop. The SAP dialog work process handling the ODP request was killed due to a runtime or memory error

How do I fix DF-SAPODP-SessionTerminate?

Check SAP transaction SM04 (User Sessions) or SM50 (Work Processes) for terminated sessions during the failure.. In SAP, check transaction SM21 (System Log) for RFC-related session termination messages around the time of the ADF failure.. Review SAP RFC timeout parameters (rdisp/max_wprun_time, rfc/connection_timeout) with the SAP Basis team — increase timeouts if large extractions consistently exceed them.. Check the network stability between the Self-Hosted IR host and the SAP server — run a sustained ping or traceroute to detect packet loss.. If the error started after a SAP maintenance window or rolling upgrade, wait until the SAP system is stable and retry.. For very large ODP extractions, use the rowsPerPage setting in the ADF source to reduce the per-session data volume.

Medium severitydata source

Power BI Refresh Error:
DF-SAPODP-SessionTerminate

What does this error mean?

The RFC session between ADF and SAP was terminated mid-extraction — due to a session timeout, a SAP system restart, or a network interruption that dropped the RFC connection.

Common causes

1The SAP system hit a session idle timeout and terminated the RFC session during a long-running extraction
2A SAP system restart or rolling upgrade interrupted an active ODP session
3Network instability between the Self-Hosted IR host and the SAP application server caused the RFC connection to drop
4The SAP dialog work process handling the ODP request was killed due to a runtime or memory error

How to fix it

1Check SAP transaction SM04 (User Sessions) or SM50 (Work Processes) for terminated sessions during the failure.
2In SAP, check transaction SM21 (System Log) for RFC-related session termination messages around the time of the ADF failure.
3Review SAP RFC timeout parameters (rdisp/max_wprun_time, rfc/connection_timeout) with the SAP Basis team — increase timeouts if large extractions consistently exceed them.
4Check the network stability between the Self-Hosted IR host and the SAP server — run a sustained ping or traceroute to detect packet loss.
5If the error started after a SAP maintenance window or rolling upgrade, wait until the SAP system is stable and retry.
6For very large ODP extractions, use the rowsPerPage setting in the ADF source to reduce the per-session data volume.

Frequently asked questions

Can I prevent SAP from timing out long extractions?

Yes — work with SAP Basis to increase RFC session timeout parameters (rdisp/max_wprun_time or rfc/connection_timeout). Alternatively, reduce per-session extraction volume with a lower rowsPerPage value in the ADF ODP source settings.

Does SessionTerminate indicate data corruption or an incomplete load?

The extraction was interrupted — no data corruption in SAP, but ADF did not receive all records. Check the activity run for the row count written; the target table may contain a partial load.

How do delta extractions behave when a session is terminated?

ODP delta tracks watermarks on the SAP side. If the session terminates, the subscription may be left open. Re-running resumes from the same point; if stuck, reset the subscription with your SAP Basis team.

Will downstream Power BI datasets be affected?

Yes — if the pipeline fails due to session termination, the target table will have incomplete data. Power BI datasets refreshing from that table may show incorrect totals or missing records.

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