How to debug a function module called in background task ?

[former_member332306]

I have a custom function module, which is called in during a standard process at Work Order SAVE.
The FM is called by using statement : 'Call Function <FM name> in Background task'.

To analyze the issue, I need to go inside this FM during debugging when the process is executed. I have also tried endless loops as well, the flow is stuck there but it is not visible in transaction SM50. As a result, I am not able to debug the same, and also the Order is not getting opened in Change mode.

Is there any way of doing this ?

[Sandra_Rossi]

If you do an endless loop and you don't see the process in SM50, then it's because:

• Either it's run by another application server. Use SM66 instead of SM50 to see workprocesses of all application servers.
• Or you use WAIT UP TO n SECONDS which makes it disappear from the active workprocesses during this N second(s). Instead, use an empty endless loop DO ENDDO (in debug you can jump after the ENDDO).

[kiran_k8]

Sandra,

Does that mean in this case,if it is not showing up in SM50,it will show up in SM66 ?

Do we have the option of switching into Debugging Mode by choosing the concerned workprocess in SM66,similar to what we do in SM50 ?

Thanks,

K.Kiran.

[Sandra_Rossi]

I said EITHER try SM66 if you have several application servers, OR you used WAIT UP TO n SECONDS. So, I can't tell you if it will show up in SM66, especially if the issue is the other option.

The debug option is available in SM66 from Basis 7.40. If you have a previous release, then you need to check on which application server is running your endless loop via SM66, then you switch to this server via SM51, then you start SM50.

[former_member400468]

Hi!

You can try to put endless loop DO... ENDDO and then go to SM51 and find your process and then choose Administration->Program->Debugging

Hope it's helpful

Evgeny

[former_member332306]

Hi Evgeny,

I have tried the endless loop, the background FM is stuck at the point. But it's not visible in SM50, as a result I am not able to debug the same.

Regards,
Tapas

[matt]

If your system has more than one appserver, perhaps you're logged on to the wrong server. Use SM51.