topic Re: Problems when defining Background Job in Application Development and Automation Discussions

Problems when defining Background Job

Former Member — Mon, 03 Dec 2012 10:54:01 GMT

Hello everyone,

I got a special problem when defining a background job (transaction SM36). For describing the problem, it is necessary to describe our system landscape. We got three systems: First our development system (E*) which is only for developing, then our test system (Q*) which is used for testing and is a copy of our productive system (P*).

The following problem I got only in our E-System. No problems with it in Q* or P*-System. So it is a little bit confusing, because all systems are on same release.

When I try to define a new background job with SM36 and try to enter the name of the abap program and the name of the variant in corresponding language, I got error message 'Enter a valid value' which refers to the variant field. The funny thing is, that the entered variant is clickable with F4-Value Help but SAP does not let me save the job when clicking on save or check.

Anyone got this problem too and a solution for it?

Kind Regards

Michael Boguth

Re: Problems when defining Background Job

sandeep_katoch — Mon, 03 Dec 2012 11:21:31 GMT

Hi Michael,

It seems to be a bit confusing but you can try following

1: Check in transaction se38 by giving the name of report and the name of variant. Once you enter the name of program and variant click on display variant radio button, see if the value is appearing for the variant.

2: If no create a variant in se38 T code.

3: Check in table Varid by giving the value of report and variant whether the entry exists or not.

4: Once all is done and everything seems to be perfect then try to create a new varaint for test and create a job with the newly created variant.

Regards,

Sandeep

Re: Problems when defining Background Job

Former Member — Mon, 03 Dec 2012 12:14:13 GMT

Hi Sandeep,

unfortunately it does not help. The variant is available in SE38 (I created it there) and also in table VARID. I created a new one with SE38 by saving it in the selection screen, but got the same problem.

One special thing that came up:

Of course I canot create background job without variant. And If I click on one of the variants, I got the problem with 'enter correct value'. But when I do not put any value in the variant field, then automatically the variant popup comes up and in some cases - after clicking on one of the values - I am able to save it. But I did not found out yet in which scenario I am able to save it, because normally (in most cases) it does not matter If I double-click on one variant or click it with the green arrow, I am not able to save.

Regards
Michael

Edit:

Ok I found out when I am able to save it. It works with:

1. Entering no variant value

2. Click on save button for the step -> then variant popup comes up

3. Choose variant

-> by doing it like this it looks like I get through the check with the variant.

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 04:43:23 GMT

Dear Michael,

Your issue is really confusing.. I too agree...

My opinion is go to SM37 and click on JOB WIZARD and try to create the job.

Hope it will work..

Thanks ,

Anoop S

Re: Problems when defining Background Job

sandeep_katoch — Tue, 04 Dec 2012 05:14:04 GMT

hi Michael,

This is really very weird case but anyways when you have got the workaround then meantime you can go with it.

Regards,

Sandeep

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 08:24:09 GMT

I have the strange feeling that it refers to some inconsistency in our developtment system, because it is of course for testing everything 😉

I tried to debug through SAP standard program yesterday, but was not able to find the point where the message came up. Unfortunately it is standard message, message class 00, message no. 002 which is used for message in several programs.

Does anyone know how to find it? By searching the message, I get a list of ~100 programs where none of them sounds right 😉

@Annoop

Where dou you find JOB WIZARD? I do not see this in SM37.

Regards
Michael

Re: Problems when defining Background Job

sandeep_katoch — Tue, 04 Dec 2012 08:29:54 GMT

Hi Micheal,

Try this to debug.

Enter into debugging mode and click on breakpoints at statement :-

Put a break point at statement message and click enter.

wherever the message statement is coming and is getting executed debugger will stop.

Regards,

Sandeep

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 08:37:16 GMT

Hi Sandeep,

the problem is not how, but where 😉

When I try to debug with '/h' it does not work, because I can only enter in in transaction field, before i get in detail mask for step definition.

When I look for the message, it gives me a list with 100 programs and from the name none of them looks right.

When I look in function group SAPLBTCH for SM36, there is a huge list of includes where it is not easy to find where the message came up.

Regards

Michael

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 08:38:34 GMT

Hi Michael,

Sorry it is in SM36..Go to SM36 and there you can see the Job wizzard.

Thanks ,

Anoop

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 08:39:20 GMT

Hi Michael,

Sorry it is in SM36..Go to SM36 and there you can see the Job wizzard.

Thanks ,

Anoop

Re: Problems when defining Background Job

sandeep_katoch — Tue, 04 Dec 2012 08:53:38 GMT

Okay then do one thing

create a notepad . txt file with these details

[FUNCTION]

Command=/H

Title=Debugger

Type=SystemCommand

Save it.

When you are about to enter the value of variant or after you have entered the value of variant then drag and drop this text file from desktop either the check button or save button. Once you will press any of these button debugger will start.

From here put a breakpoint on mesage statement and check in which program and where this message is creeping from.

Regards,

Sandeep

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 08:55:37 GMT

@Anoop

Same problem in Job Wizzard when entering variant name 🙂

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 09:06:04 GMT

Hi Michael,

Are you sure that the varient is there in the dev system?
Or create another varient and try....

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 09:09:18 GMT

@ Michael,

Or in Job wizard click on the F4 option for varient.
See the picture.

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 09:09:29 GMT

@ Michael,

Or in Job wizard click on the F4 option for varient.
See the picture.

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 09:13:43 GMT

Wohoo, text document with command /h, really nice 🙂

Never heard that before.

I did it but unfortunately it does not help. Message cames up after proving field variant (see the mark in screenshot 1) and then goes to screenshot 2. Message ID and message no. are prefilled when entering method GET_LINK. Never seen that before 😉

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 09:17:00 GMT

Yes they are availabe in value-help F4, thats the confiusing about it. They are in table VARID as well, so everything looks fine, but unfortunately SAP does not accept them.

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 09:19:58 GMT

Hi Michael,

that 2nd screen get_link method is executed whenever the program is displaying messages. It means that the value which is capturing from screen field is invalid though i dont know why. This thread is really interesting. Hope you will find the answer for it.

thanks.

Re: Problems when defining Background Job

sandeep_katoch — Tue, 04 Dec 2012 09:21:52 GMT

Put a Break point on Function Module BP_CHECK_REPORT_VALUES in Include LBTCHF07.

Check what Sy-subrc is coming.

If everything is fine till here than move ahead with step by step debugging.

Regards,

Sandeep

Re: Problems when defining Background Job

Former Member — Tue, 04 Dec 2012 09:26:08 GMT

Hai Sandeep,

This .txt file debugging is a very good idea... And it is new to me...

Thanks a lot for this info...

Anoop Satheesan