In normal operational scenario it may happen that you have lots of ccBPM in error state due to multiple reasons and it is not possible to restart these erroneous BPM processes again without re-sending the message from source.
Now to identify source message (triggering point), one way is to open each of these ccBPM and then search for starting message and then use the same to re-trigger the message again. This is quite extensive approach and requires lot of manual effort. But by using the following approach you can save quite an effort.
Step 1: Get the workflow IDs of the erroneous BPM processes using option 'Restart erroneous process' under SXMB_MONI_BPE
Step 2: Go to SE16 and enter table name as ' SWFXIPROCMSGREL'. In the input parameters, provide all the workflow IDs collected in step 1 in the field WI_ID and set MSGPROCREL as 'R'. The resulting data will provide with all the message GUIDs of the message which started these ccBPM in first place.
Now you can use standard function modules to get more information or extract actual payloads for these message guids from SAP. Hope this helps.