Note 413708 - Current RFC library

Summary
Symptom
This note provides information about the classic RFC library.  As of SAP NetWeaver 7.10, a new RFC library (and RFC SDK) has been released that is incompatible with the classic RFC library. This library is called "SAP NetWeaver RFC Library" (see Note 1025361).

After the maintenance end of SAP Release 7.10 (March 31, 2016), we no longer support the classic RFC SDK or the classic RFC library.
This end of maintenance also applies to SAP Releases 7.11 and 7.20.

Since the release of the downward compatible kernel 720 (see SAP Note 1629598), only the RFC library 7.20 is still delivered and maintained. The platforms supported as of this release are listed in SAP Note 825494.

The RFC library is upward and downward compatible on Unix and MS Windows platforms. This means that you can use the current RFC library to communicate with both older and newer R/3 Systems.

The RFC library is downward compatible on OS/400 and OS/390, but may not be upward compatible. This is due to the technical features of this operating system (signature management) and does not concern the function. If an RFC program is linked to a later version of the RFC library than the version installed in the system, starting the RFC program then fails with "signature violation".

Further libraries required by the RFC library
The Unicode RFC library requires additional libraries. For more information about this, see Notes 522119 (libsapu16), 566334 (libsapu16 on Windows) and 519753 (ICU libraries).

Where can I download the current RFC library?
The current RFC library is available from the SAP Software Distribution Center under

   'http://service.sap.com/swdc'

To download it: Navigate as follows in the frame on the left-hand side of the screen -
-> SAP Support Packages and Patches
  -> Browse our Download Catalog

Then, in the right-hand frame, choose:

Support Packages and Patches
  -> Additional Components
    -> SAP Kernel
      -> SAP KERNEL <32/64-BIT [UNICODE]>
        -> SAP KERNEL 7.20
          -> <your platform>
            -> #Database independent

The file librfc_XX-yyyyyyyy.SAR contains the RFC-library.

The unpacking procedure is performed with SAPCAR. SAPCAR is described in Note 212876. For information about replacing the (non-Unicode) RFC library (librfc32.dll) on Windows platforms, see Note 336693.
Which corrections are included in the RFC library currently available?
A note is provided for every correction and this note describes which problems are solved with the correction. You can access this list of corrections with the related notes using the info file. To display the info file, navigate to the RFC library on SAP Service Marketplace and choose the "Info" icon (on the right-hand side next to the "Patch Level" field).
How are versions created for the RFC library?
Version creation comprises the following parts:
           Version - This is the SAP Basis Release.
           Patch number - This is the current patch level of the Basis release.
           SAR archive patch level - This refers to the digits 'XX' in the file name 'librfc_XX-yyyyyyyy.SAR'. This number is incremented with each new patch version. This information is only available during the download and has no relation to the version and patch number details.
How can I check the version of an RFC library?
You can check the version using the 'what'- on Unix platforms, or using the 'strings'- command on Linux as follows:
           'what librfccm.<dll extension> |grep LIBRFC'
           'strings librfccm.<dll extension> |grep LIBRFC'
           
On Windows platforms, you can determine the version using the following steps:
           with an installed Unix toolkit using a DOS box
                    'what librfc32.dll |grep LIBRFC'
           using the DOS box (or console):
                    find "LIBRFC" librfc32.dll
           with Windows Explorer:
                    Start Windows Explorer
                    Select librfc32.dll (or librfc32u.dll).
                    Right mouse-click ->Properties->Version

Compiling RFC-enabled programs is described in Notes
           11682 - Compiled from RFC programs
           118227 - RFC described as "thread safe shared library" on UNIX.
Reason and Prerequisites
Not applicable
Solution
A solution is not required.
Header Data


Release Status:Released for Customer
Released on:08.05.2013  07:16:50
Master Language:German
Priority:Recommendations/additional info
Category:Consulting
Primary Component:BC-MID-RFC RFC
Affected Releases
Release-Independent
Related Notes


 
1793690 - SAPLogonControl timeout in BEx applications
 
1670328 - RFC tracing can not be turned off
 
1491669 - HRE: SAP PLM Integration Unicode character sets
 
1319517 - Unicode Collection Note
 
1178752 - Short dump CALL_FUNCTION_NOT_FOUND and conversion problem
 
1162662 - RFC Lib: Password change during connection setup
 
1155814 - "Symbol not found" errors with RFC library on Solaris
 
1144510 - RFC library does not deliver any version information
 
1090204 - Memory Leak in libRFC
 
1084953 - Correct code page when receiving MDMP tables using RFC
 
1084757 - RFC Patch Collection 33 2007
 
1032461 - MDX parser does not start
 
966645 - Unicode executables and corrupt UTF-8 in call or environment
 
955397 - RFC SDK on linux
 
916775 - Core: Program terminated with signal 10, Bus error.
 
915482 - DB2-z/OS: Automating DB failover
 
910182 - Importing environment variables not thread save
 
885058 - EasyDM: Unicode versions are required
 
878860 - RFC tracing for ABAP-to-external communication
 
877979 - RFC tracing for external-to-ABAP communication
 
849112 - Unicode communication between big and little endian systems
 
825494 - Platforms supported by the RFC SDK
 
817854 - RFC using SNC secure connection
 
762861 - RfcListen/RfcDispatch returns RFC_FAILURE instead of RFC_CLO
 
758210 - RFC/CPIC Logon Failed, Reason=2,Type=S in SM20
 
730844 - sapstartsrv.exe fails after exchanging librfc32u.dll
 
684106 - Microsoft runtime DLLs
 
676938 - Known problems with the RFCEXEC program
 
635083 - RFC fixed invalid clearance of allocated memory
 
633441 - Runtime analysis of RFC calls
 
619060 - QCI: New RFC server installation guide
 
608382 - Avoid splash screen when SAPGUI is started using RFC
 
607992 - Invalidation of the RFC links by ABAP exception
 
552646 - Sapshortcut: no Scripting, no Sessions in Saplogon menu
 
522119 - Shared library libsapu16 (DLL for Unicode programs)
 
519753 - Problems with ICU shared libraries
 
505712 - SAPphone Server: service is running but no longer accessible
 
447975 - TeaLeaf BW Extractor Service RFC Connection Failure
 
386600 - Availability of RfcSetTimeout APIs in 46D
 
336693 - Replacing or installing librfc32.dll on Microsoft Windows
 
212876 - The new archiving tool SAPCAR
 
27517 - Installing RFCSDK

No comments: