Modernized SAP RFC Interface
Applies to: dab Nexus 1.18 and later
With the release of dab Nexus 1.18, the internal SAP interface has been modernized. This new communication layer defines how dab Nexus interacts with SAP systems and executes RFC calls. The goal is to provide a future-proof, stable, and high-performance integration based on current SAP technologies.
What are the implications of this change?
The technical modernization introduces several important aspects to consider when upgrading to version 1.18:
End of Support for the “Classic RFC Library” (librfc32)
Starting with dab Nexus version 1.18, the legacy SAP RFC library (librfc32) is no longer supported. SAP officially discontinued this library on March 31, 2016 (see the SAP Community post).
Instead, dab Nexus now exclusively uses the modern SAP NetWeaver RFC Library (sapnwrfc). This library must be available on the dab Nexus application server to ensure continued communication with SAP systems.
Recommendation: Migrate to 64-bit Components
To ensure the long-term stability and compatibility of your setup, we recommend providing all SAP-related resources—especially:
- SAP GUI
- RFC libraries
- and, if applicable, other SAP client components
in their 64-bit versions.
This helps avoid compatibility issues with future releases and improves overall performance.
Verification of SAP Authorizations
As part of the update, please review the authorizations of the SAP user used for data extraction:
Function Module | Purpose | Status |
DDIF_FIELDINFO_GET | Required to read table metadata (e.g., field information) — see SAP Community post. | Required |
STFC_PERFORMANCE | Enables the new benchmark function for performance analysis. | Recommended (optional) |
What should administrators do?
- Ensure that the SAP NetWeaver RFC Library (sapnwrfc) is installed on the dab Nexus server.
- Verify that there are no dependencies on librfc32.
- Use 64-bit versions of all SAP-related components.
- Review and, if necessary, adjust the SAP user authorizations used for extraction.
