Guidance on SAP Note 3255746 for Theobald Software Xtract Products

The updated SAP Note 3255746 causes significant concern among our customers and partners. The new policy states that the use of RFC modules of the Operational Data Provisioning (ODP) Data Replication API by customers or third-party applications to access SAP ABAP sources is no longer permitted. This change particularly affects users of our Xtract products that rely on the ODP component for data extraction and replication. In this blog article, we will provide more details about this change, discuss its impact on our products, and present alternative solutions so you can continue to work efficiently with your SAP data.

Update on SAP Note 3255746

SAP Note 3255746 was updated on February 2, 2024, and now states that “the usage of RFC modules of the Operational Data Provisioning (ODP) Data Replication API by customer, or third-party applications to access SAP ABAP sources (On-Premise or Cloud Private Edition) is NOT permitted by SAP.”

Customer Concerns and Impact

While SAP Notes are not legally binding, we understand that the note has caused concerns among our customers and partners that utilize the ODP component in our Xtract products for data extraction and replication, as the component makes usage of the RFC modules of the ODP API.

The SAP Note was updated again on July 7, 2024. SAP advises customers “to use SAP Datasphere for realizing data replication scenarios to move data from various SAP sources (such as SAP S/4HANA, SAP BW, SAP ECC sources etc.) into third-party applications & tools.”

Our Perspective on Data Replication Choices

In our view, customers benefit if they can choose a solution for SAP data replication that best meets their needs. This can be a third-party solution or a solution from SAP. The note limits this choice and the customers’ capabilities to replicate SAP data into third-party environments, for example data and analytics platforms from vendors other than SAP.

Xtract Universal and Alternative Solutions

Customers can use our Xtract Universal product to replicate data from various SAP sources into SAP Datasphere, or directly into third-party environments.
We recognize the critical role our software plays in your daily operations and our team at Theobald Software remains fully committed to providing reliable and fully supported solutions that are compliant with SAP’s integration guidelines.

Enhancements and Alternative Integration Components

In response to the SAP Note, we will enhance the ODP component in our Xtract products, so that it can be used with the OData API, in addition to the current functionality which uses the RFC modules. Going forward, customers will continue to be able to choose the type of integration that works best for them. This enhancement is in development, and we will offer it to customers in Q4 2024.

ODP is one of several integration components in our Xtract products. Customers can use the Table, Table CDC, Report, Query, DeltaQ, BAPI, BW Cube, and OHS which are not impacted by SAP the note. The following table shows the alternative components in our Xtract products that can be used instead of the ODP source object.

FAQ regarding SAP Note 3255746

Q: What extraction types (source objects) are impacted by the SAP Note?

A: The ODP component can be used with SAP source objects CDS Views, HANA Information Views, BW source objects, BW Extractors, SLT Server. Our tools come with several other components that are not impacted by the SAP Note and can be used as an alternative to ODP, such as the Table, Table CDC, BW Query, and DeltaQ components.

Q: Does the SAP Note impact my existing Table extractions?

A: The note has no impact on customers using our Table, Table CDC, DeltaQ, OHS, BW Cube, BW Hierarchy, BAPI and Query components.

Q: Can we continue to use the Theobald Software ODP component?

A: Theobald Software will continue to offer the ODP component in our products. We are working to enhance the component so that it can be used with the RFC protocol (current functionality) or with the OData protocol (future functionality). Customers will be able to choose the protocol they prefer.

Q: What alternatives do I have?

A: With the planned enhancement, customers will be able to continue to use the ODP component with the OData protocol. For customers using the SAPI context in ODP, they can switch to our DeltaQ component, which offers the same functionality. For customers using CDS views, they can use our Table components to extract data. For customers using BW objects, they can switch to our BW Query and BW OHS components.

Q: Can the ODP component be deactivated in your product(s)?

A: We are evaluating whether we will enable this functionality in our products.

Q: How can we be compliant with SAP guidelines and Note 3255476?

A: Customers will be able to utilize the ODP component with the OData protocol or use any of the other components such as Table, Table CDC, BW Query, or DeltaQ in our tools.

Q: What solution will Theobald Software offer, in response to the SAP Note?

A: Theobald Software will continue to offer the ODP component in our products. We are working to enhance the component so that it can be used with the RFC protocol (current functionality) or with the OData protocol (future functionality). Customers will be able to choose the protocol they prefer. Customers can use our Xtract Universal product to replicate data from various SAP sources into SAP Datasphere, or directly into third-party environments.

Q: When will ODP be available with the OData protocol?

A: We expect it will be available in Q4 2024.

Q: How is the performance of the OData protocol compared to the RFC protocol?

A: Customers should expect limitations with the OData protocol when working with larger data sets (millions of records). The performance and reliability may not be satisfactory in these scenarios, and we recommend the use of an alternative component or protocol.

Q: Will the new OData enhancement for ODP offer the same functionality as the ODP functionality over RFC?

A: Customers can expect the same functionality when switching to the OData protocol for ODP. However, customers should expect limitations with the OData protocol when working with larger data sets (millions of records). The performance and reliability may not be satisfactory in these scenarios, and we recommend the use of an alternative component or protocol.

Q: If I use the OData protocol in the future, will I get the same result set as before?

A: The ODP component can be used with SAP source objects CDS Views, HANA Information Views, BW source objects, BW Extractors, SLT Server. For these objects we do not expect any differences in the result sets for customers that are switching from the RFC protocol to the OData protocol. Our other components such as Table, Table CDC, BW Query, and DeltaQ are not impacted by the change.

Conclusion

No matter how SAP is evolving, we will evolve with new certified approaches to SAP integration. Working with us is a low-risk choice for customers and partners, as we are committed to providing reliable and compliant solutions that adapt to the changing landscape. Our dedication to innovation ensures that you will always have the best tools and support for your SAP data integration needs.