WPs are in On Hold RFC status

[Former Member]

Dear all,

In SM50, very often I see the WPs in On Hold status and RFC as reason. For DIA WPs, the status changes after I refresh. But for SPO WPs, that status stayslonger.

a.) May I know what is this On Hold RFC status about ?

b.) Will this pose performance problem to the system ?

c.) Is there anything I can check or change to improve it ?

Your comment and advice will be appreciated.

Thanks.

Regards,

Kent

[shyam_dontamsetty]

Dear Kent,

1. In general ON Hold status of the workprocess is that during processing if RFC calls or waits for another RFC or some process is supposed to get complete,those cases staus will be in on hold.This is only an example,there can be many reason for on hold status of the Wp.More details can be obtained in Wp trace files.

2.Sometimes it leads to performace problems,especially if there are more wp's are in on hold status results in the bottlenecks of the availablity of wp's, as a result transactions that were running or if new users got logged in are effected.

3.Check the trace files of the work process in SM50 and also from where these RFC's got initiated.If possible check dev_rfc<wp no> files in work directory for more details.

Best Regards,

Shyam Dontamsetty