CRM BDoc Monitor
Great information on the use of SMW01/SMW02:
Transactions: SMW01 / SMW02
CRM 4.0/5.0: Architecture and Technology –> Middleware –> Monitoring –> Message Flow
–> Display BDoc Messages / Display BDoc Messages Summary
SMW01 has the following features:
· Search for special error situations per BDoc ID, BDoc type, user, date, message ID, flow context, BDoc status and linked BDoc messages.
· Successfully processed messages appear with a green light (=final state), those still in process with a yellow light (=intermediate state), and those with an error condition with a red light (=error state).
b) Display functionality
· Display the Middleware Trace
CRM 4.0/5.0: Choose BDoc Message > Display > BDoc Message Trace
·Display the data content
CRM 4.0/5.0: Choose BDoc Message > Display > Classic part
CRM 4.0/5.0: Choose BDoc Message > Display > Extended part
·Display a recipient list
CRM 4.0/5.0: Choose BDoc Message > Display > Errors/Receivers
·Display object links to other BDocs or application object
CRM 4.0/5.0: Choose BDoc Message > Display > Object Links, or push button “Links”
(if object link writing is switched off, use push button “Neighbours”; same information, but collected on demand)
c) Corrective action
· Reprocess failed BDocs
CRM 4.0/5.0: Choose BDoc Message > Process > Reprocess
Do not reprocess the BDoc messages without checking for the possibility of overlapping effects, like overwriting actual data! If newer BDoc messages for the same application object exist and have been fully processed, reprocessing an older BDoc message may cause the current data to be overwritten by a BDoc containing data from an older state. If available for the application object, you should also check the change documents, to see whether more recent changes than the date of the BDoc message have been made.
If you reprocess multiple BDoc messages, make sure the selection is sorted with ascending time stamps in order to keep the right sequence. The actual order of reprocessing corresponds to the order of the marked messages on the screen.
·Delete failed BDoc messages
CRM 4.0/5.0: Choose BDoc Message > Process > Delete
Do not delete BDoc messages without solving the problem! Deleting a BDoc message means that the receiving system(s) will not be updated, thus creating inconsistencies. Only delete BDoc messages when you are sure they are obsolete or can be recreated by sending or requesting the application object again.
As a nice alternative or even a preferred entry point for monitoring, you can use transaction SMW02, which summarizes BDoc messages and gives a good overview about the amount of BDoc messages as combination of BDoc type, state, flow context and receiver (site ID). By double-clicking on a summary line you will see the single BDoc messages by calling transaction SMW01.
Secret CRM Middleware Flow Graphic in CRM system
This can be found by executing report: RSMWDISPLAYCNTXT via SE38 in your CRM system.