Debugging a Background job

Hi everybody,
what are the different wasy to debug a job which is assigned in background. Can we debug a back ground which is running, or we can only debug the completed jobs. thanks in advance,
santosh.

hi,
refer all the links
how to debug a background program
Debugging of program running in background
how do we debug jobs in background when the peogram is running

Similar Messages

How to debug the background job in ABAP

Hi Guys,
Can anyone let me know how to debug the background job in ABAP.
Thanks in advance
peter

Hi,
Goto SM37 and see the log if any is there and based on that you can check the code.
you can't debug background job.
Create a Variant for the Program and
Schedule JOB in background:
Go to SM36 create a Job
enter Program and Variant for that program in STEP..
click on Start Condition
Click on DATE and TIME enter date scheduled Start and END times
click on Period Values
Click on HOURLY/WEEKLY etc
CLick on RESTRICTIONS also to use further criteria.
so your job will be scheduled and run as per your requirement.
and in SM37 Transaction check the status of that JOB
Check this link for scheduling jobs..
http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm
Check this
http://jplamontre.free.fr/SAP/Debug%20background%20process.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/abap+debugger&
Regards,
Padmam.

How tio debug a background job

Hello Experts ,
please tell me is there any way to debug a background job ( a report submitted in a background).

You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
command line ( no '/' ), put the cursor on the job and press enter - will
take you to the job in debug mode.
You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
Steps
1. Create variant called BACKGROUND for program to be debugged.
2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
3. Execute transaction SM50.
4. Select process that runs ZDEBUGBG.
5. Goto 'Program/Session' 'Program' 'Debugging'.
A se80 debug session will open.
6. Change variable W_EXIT to 'E'.
7. Step thru (F6) until ZWBTEST comes up.
1. Go to Transaction SM66 and find your work porocess.
Select the line work process is on and click on the Debugging button.
If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
goto SM37 and from Program menu(not sure.. try other menu's)
-->Catchjob . it will goto the active job in debugging mode.
1. select active job in sm37.
2. type "jdbg" command in command field.
No need to type /n or /o .
3. Double click the job , it will go in debug mode.
OR
1. Go to sm50 .
2. place the cursor on active job.
3. goto program mode> program> Debugging.
Check this
http://jplamontre.free.fr/SAP/Debug%20background%20process.htm

How to Debug a BackGround Job

Hi all,
Can any one tell me how to Debugg a BackGround job in 4.7 version.
I used something like JDBG in SM37 but its not working.
Is there any process for this....

Hi,
You can do using SM50 transaction.
Please check this link
http://www.allinterview.com/showanswers/56422.html
Best regards,
raam

Report without input screen working diffrently in debugging and background

hai,frds
I have one report without input-screen,But it is working diffrently in background and debugger.
please help me for this and i am bapi inside the program to create entries.but
if its in debugging it is crates corectly but if is in back ground it not working cooetly bapi working one time only.
plese help me for this.
Moderator Message: Too much of text-speak/sms-speak. Thread Locked. Write complete words and check their spellings using the Spell-Check tool in the editor here.
Edited by: kishan P on Jan 19, 2012 4:40 PM

HI,
In SM37,Put the cursor on the Job, Type 'JDBG' in Command line and press Enter.
You can able to debug your Background job now.
Find out where it is going wrong.....
how to debug background job

It has an error when run a program in background job

Dear Expert,
we have a program
when run it in background,it has a error "Error during import of clipboard contents" but when run it normally(run in front workbench se38 or run the t-code),everything is ok.i've used typingJDBG in the command box to debuge the background job,there has no error.
whould you like to tell me what had happen? thanks a lot!
addition: the program used a function ALSM_EXCEL_TO_INTERNAL_TABLE
Thanks & Regards,
Kerry
Edited by: Kerry Wang on Aug 24, 2009 2:12 PM
Edited by: Kerry Wang on Aug 24, 2009 2:14 PM
Edited by: Kerry Wang on Aug 24, 2009 2:14 PM

Hi,
You cannot use FMs to get data directly from the presentation server when program is executed in the backgroud.
Check the thread : GUI_DOWNLOAD
Regards,
Himanshu

Issue in background job for call transaction

Dear All,
I am facing a strange issue with call transaction. I need to add some Purchase requisitons in the APO using Call transactionmethod. It is working fine In All screen mode and No Screen Mode. But when I schedule the program in BAckground processing it is not wokring fine. It is not creating any Purchase requisitioins. When I debug the background Job it is creating Purchase requisitions.
Please find the code below
    DATA: l_wa_params TYPE ctu_params.
    l_wa_params-dismode = l_c_mode.
    l_wa_params-updmode = 'A'.
    l_wa_params-defsize = 'X'.
    l_wa_params-racommit = 'X'.
    CALL TRANSACTION '/SAPAPO/RRP3' USING fp_i_bdcdata OPTIONS FROM l_wa_params
                                        MESSAGES INTO l_i_bdcmsgcoll.

Hi,
I have exactly the same problem with transaction /SAPAPO/RRP5.
Thanks in advance for your help,
Yannick CAREL

FM ARCHIVE_SCHEDULE_JOB giving dump as background job?

Hello Everyone,
I am scheduling a report in SM37 which consists of FM ARCHIVE_SCHEDULE_JOB.
And based on the output of FM, some Ztables are updated and some jobs are created in sm37.
Now, when i debugged the background job, i found out that Fm is giving Dump 'NO_RUNTIME_INFO' since sy-batch is not initial.
Due to which Ztables are not updated but the jobs are created....
Can anyone please help me what should i do on this case?
Edited by: Suruchi Razdan on Jun 2, 2011 9:45 AM

Hi Akshay,
II have copied the Std workflow WS20000075 into a custom one and in the latest end tab, i have selected "Workitem creaton" for Refer Date/Time field and given 5 mins. I have deactivated the workflow in which i have created the containers for date and time and used "Expresion" for latest end and also commented the zmethod in delegated object. Even now also the job is getting cancelled with the same error.
Any idea why is it happening ?
regards,
Trimurty

Background job not run properly

Hi,
When an infopackage is triggred through process chain in BI a background job will be exeuted at R/3 to fetch data from R/3.
But the bakground job did not execute properly hat is it did not fetch any data but ot finished.
But when the infopackage is executed manually the background job fetches the data from R/3.
Why the job is not fetching data when triggered through process chain.
Please help me to sole this issue.
Regards,
Indhu

Hi Induja,
In your case, you will have to debug the background job that is activated through BI. Check if proper data is coming from BI.
You can only debug a background job if it is created under your user id. Thus, to debug the job you first have to own it and then debug by selecting it and either typing 'JDBG' in the command field or through menus available on the top.
Job overview transaction code - SM37.
Hopefully the issue is in Development/Test/Quality system and not in Production.
Hope that helps!.
Regards,
Saba

Background job not generating spool

Hi all,
I am calling a report from another report. The called report will display the final output list.
Here, the called report will be executed in background.
here the job is completing but the spool is not generated.

Hi,
It seems that the final internal table which has the output data is empty & hence write statements are not executed ( assuming all the write statements are inside a loop).
Place one write statement outside loop like
write :/ 'Following is the result :'.
& check whether spool is generated. If yes, then the problem is of empty internal table.
You can select the job in SM37 & type JDBG in command prompt to debug a background job.
Debug & check the issue.
Best regards,
Prashant

Change internal table values in background job

Hello All,
Currently we have a report which is running in background job.
Because of error in one PO (error in header status), the job is getting cancelled in production.
Is there any way, we can exclude this PO in debugging from the internal table.
The report should run in background, the requirement is exclude the PO from internal table and the background process should run as normal after excluding that PO.
Please advise how to do this.
Thanks,
Priya

Hi All,
Thanks for your replies.
I found the following way to debug the background job helpful. Go to SM37, select the job name and do as shown below. Once you click Capture: Active job, debugger will open and we can analyze from there further.

Debugiing a BackGround Job.

Hi All,
I am facing a problem when my program is being run in the Background. As far as i know Background Jobs can be debugged by using transaction SM50. But i am unable to.
Could anyone please provide me pointers on this or could guide me on how to debug a background job. Thanks in advance for tour replies.
Regards,
Goutham.
PS: Points will be definitely awarded.

Hi Goutham
As Anversha has already mentioned, we can perform the debugging from SM50 transaction.
Steps:
1. Go to Transaction SM50.
2. <b>Select the process(check box) where your job is executing</b>.
3. Use Menupath: Program/Mode -> Program -> Debugging.
By doing this it will open a new session in debugging mode of your current execution.
<b>Also make sure that you havent occupied all sessions permitted so that the debugging window can open a new session.</b>
If the job has already finished, use transaction SM37. Display the job. Select the
job, execute command JDBG in command field. A series of
F7 need to be done until you reach your program. From
then you can debug to see how the commands are executed.
Hope the info helps you.
Kind Regards
Eswar

HOW TO DUBUG BACKGROUND JOB?

1)HOW TO DUBUG THE BACKGROUND JOB?
2) HOW TO DEBUG THE BACKGROUND JOB WHICH IS ALREADY RUNNING??
CAN YOU PLZ REPLY TO THE ABOVE TWO QUESTIONS....??? URGENT...
THANKS IN ADVANCE
SRI

