> ## Documentation Index > Fetch the complete documentation index at: https://docs.maia.ai/llms.txt > Use this file to discover all available pages before exploring further. # SAP Note 3255746 and its impact on SAP ODP data extraction export const maia = "Maia"; SAP Note 3255746 restricts third-party use of the RFC modules in the SAP Operational Data Provisioning (ODP) framework. This affects how you extract data from SAP systems using {maia}'s [SAP ODP](/docs/components/sap-odp) component. This tech note explains the background, what's changing, and the alternatives available to you. *** ## Background The SAP ODP framework enables real-time data extraction from SAP ERP and other SAP systems, and is widely used. It provides a unified and scalable way to access and integrate data into analytics, reporting, and decision-making workflows. The framework lets external data consumers subscribe to datasets that are already modeled for analytical consumption, and it supports delta-enabled datasets, which significantly reduces the volume of data you need to refresh each day. *** ## What SAP Note 3255746 says SAP first published Note 3255746 in 2022, explaining that third parties could use SAP APIs for the ODP framework, but that these APIs were unsupported and intended for internal use only. On February 2, 2024, SAP updated the note (version 4) to state that customers and third-party applications are no longer permitted to use ODP APIs to access SAP ABAP sources. SAP also warned that it may restrict and audit unpermitted use of this feature. On July 7, 2024, SAP updated the note again, advising customers to use SAP Datasphere for data replication scenarios that move data from SAP sources into third-party applications and tools. The 2026 update to this note formalized SAP's position on the use of *non-published APIs*. *** ## What's changing On June 9, 2026, SAP released [security patches](https://support.sap.com/en/my-support/knowledge-base/security-notes-news/june-2026.html) that block unrestricted calls from non-SAP applications—including affected Matillion connectors—that rely on the ODP-RFC interface. SAP provides a temporary option to revert to unrestricted ODP-RFC calls. According to [SAP's Operational Data Provisioning (ODP) update public FAQ](https://www.sap.com/documents/2017/06/66673acb-c37c-0010-82c7-eda71af511fa.html): > *SAP provides a time-limited option to revert to unrestricted ODP-RFC calls. This flexibility will expire on December 2026. More details are documented in the relevant SAP Note 3731818, published on June 9, 2026. Customers should be aware that the identified security risk will persist until the security patch has been installed, and the decision to temporarily revert to unrestricted ODP-RFC calls is at the customer's risk.* This means you may be able to temporarily roll back the restriction and continue using ODP to extract your data, but only until December 2026. *** ## What you need to do * **Review the latest SAP notes.** Independently review SAP Note 3255746 (the reclassification notice) and SAP Note 3439624 (the self-assessment tool) through the SAP Support Portal at [support.sap.com](https://support.sap.com/en/index.html). Raise any concerns or feedback through the appropriate SAP channels. * **Audit your environment.** SAP's self-assessment tool (SAP Note 3439624, available since April 13, 2026) helps you identify all current ODP-RFC usage across your systems. The Matillion SAP ODP connector shows as *unpermitted*, meaning the security patch blocks it. The Matillion SAP OData connector shows as *permitted*, meaning it continues to work as expected after you apply the SAP June security patch. * **Evaluate the Matillion OData connector.** We continue to enhance our connectors, and we're planning to release a new SAP connector later this year that may prove to be a viable alternative. * **Work with Matillion.** Before you implement the SAP June security patch, discuss your use case with your Matillion representative. We can help you understand the impact of these SAP restrictions on your pipelines, and determine how best to minimize disruption to your business processes before the December 2026 deadline. *** ## Matillion's position Matillion is committed to: * Remaining transparent about SAP's guidelines, both on what's permitted and what's recommended. * Continuing to maintain, and further enhance, the SAP ODP components in our products. * Recommending that you keep your Matillion SAP data extraction as-is for now. The OData Services option remains available if you have concerns. * Working with third-party partners to investigate alternatives to the existing ODP component, to deliver solutions that work within the new SAP guidelines while delivering the same, or better, data movement capabilities from SAP into your business systems. *** ## Alternatives to SAP ODP The following alternatives are available if you need to move away from the [SAP ODP](/docs/components/sap-odp) connector. ### SAP OData services via SAP Gateway Use the [OData Query](/docs/components/odata-query) component to connect to SAP systems using standard RESTful requests. Data extraction using OData allows for easier retrieval and manipulation of data, and can enable real-time data access and integration. However, this option is primarily intended for transactional, real-time data—it wasn't built for bulk data extraction. For best performance, consider breaking large datasets into smaller parts and loading them step by step. ### SAP NetWeaver Use the [SAP NetWeaver Load](/docs/components/sap-netweaver-load) component to connect using this proven technology, which predates ODP and has been in use for many years. This makes it reliable and well understood by SAP professionals. SAP NetWeaver sometimes requires additional setup and configuration, but it's an excellent choice for established environments that can take advantage of its extensive integration options. ### JDBC from SAP HANA Use the [JDBC](/docs/components/jdbc#sap-hana) component to connect to SAP HANA using a standard database connection, letting you interact with SAP HANA and retrieve your data as tables and columns. Connecting using JDBC is subject to the detailed conditions in your SAP HANA license, so make sure your license allows this. You're also likely to find that interpreting the available database objects requires knowledge of SAP HANA internals. SAP's rules also state that technologies such as SLT Replication Server, Master Data Integration ABAP Adapter, SAP HANA log-based replication, and SAP Database Trigger must not be used to move data out of SAP. *** ## Summary The June 2026 security patch moves SAP one step closer to potentially removing ODP RFC-based data extraction entirely. However, the option to extend data extraction until December 2026 gives you time to develop an alternative strategy for SAP data extraction. If you have questions or want to discuss your specific configuration, contact [Matillion support](/docs/guides/getting-support) or your Customer Success representative.