Diagnosis
This message describes the monitoring functions in the Alert Monitor.
Transactional RFC (tRFC, Remote Function Calls) is a function thattransfers data between SAP systems or between an SAP system and anexternal component.
Here, you see the log messages for calls with CPI-C errors - calls thatcould not be completed due to a connection or communication problem withthe SAP destination system or external destination component. You canreschedule and repeat these jobs as background processing jobs. Enterthe number of retry attempts in transaction SM59.
Calls with CPI-C errors can be tRFC calls from ALE or tRFC calls fromother applications. You can also use the ALE monitoring tree toinvestigate ALE calls with communication errors. The ALE monitoring treeincludes views of calls with communication errors in the ALE queue orother entities.

Procedure
Each CPI-C error generates a log message. The log message contains theinformation you need to identify the call. You can use the analysismethod or transaction SM58 to display CPICERR calls. The display givesyou more information about the problem. Note: You might not find logmessages for all calls with CPI-C errors. The Alert Monitor only has alimited amount of space for these messages, which means that some mightbe deleted. For a complete view of all calls with CPI-C errors, use theanalysis method for the monitoring tree element 'Number of CPI-CErrors'.
CPI-C errors have level yellow. No red alert is generated, since thecommunication problem is often not that severe. For example, the targetsystem might not be running due to maintenance work. Since calls withCPI-C errors are repeated automatically, the problem might well besolved as soon as the destination is available again.
If the CPI-C errors are not caused by a routine problem, such asmaintenance, then you must check the network connection to thedestination server. As well as definite network problems, CPI-C errorscan also be caused by the following:

• An inactive gateway process in the calling or destination SAP system


• A CPI-C implementation with errors on an external server


• Errors in the definition of the destination of the calling system
(transaction SM59).
You can test the connection in transaction SM59.
Once you have solved the problem, the affected tRFC calls and LUWs areprocessed automatically, as long as the interval for the retries has notpassed.
Otherwise, you can trigger the processing of an affected LUW manually intransaction SM58, or in the analysis method for tRFC.