Solution : https://service.sap.com/sap/support/notes/588701 (SAP Service marketplace login required)
Summary :
In SAP environments, SYSFAIL statuses in R/3 backend outbound queues and EBP/CRM Server inbound queues often result from predefined safeguards against data inconsistencies due to logical system name changes. The prevention mechanism halts queues if a linked R/3 backend client’s logical system name changes or if new or existing R/3 backend clients with identical logical system names are linked incorrectly. To resolve issues, restoring the original logical system name and reactivating queues or rejecting specific SYSFAIL entries and correcting check tables might be necessary. Situational solutions should be implemented following SAP or consultant guidance to ensure data integrity.
Key words :
rfc destination points, connected application servers, ebp/crm server, status text refers, severe data inconsistencies, /3 backend system linked, crm server, data inconsistencies, crm applications, data hangs
Related Notes :
| 765018 | Problems with logical system during data exchange |