We have added search box. Key in SAP issue keyword to search

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE: [sap-basis] job is "HOLD" and reason is "RFC

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from Waelz, Dean on Jun 27 at 12:19 PM
Good Day

There are work process timeouts (rdisp/max_wprun_time) and gateway timeouts (http://help-legacy.sap.com/saphelp_erp2005/helpdata/en/7c/e75c 6798dc40269fd7213ff01c9aa8/content.htm). Changing the system values to accommodate this one scenario could do more harm than good (be careful to understand what else you may be affecting before you start changing values).

In this link: https://archive.sap.com/discussions/thread/1565725 a reply mentions: "maybe you could use function module RFC_VERIFY_DESTINATION just before calling your RFC". That sounds to me like a better approach.

Also check:


---------------Original Message---------------
From: Ramon
Sent: Tuesday, June 27, 2017 6:50 AM
Subject: job is "HOLD" and reason is "RFC


We have a job that integrate idocs. It send idocs to 4 systems.
We have the problem that if system 2 is not available because the oraarch is full, the background
workprocess status of the job is "HOLD" and reason is "RFC" because the job can not connect to system 2.
We would like that if system 2 is not available (after trying some minutes) the job continues with system 3, by this way the job could finish correctly.

Is there any way to configure a time out of rfc or something like this?

Best regards

Reply to this email to post your response.
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
© 2017 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
Waelz, Dean  

IT/IS Professional/Admin/Staff
Mark as helpful
View this online
Ask a new question
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements



Post a Comment

T r a n s l a t e to your language