RFC Job Issue

[Former Member]

Dear experts,

scenario:

Many parallel jobs are being triggered in our R/3 server. These are triggered by RFC from BI and they are posting idocs in R/3. During this process,each job is reading NRIV table and posting idoc in R/3. some jobs read this table for more than 7000 secs...during this time many parallel jobs are running from the same user and occupying all background processes in CI and app servers as well....

Can i restrict the number of background jobs triggered from this RFC user ? any rfc profile parameters needs change?

we are running on solaris and Db2

Regards

Ravi

[Former Member · Accepted solution]

Hi,

Are you running only with CI Instance or you also have other instances ? as you have mentioned CI is loaded with all of BG process kindly check below points:

1) Schedule the jobs by keeping 10-15 mins Interval so that table will not get updated for the same entry with same job everytime

2) Check RZ12 / SARFC for resource utilization

3) You also need one or more additional instance if you are facing frequently wp resource issue or high utilization of resources

Thanks,

Saleem

[Former Member]

Thanks all for the feedbacks. we have advised the user to run the jobs site wise and asked to repaeat it once the earlier jobs complete...so far it is ok

Regards

Ravi

[Former Member]

Thanks all for the feedbacks. we have advised the user to run the jobs site wise and asked to repaeat it once the earlier jobs complete...so far it is ok

Regards

Ravi

[Former Member]

Dear all,

Thanks all for your feedbacks.

I have changed the rfc/* parameters from the transaction SARFC but still the same situation.

The RFC user in the BI RFC connection to R/3 is given a Service user. Is this because of this ?

Regards

Ravi

[Former Member]

Hello Ravi,

The logic is unless there is work process available to execute the job the job will not be running rather the jobs will get queued up in the system. One of the best approach would be prioritize the background jobs and reduce the number of background worklprocesses. The workprocesses will pick the jobs based on the priority and remaining will be in queue till the workprocess for them are available.

Regards

Vivek

[Former Member]

Hello Ravi

You can reduce the number of background work processes on these application servers which will allow these jobs to run as first in first out.

Unless the work process is available all the jobs will queue up.

You can also create a background server group to avoid central instance being part of this in SM61.

Regards

Vivek

Edited by: vivekwali on Apr 28, 2011 7:27 PM

[former_member311580]

Hello Ravi,

Please check the recommendations from note SAP 74141 regarding resource distribution. See also note 920234.

Regards,

Rafa

[former_member208104]

Hi,

Go to SMQR and reduce select your BI RFC connection in destination field and reduce number of connection.

-Sanjay

[Former Member]

Hi Ravi,

This is because your BI is running extraction jobs from ECC which sends data in the form of Idocs. Now , there are two things you could to either have operation modes or request the BI team to see if they can set the parallelism of these which I think is possible.

Regards,

Venkatesh