cancel
Showing results for 
Search instead for 
Did you mean: 

Background Jobs

Former Member
0 Kudos

Hi Friends,

At one of my Customer site, I found strange issue in Test System Environment.

When I define Background Job in SM36 as Class B or C , the job is in released status only.

I have gone through already defined background jobs as Class B or C, those jobs all still in released status.( Those jobs timestamp already completed).

Background Jobs with Class A founds be okay.

What may the actual reason?

How to resolve this Scenario.

Please share your experience.

Thanks inadvance.

Regards,

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Be sure that the number of class A work processes is less than the total number of background work processes in an application server. Otherwise, only class A jobs will be eligible to run on that server

and jobs assigned for class B and C will not execute.

Regards

Krishna Vanga

manu_susankar
Active Contributor
0 Kudos

Hi Thirunagari Venkata Ramana,

As per your input's in the thread, It seems back ground work processers in your system are assigned to class A. Check the below link for your reference

http://help.sap.com/saphelp_erp2004/helpdata/EN/c4/3a7f53505211d189550000e829fbbd/frameset.htm

Regards,

S.Manu.

Former Member
0 Kudos

hi,

please check;

Is there at least one host with a free background work process for the required job class?

Wait until a background work process becomes free, or set up a further background work process for the job class (see "Analyzing parts of the runtime environment", section "Switching between operation modes").

please refer the Snote:37104

Regards,

Gokul