2010 Jun 22 8:25 AM
Hi All,
I am scheduling a background job for MIGO by submitting a posting posting program which is using BAPI_ACC_DOCUMENT_POST to post the document. sometimes when I check in SM37 gets job cancelled which says 'Job cancelled after system exception ERROR_MESSAGE' and when I re-process the job the document gets posted . Due to this I am not able to debug the program. I tried increasing the wait time for the job posting but that is also not working.
Please suggest me how can I overcome this problem.
Thanks.
Shweta
2010 Jun 22 9:40 AM
Hi ,
I hope you know about JDBG. If yes then are you not able to debug your cancelled job with this command. Is it not getting displayed in sm35.
If above is not working then, try to see in st22 if you can get some description
Also see in your program that are you writing any exit , message statements.
Regards,
Uma Dave
Hi All,
I am scheduling a background job for MIGO by submitting a posting posting program which is using BAPI_ACC_DOCUMENT_POST to post the document. sometimes when I check in SM37 gets job cancelled which says 'Job cancelled after system exception ERROR_MESSAGE' and when I re-process the job the document gets posted . Due to this I am not able to debug the program. I tried increasing the wait time for the job posting but that is also not working.
Please suggest me how can I overcome this problem.
Thanks.
Shweta
2010 Jun 22 9:40 AM
Hi ,
I hope you know about JDBG. If yes then are you not able to debug your cancelled job with this command. Is it not getting displayed in sm35.
If above is not working then, try to see in st22 if you can get some description
Also see in your program that are you writing any exit , message statements.
Regards,
Uma Dave
2010 Jun 22 9:58 AM
Hi Uma,
I am able to use JDBG but when I debug using JDBG the program is re-run so it does't give me any error message in return[] of bapi. Due to this reason I am not able to check why job got cancelled.
Because when we reschedule the job , job gets successfully executed.
I checked in ST22 but it is not having any details.
Thanks.
2010 Jun 22 10:06 AM
Hi,
In the job Log, Select the Row which shows the error and click on Long Text button. Does the system shows any details?
Regards
Vinod
2010 Jun 22 10:47 AM
2010 Jun 22 12:55 PM
2010 Jun 22 12:58 PM
Hi ,are u passing same inputs when u run the Job in Foreground successfully ?
Please if all the input variables that u are passing to the job are correctly populated. Might be infirst pass some memory variable is initial and after runing the program second time that variable gets initialized to some data and hence program runs successfully. Check for such data and memory related possibilities.
Otherwise there seems no reason for such abnormal behavior.
Hope this is helpful.
Regards,
Uma Dave
2010 Jun 22 1:18 PM
Actually the job is getting cancelled very rarely. its like if 20 jobs are run 1 shows the cancel status. but if the cancelled job is executed again in foreground/background the job get finished and the posting is done successfully.
Initailly thought there is a deadlok issue .. checked but that is not the case. then increased the wit time so that if there is delay in input parameters the program will wait for it ... also provided a check to not to create job if in case input parameter is not generated.
Not getting why this ia happening.
2010 Jun 22 10:54 AM
2010 Jun 22 11:17 AM
2010 Jun 22 11:33 AM
2010 Jun 22 11:53 AM
2010 Jun 22 12:18 PM
You can check whether there is any notes available for this.