Debugging the Job

Hi Experts,
I have submitted a job in background using submit via job. Is it possible to debug the program which i have called through submit via job?
Thanks
Harshad.

Hi hrashad,
u can debug ur own job through sm37 then select ur job then type JDBG in comand line.
or
u can debug ur own active job through sm37 then select ur job then click capture: active job.
in menu baar (Job-> capture: active job).
Thanks & Regards
Rahul

Similar Messages

How to debug active jobs

Hi,
How to debug active jobs?
Thanks in Advance

Hi,
You can debug the job using :JDBG: But the only criteria, you can dubug the job if you are the creator of that job.
Regards
Maneesh Chandran

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.

Is it possible to debug a Job which already executed in the Background.

Hi Friends,
My Z program has a bug when run it in Quality System.
If I run this program in foreground to debug, its giving TIME OUT dump.
If i try to run it in Background and started DEBUG mode using JDBG.
Still one of the table fetch gives TIME OUT dump.
Is there any possibility to DEBUG the already executed job?
Regards,
VIJI

Hi,
If the job is running go to SM50..
Select the process:
In the menu..Program/session -> program -> debugging..
OR
Fix the break points.
2) Create job.
3) Go SM37
4) Select the job and write "jdbg" in command line.
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".
Regards,
Suresh Kumar

How to debug the back ground job

Hi All,
I want to debug the program, but it is taking more time so iam running it in back ground, but i need to debug the program from some particular point....is there any other way to debug the program...
Means...to run the program in background upto particular point and later i need to run it in debug mode.
Please suggest.
Thanks & Regards,
Hari

Hi,
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 and sy-batch set to 'X'.
Use SM37 to get list of jobs , type 'JDBG' in the command line ( no '/' ), put the cursor on the job and press ENTER
You are in debug mode now. Step through SAP program (press F7 couple of times) until you get to code you need.
Hope this helps u.
Thanks.

Debugging the master jobs and packages

How to do Debugging the master jobs and packages ?

Hi Mukejee,
Except for executing a SSIS package in BIDS, we can also execute a package using the following methods:
Execute SSIS Package using DTEXEC.EXE Command Line Utility
Execute SSIS Package using DTEXECUI.EXE Utility
Execute SSIS Package using SQL Server Agent Job
In each method, we can specify the package configurations for the package at runtime. For the detailed information, please see:
http://www.mssqltips.com/sqlservertip/1775/different-ways-to-execute-a-sql-server-ssis-package/
http://technet.microsoft.com/en-us/library/ms162810(v=SQL.105).aspx
http://technet.microsoft.com/en-us/library/ms141701.aspx
Regards,
Mike Yin
TechNet Community Support

How to find the Job Name in the debugging from the SM37

Hi All,
Here my problem is i want to update the Actual UOM into MM02 and if new material is coming i need to create the material and UOM in MM01.
for this requirement i am using RMDATIND standard Direct Input program and I am using Background JOB Schduling by giving name MRP_MATERIAL_MASTER_DATA_LOAD
I am getting the data into my internal table and i am successfully getting the message "JOB started" once i execute the program.
then i gone into SM37 there i found my job is completed.
but when i try to find the data has updated in MM02 or MM01, here i could not found the updated data.
Can any one can help me in this.
Thanks & Regards,
Venkat N

hi,
When ever you schedule any job, it gives the name of the job in the screen.
Now after going to SM37 filter the screen for the time period you did the job and put the user id as your user id, so that it show only your jobs which started from the given time interval
regards,
Omkar.

Not able to run the job with user id - is

Hello experts,
We have problem.
Every day we run the job.
( the job contians two programs called ZTIBCOPRG and J_5HJSTP )).
I would like to know why the above job is running with the user ID TIBCOADM. Because this user has German settings for the size conversion in program ZTIBCOPRG and we are having some issues.
We changed the user to TIBCOUSA and the job would not run.
We have changed the user back to TIBCOADM. It is running.
KINDLY HELP ME WITH YOUR VALUABLE inputs. YOUR HELP WILL BE HIGHLY APPRECIATED.
I have checked for both users in AGR_USERS table.
The AGR_USERS is the old user and have many roles compared to userid TIBCOUSA.
WHERE WE NEED TO SEE . IS it authorisation problem or the other user with whom unable to run the job ?
or is this the error in the program ZTIBCOPRG which is not able to do size conversion and causing some issues.
Thanks and Regards,

Hi,
after running the job with user id TIBCOUSA, it should be in cancelled state as per your comments.
you just select the cancelled job and type JDBG in command box and enter it takes you to Debug mode.
There you may get some information where it is failing.
Sudheer. A

Debug the backgroung program

Hi,
I have made one program. Inside this report I am using 'submit' which is used to call a program to display invoice list. when I executed this report in foreground it gives the output but when I run this report in background(using F9) it dose not contains any output. Please advice me what is the actual problem and how to debug the background job,
Please help me it is very very urgent.
Thanks in advance.
Abhishek prakash

