Runtime Errors - LOAD_PROGRAM_NOT_FOUND

[#1]

Hi ,

we have scheduled delta job for the DO once in a day. After deleted this job, everyday getting dump 'LOAD_PROGRAM_NOT_FOUND' in st22 ,Short Text:

getting dump LOAD_PROGRAM_NOT_FOUND in st22.

Information on where terminated

Termination occurred in the ABAP program "RSBTCRTE" - in "START-OF-SELECTION".

The main program was "RSBTCRTE ".

In the source code you have the termination point in line 492

of the (Include) program "RSBTCRTE".

The program "RSBTCRTE" was started as a background job.

Job Name....... "Sliding Window-Date"

Job Initiator.. "PRODR4"

Job Number..... "0000542F".

What could be reason?

Regards,

Kanagaraj.

[Former Member · Accepted solution]

Hi Kanagaraj,

Basically, when you are deleting the job, you should delete the job in tcode SM37 with the status 'Released'. The job with status Released is responsible for spawning new job based on the frequency. Unless this is deleted, new will be created based on the defined frequency.

I guess in your case, this job is not deleted in SM37 and thats the reason new job is getting creted everyday and trying to execute a report which is also deleted.

If you are using sdoe_bg_job_monitor tcode to schedule/delete a job, you should not have this issue.

Regards,

Vinodh

[Former Member · Accepted solution]

Thanks for your response.

Hi Vinodh ,

I have schedulded and deleted the job using t-code sdoe_bg_job_monitor only.

Eventhoug i got this issue.

This issue has stoped after i deleted the particular program in SM37.

What is standard behaviour ?

Regards,

Kanagaraj.

[Former Member · Accepted solution]

Hi Kanagaraj,

If you had deleted the job using sdoe_bg_job_monitor and you are facing this issue, then I guess there is a problem with the sdoe_bg_job_monitor tool. Please report this to SAP to get it fixed via OSS message.

The standard behaviour is that if you delete the job via sdoe_bg_job_monitor, then this tool should delete the job with status Released so that no new jobs are created again for that report.

Regards,

Vinodh

[Former Member · Accepted solution]

Thanks Vinodh.

[Former Member]

I think it is trying to initiate a background for which either the variant or the program does not exist. please check under the job step what program it is trying to execute and the variant and then check in se38 if that program exists