Backgroundjob Creates a Warning Message

[Former Member]

Hi Friends,

Kindly help me on this job program issue.

When I execute my job program , the system throws a warning message as 'Warning ! System finds an error due to CONSTANT' of message class 26 and message no 500.I just wanted to know ,where this message is getting triggered. Since, the program involved here is a JOB program , how do I check this root cause ? is it possible to use Debugging , while the job program runs in the Back Ground. i have attached job program details for further verifications.

[Former Member]

Hi Friends,

Kindly help me on this job program issue.

When I execute my job program , the system throws a warning message as 'Warning ! System finds an error due to CONSTANT' of message class 26 and message no 500.I just wanted to know ,where this message is getting triggered. Since, the program involved here is a JOB program , how do I check this root cause ? is it possible to use Debugging , while the job program runs in the Back Ground. i have attached job program details for further verifications.

[kesavadas_thekkillath]

" is it possible to use Debugging , while the job program runs in the Back Ground" - Yes. Please search for the available information.

[Former Member]

Hi,

Unfortunately, you're a victim of lazy developers here, as message 26 500 is a generic message with only placeholders.  This means there's no explanatory long text and the where-used finds multiple, unrelated calling points.

Your best approach is to search the ABAP program in the job step (the name's a bit unclear in the screen print) to find the calling point(s) and find the one which passed the text you see in the message log.  From there you can determine what is causing the message to be triggered.

Alternatively, if feasible you could run the program in dialog to debug it.

regards,

Nick

[Former Member]

Thanks for ur valuable answer, but when i tried to debug the job program using JDBG command, the warning message was not triggered as the job was in finished state . So, how can I proceed in debugging the job, to find the message triggering event in my background job.

[former_member194669]

Try with transaction code SE91 and given the message class 26 and message no 500 , then make a where used , system will popup with programs with message class 26 and message 500 directly used.

aRs

[Former Member]

Hello,

take your basis person's help , because there is 1 configuration for background jobs to avoid warning messages while running the job.

modify this view accordingly : V_T100C (with the help of basis person)

Regards

Avirat