BPM issues in production support

[Former Member]

I am in a Prod support and needs to handle errors and monitor the message flow with out flaws...

I am new to BPM and Workflow...

Could any one suggest me how to handle the monitoring and How to handle errors in the BPM and how to check the workflow related to the BPM.

[Former Member]

HI

refer the below links

/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers

http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm

/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm

/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi

cheers

[Former Member]

Select your message in SXI_MONITOR via proper selection criteria. Then upon chhosing the message click on 'PE' in the item line to navigate to Workflow.

Then check out the container variables in the WorkFlow to fid out the error message.

'PE' stands for Process Engine.

Pls reward points if helpful.

Edited by: Shibaji Chandra on Jun 24, 2008 9:40 AM

[Former Member]

hi,

Could any one suggest me how to handle the monitoring and How to handle errors in the BPM and how to check the workflow related to the BPM.

Check the below links

monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb4...

Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm

Also see the below BPM related links

check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193...

/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers

http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm

Many other examples can be found under the following link at help.sap.com

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

And some weblogs

https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]

/people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****

/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm

/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi

/people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****

/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****

/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure

/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement

Also have a look at these seminars,

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37be...

Thanks,

Vijaya.

[Former Member]

Monitor in SXMB_MONI_BPE

It will highlight any failiures, then check the workflow for the fail point/bottleneck!