Setting RFC Bit Options in
SM59In transaction SM59 you can make the following settings after selecting a destination:
· Under Special Options -> Special Flags, you can activate options for a trace and slow RFC connections.
· When you choose RFC Bit Options, you can set various RFC bit option flags.
Note that you have to be in ’change’ mode if you want to select changes.
If you are in
’display’ mode, all checkboxes are not accessible and appear
grayed out. Use the icon
to switch between 'display’
and ‘change’ mode.

The settings for the RFC bit options are as follows:

Each time you change one of these settings, the following warning appears:

When you choose Info, you see a more detailed description of the possible bit options.
This dialog box appears if your
current selection is different from the last setting saved in the table RFCDES
(however, if no checkboxes are selected, no dialog box appears).
When you choose Enter, you can choose from one of four options:
Cancel: Your current settings are reverted back to the settings saved in the table RFCDES.
Info: You see information about the next steps you can take.
Reset: All settings are reset and the RFC options are initialized.
Yes: Choose Yes to accept the new settings. You then save the new settings to the table RFCDES by choosing Save.
If you choose Enter, you go back to the previous screen if you have not changed the value for the
RFC option saved in the table RFCDES.
When you deactivate the delta manager, the complete contents of the table are sent back from the called function module instead of only the modified table rows being sent back. Depending on the system and the function module, this can increase the amount of data that is sent, which can affect performance.
The hex value of this bit option is 00000001.
This option enters additional statistics information for the regular RFC traces. This enables you to detect bottlenecks if you experience performance problems. However, performance can also be affected by generating this statistics information.
The hex value of this bit option is 00000002.
This option deactivates the compression of the function module tables. This means that tables are no longer compressed before they are sent, which places more load on the network. Dropping the compression can improve performance slightly, but this is difficult to predict.
The hex value of this bit option is 00000004.
This option is set automatically. It activates the FastMemoryChannel as a transmission channel for SAPJ2EE instead of CPIC.
Never change this option
manually.
The hex value of this bit option is 00000010.
When you use n<tcode> to call a transaction in an RFC context, the connection is broken. You can use this option to retain the connection. Once the remote RFC context is disconnected, the function module parameters are no longer transported to the caller.
The hex value of this bit option is 00000020.
This option prevents you from using n<tcode> to call a transaction in an RFC context. Executing the ABAP language elements LEAVE TO causes an ABAP runtime error.
The hex value of this bit option is 00001000.
You can use this option to activate the ABAP runtime analysis for the remote RFC context. In the target system, you can then use transaction SE30 to analyze the logged runtime traces for the relevant RFC user.
The hex value of this bit option is 00000040.
The delta manager is used to optimize performance. It checks whether the server has made changes to a table and only sends back modified data records, if possible. If the volume of changes is high or if the delta manager has been deactivated, then the whole table is sent. You can use the delta manager trace to see which table changes have been made and how these changes are handled by the client and server.
Delta manager traces can be highly
intensive, depending on the table. Therefore, only use this option after
discussing it with SAP.
The hex value of this bit option is 00000080.
If no logon is specified by an external program when an RFC is executed, the instance language is used as the default logon language, and not the user language entered in the user master data. When you set this option, the user language is used as the default.
The hex value of this bit option is 00000100.
If you choose this option, the language from SM59 is used to determine the communication code page and not the local logon language. This option only applies to Unicode systems.
The hex value of this bit option is 00000200.
If you use HTTP debugging (external debugging) and the profile parameter rfc/ext_debugging is not active (if it does not contain the value 2 or 3; see transaction RZ12), then you can use this option to activate external debugging for this destination explicitly.
The hex value of this bit option is 00000400.
You can only set one of the flags under
Remote Session
Handling.
If multiple bit options are selected,
the individual hex values are totaled.
Under Remote Session Handling, you can activate the following options:
1. Retain Connection After “/n” in Target System
·
2. Prevent Execution of “/n” in Target System
·
Under Special Options -> Character Width in Target System, you can choose between non-Unicode communication and Unicode communication. The default is non-Unicode.
Each time you change the Unicode setting, you
are prompted to run a Unicode test. To run the Unicode test, choose
Unicode
Test in the
toolbar.
Under Special Options -> Character Conversion, you can specify whether conversion errors cause short dumps. The default is Ignore Errors.