SAP Basis Tech Supports

Symptom
The syslog contains the “Execute rollback” entry.
Other terms
RFC, “Execute rollback”, ThIRollBack, roll back
Reason and Prerequisites
The message “Execute roll-back” appears because one of the following messages is displayed when you execute a function module:
a, e or x message.
You may then find the following entry, for example,in the dev_w file, indicating the cause of the error:
A RFC * AUTHORITY-CHECK PROG: SAPLBBPM_46
A RFC * AUTHORITY-CHECK FUGR: BBPM_46
A RFC * AUTHORITY-CHECK FUNC BBP_46A_DOCUMENT_UPDATECHECK
…..
Y ===> ===> ===> ===> ===> message: ERX E0 062
The above error indicates that an error message of the class E0 and message number 062 has occurred (the error text can be found in transaction SE91). You also find out that the error message happened in the main program SAPLBBPM_46 and in function module BBP_46A_DOCUMENT_UPDATECHECK.
As a result of these messages, the user context in the RFC server is rolled back. As a result, the roll-back message “Execute roll-back” is entered in the syslog.
Remark: The following entry may also appear in the dev_w filein association with the “Execute roll-back” message in the syslog:
Y ===> ===> ===> ===> message: JCB <Message class> <Message No.> .
Solution
If the error does not occur very often (less frequently than every five minutes), you can analyze the problem as follows depending on the R/3 release:
R/3 releases older than 6.20:
Set the profile parameter rfc/dump_connection_info = 2 and restart the R/3 system (unfortunately the profile parameter is static).
The next time the error occurs in syslog, you will find the number of the affected dialog work process from the syslog as follows:
Time Type No Text
09:30:00 DIA 2 Execute rollback
Now you can go to the file dev_rfc2 to find out the reason for the rollback that occurred at 09:30.
R/3 releases higher than 6.20:
As of version 6.20 and higher you can analyze the error scenario as follows:
Enter the profile parameter rfc/option_list in transaction RZ11. Set the value for the parameter to “,D=2″ (without a ” character, but using the comma [,] as the separator) or add “,D=2″, if other assignments were already entered in the profile parameter.
If the error occurs in syslog, you can find the error in the affecteddev_rfc fileas described under “Cause and prerequisites”.
After you analyze the problem, replace the entry “,D=2″ in the profile parameter rfc/option_list with “,D=-”.

If the entry “Execute roll-back” appears frequently in syslog, you can analyze the problem as follows:
Since an error message is logged in the DIA work processes with an activated trace, you should perform the following steps for the troubleshooting:
1) Delete the R/3 RFC trace
SM59 –> RFC –> Delete traceSM50 –> Process –> Trace –> ResetSMGW –> Goto–> Trace –> Gateway –> Reset file
2) Increase the trace level for the DIA work process type in the R/3 System
SM50 –> Process –> Trace –> Active componentsIn transaction SM50, set the trace level for the “DIA” work process type for the following components to “2″:M (Task handler)A (ABAP proc.)Y (Scrn. proc.)
3) Wait for the “Execute rollback” entry to appear in the syslog

4) Reduce the trace level for the DIA work process type in the R/3 System
SM50 –> Process –> Trace –> Active componentsIn transaction SM50, set the trace level for the “DIA” WP type to “Default values”.
5) Display RFC destination and gateway trace
Log on to the system and call transaction SM59.
SM59 –> Trace –> Display traceIn the menu, select “System –> List –> Save –> Local file” and save the list in an “unconverted” format.Call transaction SMGW.
SMGW –> Goto –> Trace –> Gateway –> Display fileIn the menu, select “System –> List –> Save –> Local file” and save the list in an “unconverted” format.
6) Send the already generated RFC traces to SAP
Transfer the trace files of the DIA work processes and the traces from step 5) to SAP, as described in Note 40024.