Useful SAP Middleware transactionsSAP CRM Middleware uses Business Document (BDoc) messages when transferring data between systems. Sometimes problem during the replication requires monitoring the Middleware. SAP offers standards tools to monitor BDoc errors messages in the system. The most used transaction is SMW01 (Display BDoc messages) accessed via menu path Middleware>Monitoring>Message Flow>Display BDOC Messages. However there are other useful transactions in the system. Middleware Common Transactions When checking Middleware problems, a review of configuration is necessary. The following transactions are useful. CRM Generation SMOGTOTAL Generate required objects for CRM Replication GENSTATUS Check Status of Generation Jobs SMOGIND Generate Industry Specific Objects SMQR qRFC Monitor/ Register CSA Queue SMOHQUEUE Queue demon CRM Connectivity SALE Define Logical system SM59 Configuration of RFC Connections SMOEAC Administration Console ERP Connectivity SMQ1 Outbound Queue SMQ2 Inbound Queue SALE Define Logical system SM59 Configuration of RFC Connections CRM Replication Setting Adapter object overview (replication filter for customizing R3AC3 objects) R3AS Start Initial Load R3AM1 Monitor replication status R3AC1 Adapter Object Overview . BDoc messages Copy BDoc and process Process BDocs Convert BDoc Messages to XML BDoc Message Error Recovery Watchdog for failed BDoc Messages Tx SMW02A “BDoc Message Error Analysis: Sum of Errors” This transaction is useful to get a detailed error message for “BDOC type”.Troubleshoot BDoc Replication When a BDoc is not replicated successfully. The following transactions are useful: SMW01 SMW02A SMQR SMQ1 SMQ2 SMWP SMWT SMOHQUEUE SMO8REORG SMW03 SMW19 SMW20 SMW3RBM SMW3RC SMW3WD Display BDOC Messages BDoc Message Error Analysis: Sum of Errors qRFC Monitor Outbound qRFC Monitor Inbound qRFC Monitor CRM Middleware Monitoring Cockpit Middleware Trace Monitor R&R Queues Delete Processed BDocs Show stats of unproc. is necessary to check the logs and understand the reason that causes the problem. That allows summarising all errors founded in the system. .The result list not only show the “Bdoc Type” but also the component affected that is useful information when researching SAP Notes that could give any indication of the reason for the error. It could be run in a test mode and filtered by BDoc Type.When pressing button “Detail Analysis” system navigate automatically to transaction “SMW01 Display BDOC Messages” and displays the BDocs Message affected. . User or change date/time. Tx SMO8REORG “Delete processed BDocs” This transaction allows deleting BDocs logs from the system. Cleaning the log will allow users to focus on unresolved system issues. BDoc Message ID. Always have a look not only to the middleware configuration but also to the component configuration. .In summary. issues in more detail could be checked and knowing the "Application Component". a better filter could be used when looking for SAP Notes. middleware problems are usually based on configuration. Using monitor tools.