SAP Note 3255746: How to Achieve Data Integration Without ODP

SAP Note 3255746 has drawn significant attention because it defines how data must be securely extracted and replicated from SAP systems going forward. Learn how companies that have relied on RFC-based ODP integrations can adjust their processes to remain fully compliant with SAP requirements.

‍

Key Points at a Glance

• Since February 2024 (updated July 2024), SAP Note 3255746 states that customers or third-party providers are no longer allowed to use the RFC modules of the ODP Data Replication API.
• Affected: SAP ABAP sources such as S/4HANA, BW, and ECC.
• Solution: Theobald Software offers an SAP-compliant alternative via OData.
• Alternative Components: Table, Table CDC, DeltaQ, BW Cube – not affected by the note.
• Recommendation: Consider migrating to OData, set up monitoring, and use alternative components for large data volumes.

‍

Why SAP Note 3255746 Matters

‍The note is relevant for anyone transferring data from SAP systems into third-party applications or analytics platforms. RFC-based ODP integrations, common in the past, are no longer permitted according to SAP. That forces companies to adjust their integration processes.

SAP’s goal: ensure that only certified, secure extraction methods are used – across on-premise environments, cloud systems (Private Edition), and SAP sources such as S/4HANA, BW, and ECC.

‍

Current Situation in 2025/2026

‍Since the release of the note, Theobald Software has expanded its Xtract products with OData connectivity. This allows you to:

• Replicate data via OData services instead of RFC
• Load data incrementally through an OData connection to the ODP framework
• Continue using all existing components such as Table, Table CDC, and DeltaQ

Bottom line: Your SAP data can still be replicated efficiently, reliably, and in line with SAP rules.

‍

Recommendations for Your SAP Data Integration

‍If you’ve relied on RFC-based ODP until now, the following steps make sense:

1. Check Alternative Components: Table, Table CDC, DeltaQ, or BW Cube offer flexibility and performance – especially important for large data volumes.
2. ‍Migrate to OData: This is the SAP-compliant method for data replication.

‍

Alternative Integration Components in Xtract Universal

‍

All these components are not affected by SAP Note 3255746 and can continue to be used without restrictions.

‍

Conclusion

• SAP Note 3255746 is a key factor for all SAP data integrations into third-party systems.
• Theobald Software’s SAP connectors continue to offer reliable, compliant, and flexible data replication.
• Companies should review a migration of RFC-based ODP scenarios to OData.
• Components such as Table, Table CDC, DeltaQ, or BW Cube ensure efficiency and flexibility.

With these measures, your SAP data integration remains efficient, performant, and future-proof under the current SAP guidelines. More information about all Theobald Xtract products is available on our website.

‍

FAQ: Common Questions About SAP Note 3255746

Which extraction types (source objects) are affected by the SAP note?
The ODP component works with SAP sources such as CDS views, HANA Information Views, BW objects, BW extractors, and SLT servers. Our solutions offer several other components not affected by the note—usable as ODP alternatives—such as Table, Table CDC, BW Query, and DeltaQ.

Does the note affect my existing Table extractions?
No. Customers using Table, Table CDC, DeltaQ, OHS, BW Cube, BW Hierarchy, BAPI, and Query components are not affected.

Can I continue using ODP via RFC?
No. SAP no longer allows this. Theobald Software supports OData + CDC to ensure a secure migration path.

When will OData + CDC be available in Xtract Universal?
The functionality is already active in 2025: Xtract Universal OData + CDC.

How does OData performance compare to RFC?
OData delivers solid performance, especially combined with CDC. For extremely large datasets (millions of records), performance limits may appear. In such cases, we recommend using an alternative component or protocol.

What risks come with using OData?
Higher resource consumption and potential performance limits at very large data volumes. Setting up robust monitoring is advisable.

‍