Solution : https://service.sap.com/sap/support/notes/537821 (SAP Service marketplace login required)
Summary :
In an SAP R/3 System, outbound queues destined for a middleware, which doesn't exist, cause SYSFAIL status. These issues affect ARFCSDATA and ARFCSSTATE data, notably displaying "BAPI_CRM_SAVE" in ARFCSSTATE. This occurs due to lack of a connection or nonexistent RFC destination (CRMRFCPAR table) related to EBP/CRM servers. To resolve, entries for non-existing middleware in CRMRFCPAR should be deleted using SM30, improving performance by halting unnecessary queue processing in SMQ1. If not required, the BC-MID indicator in TBE11 should be set to inactive. Additionally, for required connections, establish an RFC using SM59 targeting the CRM server.
Key words :
rfc connection called <enter middleware destination>, sap business information warehouse, bc-mid application indicator, destination <enter middleware destination>, bbp/ebp/crm server, respective rfc destination, rfc destination, ebp reason, crm server, linked server
Related Notes :
| 510192 | Description and maintenance of table CRMRFCPAR |