Debugging a Background Job

[Former Member]

Hi All

To debug a background job which is completed we use the command JDBG and click on the job it will go to debugging module.It is just like simulating the program again.

My doubt -is it like rerunning the program again?If suppose the program contains some insert statement into Ztable it will insert again or not?

Thanks

Raj.

[Former Member]

Hi Raj,

I don't have the T-CODE : JDBG

Are you sure that is the transaction you are using?

SL

[former_member598013]

Hi ,

I dont think so it will not insert the duplicate the data into the ztable. It depends on the Primary key

Thanks,

Chidanand

[Former Member]

What is command JDBG in SAP?

Is it t.code in SAP or it is some ABAP command?

[Former Member]

It is a copy of the running or scheduled job.

Depending on what the program does, it might do nothing, it might process something for you (it is the equivalent of update debugging), or even create entries twice (if entries are always written each time the job runs).

Cheers,

Julius

[Former Member]

Hi,

JDBG is the command used to debug the background job.

If in the job we are inserting any data then job will executed and records will updated. But while doing so it will also maintain the databse constraints and will not update the same data record twice.

[Former Member]

This is the info from SAP help.

You cannot insert a line if a line with the same primary key already exists or if a UNIQUE index already has a line with identical key field values (with regard to this UNIQUE index).

So, it will not be done twice.

Thanks

Kiran