update problem

[Former Member]

We have the problem that two reports are not working which are plant as a scheduled job every night.

Both jobs ran for more than a year flawlessly. This phenomenon is new. But via dialogue

it runs without any error.

Did you have even a similar problem.

Please help.

regards

sw ++

[Former Member]

It Might be linked with some Fiscal year date based varients.

or some input parameters might have changed.

Regards.

Gaurav sood

[Former Member]

Can you describe the problem in detail.

Regards,

Lalit Mohan Gupta.

[Former Member]

ok,

The first job reads from a Z-table (customer table) and makes an update to the ADCP-table, the affected fields are -> building, floor , room_no .

And second report makes an update on the attribut CNT (cost center)

Regards

sas

[Former Member]

Dear Experts, how do you generally proceed if your batch input job is not working.

Is there a way to debug our step through to see what causes the problem.

Please help I

bye

sw+++

[Former Member]

You can copy the scheduled background job into the job debugger in SM37 (place your cursor on the job, type "JDBG" into the ok-code and hit enter).

But take note that updates will go through, and the job will effectively run twice... or as many times as you debug it.

Perhaps if you take a look in ST22 before this, there will be short dumps with information about the program and the coding location where the problem is. Keep an eye out for DYNPRO_SEND_IN_BACKGROUND for example.

Cheers,

Julius

ps: Your other question was rejected due to the subject title, and close relation to this question.

Edited by: Julius Bussche on Apr 21, 2009 3:00 PM

[Former Member]

Hi,

Run the first report directly and check whether the functionality is working properly in the debug mode, check the second report in the same way.

if the two programs are working fine in the front end, then they should work in the background also.

see the code which you are using for updating the database tables is working or not.

Please use all the primary keys of the standard table for which you want to change the data.

Hope this will work.

Please let me know if there are any further issues

[Former Member]

hi,

just a question.

What is

DYNPRO_SEND_IN_BACKGROUND ? And what is the reason for keeping an eye on this

Regards

sw++

[Former Member]

Hi sw++.....

It is a type of runtime error which ST22 records, which would indicate background processing problems. It was an example.

Another possibility which occured to me is that someone might have changed the variant which is scheduled with the program in the job. Take a look in transaction VARCH to see whether any changes were made?

Cheers,

Julius

[Former Member]

thx, my problem is still existing I didn't find any error.

I also checked ST22. It is empty. If I have more questions I will ask them here.

If I should meanwhile solve the problem I will close this thread.

Thanks

sw++

[Former Member]

Julius I thank you very much. The problem is solved..

Regards

sw++