Hi Srikanth,
There are two ways to achieve this:-
1. 1) Fix the break points.
    2) Create job.
    3) Go SM37
    4) Select the job and write "jdbg" in command line.
2. 1) Use Transaction SM50. This would give you a view of all the background
      processes running in the server.
   2) Choose your background process from the list and got to
      MENU "Program/Mode"->"Program"->"Debugging".
NOTE: I found the 1st was in one of the replies on SDN only and felt, its a betetr
          option than the second one. Its my perception :).
          Please award points, if you feel the query is solved :).
Thanks and regards,
Ravi .

BP Generating - Background Job

Hi @all,
I want to create my business partner by the transaction BG_GEN (automatic business partner generation, depending on the users in the R/3 System).
Everything works fine, the business partners where created and it's perfect.
But I have a question. Can I make this automatically creation with a job? I mean, can i plan a job (for example once a day), which creates business partners? So if we got a new user, thsi user will automatically been created as business partner in our SolMan?
Hope anyone could help me to do this,
thanks in advance
Michael

Hi,
It seems that the final internal table which has the output data is empty & hence write statements are not executed ( assuming all the write statements are inside a loop).
Place one write statement outside loop like
write :/ 'Following is the result :'.
& check whether spool is generated. If yes, then the problem is of empty internal table.
You can select the job in SM37 & type JDBG in command prompt to debug a background job.
Debug & check the issue.
Best regards,
Prashant

Debug Background Job

Hello Experts,
I want to debug standard T- Code 'F110' (Automatic Payment Run).
Basically wat it does is just submit one program SAPF110S
but as a background job
i.e
SUBMIT SAPF110S AND RETURN
                      USER SY-UNAME
                      VIA JOB JOBNAME NUMBER JOBCOUNT
                      WITH PARLAUFD = F110V-LAUFD
                      WITH PARLAUFI = F110V-LAUFI
                      WITH PARXVORL = XVORL.
and thats why i m not able to debug it
so how is it possible
Pls help me on this
Regards
Ravi

Hi Nagraj,
I know the standard method of debugging a program, but I am submitting a report program which is executed in Background.
I tried debugging with /h in the command field, but I am unable to debug.
I hope u have understood the question properly.
Regards,
Ravi

Debugging a Background job

Similar Messages

Maybe you are looking for