How To Fix RT198 - Nombre minimum d'appels avec le statut CPICERR.

SAP Error Message - Details

• Message type: E = Error

• Message class: RT - Monitoring infrastructure MSG and alert texts

• Message number: 198

• Message text: Nombre minimum d'appels avec le statut CPICERR.

Quelle est la cause de ce problème?

Here, you see the number of tRFC calls which could not be carried out
because of a problem contacting or communicating with the destination
system or external component. Such calls are optionally re-scheduled as
background processing jobs and are retried. Whether these calls are
retried and how many times they should be retried is specified for each
RFC destination in transaction SM59. By default, retry of calls is in
use.
You see here only tRFC calls with communication errors. Outbound qRFC
calls, which can also have this status, are not monitored directly.
Rather, the alert monitor watches over the status of the queues to which
qRFC calls belong.
You can display communication errors with the ARFCSSTATE monitor
(analysis method). You will also find detailed information in the ALE
monitoring tree on CPIC error calls that were generated by ALE.

Réponse du système

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Comment corriger cette erreur?

Normally, you should see few or no calls with communication problems.
However, communication problems do not necessarily represent a problem.
For example, CPI-C errors may occur if a server or system is down for
maintenance. If the destination is returned to service before the retry
interval runs out, then the tRFC calls are automatically processed.
For this reason, alerts because of accumulations of CPI-C errors
initially carry the alert criticality yellow.
If the CPI-C errors are not caused by a routine and self-correcting
problem such as servicing, then you must check the network connection to
the destination server or component. In addition to actual network
problems, CPI-C errors may be caused by:
an inactive Gateway process in the calling or destination system
an incorrect CPI-C implementation in an external server
incorrect data in the definition of the destination in the calling
system (transaction SM59).
You can test connections to RFC destinations in transaction SM59.
After you have corrected the problem, affected calls are automatically
processed if the retry interval has not elapsed.
Otherwise, you can trigger processing an affected LUW by hand in
transaction SM58 (the analysis method for tRFC).
Once successfully processed, calls with communication errors are
automatically deleted from the tRFC work queue and will no longer appear
in this monitor.

Extrait du message d'erreur du système SAP. Copyright SAP SE.