1. SAP 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
R3AC3
Adapter object overview (replication filter for
customizing objects)
R3AS Start Initial Load
R3AM1 Monitor replication status
R3AC1 Adapter Object Overview
Troubleshoot BDoc Replication
When a BDoc is not replicated successfully, is necessary to check the logs and understand the reason

2. that causes the problem.
The following transactions are useful:
SMW01 Display BDOC Messages
SMW02A BDoc Message Error Analysis: Sum of Errors
SMQR qRFC Monitor
SMQ1 Outbound qRFC Monitor
SMQ2 Inbound qRFC Monitor
SMWP CRM Middleware Monitoring Cockpit
SMWT Middleware Trace
SMOHQUEUE Monitor R&R Queues
SMO8REORG Delete Processed BDocs
SMW03 Show stats of unproc. BDoc messages
SMW19 Copy BDoc and process
SMW20 Process BDocs
SMW3RBM Convert BDoc Messages to XML
SMW3RC BDoc Message Error Recovery
SMW3WD 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”. That allows summarising all
errors founded in the system.

3. 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.
When pressing button “Detail Analysis” system navigate automatically to transaction “SMW01 Display
BDOC Messages” and displays the BDocs Message affected.

4. Tx SMO8REORG “Delete processed BDocs”
This transaction allows deleting BDocs logs from the system. It could be run in a test mode and filtered
by BDoc Type, BDoc Message ID, User or change date/time. Cleaning the log will allow users to focus on
unresolved system issues.
In summary, middleware problems are usually based on configuration. Always have a look not only to
the middleware configuration but also to the component configuration. Using monitor tools, issues in
more detail could be checked and knowing the "Application Component", a better filter could be used
when looking for SAP Notes.
http://scn.sap.com/thread/198951 I DOC & B DOC