‎2007 Nov 15 10:23 AM
Hi,
We have a batch job which picks up 64 status Idocs and calls a customised function module and posts the Idocs. However we have had an instance where the batch job failed (there is a dump in ST22) due to some data conversion issues in the function module for one of the Idocs.
My questions are:
1) How do I execute the batch job manually in a way that it does not pick up the Idoc which caused this problem, so that the other Idocs are posted.
2) How do I find out which Idoc caused the problem as the log does not give the Idoc number
Any help would be appreciated.
Thanks in advance.
Mick
‎2007 Nov 15 10:27 AM
u can debug the background job where it failed,
t.code i am not sure it may be using sm50 or sm52
‎2007 Nov 15 10:27 AM
u can debug the background job where it failed,
t.code i am not sure it may be using sm50 or sm52
‎2007 Nov 15 11:21 AM
Thanks Madhavi.
When I go to SM 50 and select Program/Mode>Program>Debugging after selecting the process, nothing happens. Could you explain what steps do I need to take to go into debug mode?
‎2007 Nov 15 11:44 AM
Hi Mick
Debugging may not be possible for cancelled jobs using SM50..(yes for active jobs). Instead try <b>selecting</b> the cancelled job ..and type JDBG in the command field (remember do not type "/n") and press enter.. Keep pressing F7 till the relevant area is encountered... Try and let me know if it works...
Also in the short dump check "Chosen variables" section...
Regards,
Arun
‎2007 Nov 15 11:55 AM
goto SM37, select ur job and type in JDBG in the command prompt u will get into debugging mode