Update Debugging

[Former Member]

Hi all,

I have used a BDC Call Transaction in my User-Exit through a Function Module. This user-exit triggers only in the Update Debugging Mode, So I switch the Update Debugging On and I enter the Exit, As soon as the trigger comes to "Call Transaction", the Update Debugging Screen vanishes. Can anyone please help me in this.

Thanks

JM

[Former Member]

Hello,

Instead of switching the dedug on, try to put a break point on yoy FM or exit, this will not let you screen to vanish.

hope this helps,,

Gabriel

[Former Member]

Hi Johann,

The debugging will be switched off by some of the FM's and keywords. SO the only alternate I think in Ur case is use the mode A in the call transaction and check for the process.

[Former Member]

Hi,

I am using the MODE 'A', but the problem is as soon as the call transaction is triggered the "Update Debugging" session vanishes of and am getting a Error message in my SAP mail.

Thanks

[Former Member]

Hello,

Instead of switching the dedug on, try to put a break point on yoy FM or exit, this will not let you screen to vanish.

hope this helps,,

Gabriel

[Former Member]

Hi,

I think we cannot use CALL TRANSACTION... or SUBMIT STATEMENTS... inside a update task, that is why the statement is not getting executed and the update is ending abruptly. This is when we receive a mail to our SAP Mail ID.

The alternative can be to use a BAPI inside or try to do direct update or insert.

Please let me know if further details are required from my side.

Thanks & Regards,

Goutham.

[Former Member]

did you try like this

call transaction 'TCODE' using bdcdata MODE 'A'

update 'S'.

Reward Points if it is helpful.

Thanks

Seshu