Symptom
- Inbound CSA* qRFC entries with the error 'BDoc Message processing cannot be started. MW not operational.' This leads to large growth of table TRFCDATA.
- You wish to know if unwanted BDoc's created on SolMan system are required.
- Large database growth of table SMW3_BDOC2 or other SMW3_BDOC* tables and/or table SMWT_TRC.
- Solman inbound CSA* queues stuck in status Ready.
- This note is also valid for cases in which a CRM system does not exchange data with any other system.
- Stuck SMQ2 entries in client 000.
- Solman Self diagnosis test raises 'Alert Middleware trace level settings are not correct (Alert ID 68)'
Read more...
Environment
- SAP Customer Relationship Management (CRM)
- SAP enhancement package for SAP CRM
- SAP enhancement package for SAP CRM, version for SAP HANA
Product
SAP Customer Relationship Management all versions ; SAP enhancement package for SAP CRM all versions ; SAP enhancement package for SAP CRM, version for SAP HANA all versions
Keywords
SMQ2, SMW01, CSA_INDOBJ*, UPDATES, BUPA_MAIN, BUPA_REL SMW3_BDOC, SMW3_BDOC1, SMW3_BDOC7, SMW3_BDOCQ DDIC, Client 000, SMW3_MFLOW_QPROCESSMBDOC , KBA , CRM-MW-ADP , Middleware Adapter , SV-SMG-SUP , Service Desk / Incident Management , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.