09-01-2008 10:20 AM
Hello friends,
I am trying to solve a problem that occurs within a program / transaction which can only be executed in background. The transaction in question is FPCOPARA and apparently this program cannot be executed in foreground.
If I understand well, we cannot set breakpoints within a background job and as a result we cannot inspect variable etc. during job execution. So the question is how to achieve the same goal within a batch job? How did you do it? As this is a standard SAP transacrtion, no program modification can be applied.
Your help is greatly appreciated.
09-01-2008 10:23 AM
You can debug an already running background job via SM50, "program/session->program->debugging".
Maybe this helps.
Thomas
09-01-2008 10:23 AM
You can debug an already running background job via SM50, "program/session->program->debugging".
Maybe this helps.
Thomas
09-01-2008 10:24 AM
Hi,
First u run the job. later goto SM37 and select the job and give command JDBG in command box it takes to to debug mode and shows how it runs in Background.
Sudheer. A
Edited by: sudheer Addepalli on Sep 1, 2008 2:55 PM
09-01-2008 10:25 AM
I can not see a reason why a report cant be run in foreground. Maybe you need to temper with sy-batch so that the report is believing he is running in batch.
09-01-2008 10:25 AM
Hi......
After u have executed ur batch job..
go to sm37 >>select ur job using checkbox>>enter 'JDBG' in transaction box and press enter
now debugger will start ..initial it will go through system code..after after a while the debugger will reach to your code and den you can debug the remaining report....
all the best
regards
vivek