Siebel Connector for SAP R/3 > Troubleshooting Siebel Connector for SAP R/3 > Troubleshooting SAP Configuration Problems >

Resending Transactions from the tRFC Queue

There are three ways to resend transactions from the tRFC Queue.

1. Manually using SM58. Select a specific transaction and resend with Edit > Execute LUW.
2. Through a scheduled background job. This is the preferred method. You can schedule RSARFCCP to resend failed tRFC calls for a given logical system or RSARFCEX to selectively resend failed tRFC calls. To do this you need to turn off the automatic resend of transactions, as described in the next step.
3. Automatically through background processes. Initially this is the default setting for RFC Destinations. This is not recommended if the IDOC load is expected to be heavy. The resend is done with background processes and, depending upon your configuration, can limit your background processes and cause a very slow resend of IDOCs to the Siebel application.

   The automatic resend is configured under SM59 by making changes to your RFC destination. The RFC Destination can be assigned tRFC parameters consisting of three values. (This is done through the tRFC Options selection in the Destination menu under sm59.) These options are:

   1. Suppress background job if connection error

      If this flag is set to X and a connection error occurs there is no automatic resubmittal of the transaction to the external application. If it is not set, jobs are automatically created according to the following two parameters.

      NOTE:  This flag should be set and resubmission of failed tRFC transactions should be handled through scheduled background jobs.

   2. Connection attempts up to task

      This specifies the total number of attempts SAP makes to resend this transaction.

   3. Time between 2 tries [mins]

      This specifies the number of minutes between each attempt to resend the transaction.

      For example, if a transaction were sent to an external system that did not exist or was not available at the time the transaction was sent, a batch job would be scheduled to resubmit the transaction at a later time. If the value for (b) is 5 and the value for (c) is 10, then the job would be scheduled to run every 10 minutes up to 5 times. At the end of this time the transaction would have to be manually restarted from the tRFC queue (or a batch job to execute it would have to be set up manually).

      If these values are not set for the specific RFC Destination, the default values for (b) and (c) are typically 30 and 15 respectively. This means that the default behavior for a failed job (due to connection or time out problems) is to reschedule itself to run every 15 minutes for up to 30 attempts.

      You can see the time the batch job is rescheduled to run in sm58. This is the time column on each transaction line. This time is first set to the original submission time of the transaction. If the transaction is scheduled as a background job, this time is updated to be the start time for that job. To see more information about the scheduled job, select a transaction line and choose Information > Display Planned Jobs from the menu.

      Remember that the timing values for retry of a transaction determine only when the batch jobs are scheduled to run. A scheduled batch job may not run at the scheduled time, but may run later than this, depending upon the load in SAP and parameters set on the type of job submitted. This can create a very slow transfer of information out of SAP, causing IDOCs to appear in the Siebel application, possibly many hours after they were first created. It is more efficient to schedule your own jobs for the resend of failed transactions.