Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from TerryB on Mar 22 at 12:47 PM Tcode SRDEBUG is designed to make that sort of "brute-force" technique unnecessary. If you are having trouble getting SRDEBUG to work, make sure that the user account used on the RFC call is a dialog user, and that it is set to use the new debugger by default. If the RFC user is set to use the classic debugger then SRDEBUG will not work.
Cheers,
Terry
| | | ---------------Original Message---------------
From: Zdeno
Sent: Thursday, March 22, 2012 12:38 PM
Subject: Subsequent RFC Calls Fail to Update DB
Hi,
Another crazy idea:
If it's no possible to external break the RFC function and the call is not very frequent, think over inserting a deadlock loop conditioned by if it's testing system and internal lv_exit variable which can be modified in active debugging. Then wait it in transaction SM50 and try to debug it.
Zdeno |
| Reply to this email to post your response. __.____._ |   _.____.__ |