Hi Abhishek,
you can debug the background job either two way..
1 if the job is finished then goto se37 select the line which u want to debug type JDBG on t-code bar then enter u will go into debugger..
2. if the job is running state then goto SM50 then select your job then goto program and debugging u will go into debugging mode...
please reward if problem solved..
Thanks Amit.

Debugging Background job

Guy's
is it possible to debug background job.job
that u schedule in background

You can also try this..
Once the job is completed, get into SM37, place the cursor on your Job and enter 'JDBG' in the command field (where you normally enter the Tcodes). This will take you into debug mode & will replicate the runtime of the Job that is completed.Once in debug mode, you will have to single step through a few times to get into the actual ABAP Program.
Regards,
Suresh Datti

Debug background job program

Hi,
i am debugging the program in background mode,
first time i was successful in capturing the job,
second time it is giving error, capture job is failed.
sm37 , jdbg also not working, its given error like bebuggin is not possible in active mode.
in sm50 transaction, it is giving some information message like user reached maxium debugging modes. some error.
please help me, it is very urgent
thanks in advance
points will be rewarded

Hi,
change source code in a way like this:
DATA:
stop_for_capture.
DO.
IF sy-uname NE 'HABICH'. "change to your account
EXIT.
ENDIF.
IF NOT stop_for_capture IS INITIAL.
EXIT.
ENDIF.
ENDDO.
So you have enough time to capture.
proceed by changing value stop_for_capture.
regards
Walter Habich
Edited by: Walter Habich on May 23, 2008 9:56 AM

Regarding ABAP Dump found when saving the job.

Hi all,
Generally we create a job and once the job is created,we rasie Sales Order,Purchase Order and so on.
When we create a job we give the details of the Sold -to-party,client,parent and child job text,advertising category,project type, sales organisation,Cost and profit center,person incharge and purchase division.
After submitting these details the job gets created and the job number will be generated.
But now we have created a new Sales Organisation, which is leading to ABAP Dump.
The functional people have concluded that there is nothing wrong in the configaration settings.
If we enter an existing sales organisation in the job creation process the job is getting created and the job number is displayed.
But if we try to enter a new sales organisation the ABAP Dump is comming.
After debugging we came to know that BAPI function Module called
Bapi Project Maintain Call and inside that there is another bapi call called
BAPI_PROJECT_MAINTAIN which is taking some structures as inputs among them
this new sales org is there.

Hi all,
Is there any answer regarding this question.
Thanx in advance

How to debug the report which isrunning in Background?

Hi all,
1.How to debug the report which is running in Background?
thanks & regards
vishnuvardhan

Hello,
Do like this.
Create an infinite loop before the line u want debug.
data: lf_flag.
do.
if lf_flag = 'X'.
exit.
endif.
enddo.
Now execute the report in background. In Tcode SM37 select ur job and in menu job--> Capture Active Job
IT will stop at the point of infinite loop.
Regards,
Vasanth

How to Debug the Failed Data loads?

Hi..All
Can Any one plz explain How to Debug the different types of Failed Data Loads?
Thanks & Regards
Jonn

Hi Jonn,
If any data failed ....1st analyze where it occurs according to that what we have to decide...
Analysis:
1.Check the Status Tab in RSMO--here we can get error information
2.Check the Details Tab in RSMO--here we can get whether extraction is completed,and where it is exactly failed i.e while updating from PSA or in Update rules etc
3.Check the corresponding request job log in SM37.
4.Check whether any shortdump in ST22.
5.Check the Request status in the Target...some times activation job failed in SM37 but in the Target we found as activated.
6.Check BD87 Transaction for any IDOC errors.
7.Check SM58 for TRFCs
Hope this helps u.....
Mohan

Error is thrown ONLY when the job is run doe delivery creation

Dear SDNres,
I am facing a tricky issue.
I have a job that creates Sales order , Delivery, Billing.
When the sales order contains line items <=8 then the job runs fine and creates delivery successfully
When the sales order contains line items more than 8, then the job fails on delivery creation and the BDC captures error "customised error''
Doubt:
steps in manual creation:
1)I create a Sales order with line items > 8
2)then i create delivery manually .
After the above 2 steps i dont get the error at all in case of manual creation
But the same steps when the job does for a Sales order with line items >8 then the error comes and job fails.
Kindly suggest me as to where i need to look for the error.
Regards,
SuryaD.

Thanks for your response Dave.
Yes i am doing a BDC Call Transaction.
there is no BAPI.
Trickier part is when i execute the job through debugging then i do not get the error.
What could be the reason for this error.
Is it some error in teh coding?
regards,
SuryaD.

Debugging the Job

Similar Messages

Maybe you are looking for