Skip to Content
author's profile photo Former Member
Former Member

Design question about the Error Handling for failures in PI

Hi,

We wanted to know how you guys are handling (or will handle if asked) error handling for below scenario:

We have sync scenario (soap-jdbc) from a web which sends a request to PI to call SPROC in DB and need to send the response back to web. This scenario works fine as long as there are no errors in PI. However if message fails in PI, Web is giving "We are sorry...." exception as part soap exception. We want to send some graceful message back to web if message fails in PI as similar to we send response from SPROC. Lets say if message fails because of mapping, sending response as "Message failed in PI with the error: error from PI". How to implement this in PI?

I think Alerts is not an option here as we don't want to send an email to anyone but we want to send back response to Web Services as message failed in PI immediately as user is waiting in front of screen.

Regards,

N@v!n

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    Posted on Aug 16, 2012 at 12:18 AM

    May be you need to use BPM with Sync-Async bridge pattern by handling mapping error within BPM and then send static response back to sender.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 16, 2012 at 06:55 AM

    Hi Navin,

    If PI is down clearly is impossible to produce an answer. The only solution for this issue is to reduce the possible causes of error.

    1. To use the PI XML validation in order to avoid mapping erros.

    2. With the XML validation the unique problem could be in the receiver side, but you can control this point with the PI fault messages. Check this links:

    a) SAP HELP documentation: http://help.sap.com/saphelp_nwpi711/helpdata/en/48/5946db5f693912e10000000a42189b/content.htm

    b) Jhin Shin's blog that deals with the SOAP Fault Response: http://scn.sap.com//people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi

    c) Shabarish's blog with the Abap Server Proxies fault messages handling http://scn.sap.com//people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Jörg,

      You can define a mapping for error cases, but it is actually the nature of mapping errors that something unexpected happen. And then the mapping will fail, the response will not be delivered. You ll get a red flag in MONI, but the soap sender will get nothing.

      Regards,

      Udo

  • author's profile photo Former Member
    Former Member
    Posted on Oct 25, 2013 at 07:19 PM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 11, 2013 at 10:02 PM

    HI,

    Did you find any solution for this? we are also at the same scenario to implement error handling.

    We had proxy to soap syncronous interfaces which return application faults in response if anything wrong in target system.

    Now the requirement is to send any mapping errors or missing fields in payload back to sender as application fault without distrubing the exisitng setup.

    any inputs you guys implemented will be of help.

    Thanks.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.