Have you ever been stuck up trying to figure out what actually is going wrong with the mapping program that you have referred to in the transformation step of the BPM? It so happened to me that I had executed my scenario and it gave me a red flag in SXMB_MONI.Upon troubleshooting, the problem was found to exist in the transformation step of the BPM I had used. On a quick check on the mapping program I found a bug which I happened to correct, activate and retest to perfection. Happy that the bug was fixed I returned to test my complete scenario but ‘Alas’ SXMB_MONI still didn’t withdraw the red flag. To my disappointment it stood staring right in my face and the message remained the same – ‘Transformation Error’. More rounds of debugging the mapping program followed but in vain, as I found the mapping to be error free. Further on testing the scenario, the red flag never gave up on me. People who have a deliverable at their hand and are running out of time unable to figure out what the problem is might understand my plight. But luck turned out well as a colleague mentioned the transaction “SWWL”. SWWL is for deleting work items. Following is a screen shot of the transaction. I ran a check in this transaction and found that the workflow loaded concerning the BPM I was using still maintained an ‘Error’ status which I presume would have arisen due to a queue problem. The screen shot below shows the same: Upon deleting the current error entries for the BPM, I went about to test the scenario which was a complete success this time and finally I happened to see the chequered Flag. Phew … Isnt it good to know that there is always a way to get you out of trouble. Note : Deleting entries in SWWL is not recomemded in many live projects.