Handle system errors in BPM

[Former Member]

I'm working on a BPM that may fail to perform some steps due to system errors. I can raise an exception if that happens, but what I'd like to do in the exception branch is to build a response message to the calling application that starts the BPM, declaring the reasons of the error. I can do that giving a generic "system error" description, but I'd like to be more precise, and access the system error cause itself and add it to the message description.

Is this possible? How to make it?

Thanks in advance.

[Former Member]

Hi ,

I Assume that we can not find the cause of the error . Just we can have an exception branch and put your message "system error " OR else in the Exception Block keep an transformation , in that you will be having a message mapping . If possible we can collect any system messages here

Regards,

Jude

[Former Member]

OR else in the Exception Block keep an transformation , in that you will be having a message mapping

Yes but, which will be the source interface of the mapping? Does the system error generates a message saved in any default system interface?

[Former Member]

So nobody knows an answer? Even if the error is triggered by an exception of a RFC that in any normal scenario would be stored in the exception message type, in a BPM we can't have access to it?

Edited by: Eduardo Cabezas López on Nov 6, 2009 2:00 PM

[rajasekhar_reddy14]

Hi,

As per my knowledge we can raise System errors using Send step and Transformation Step.I dont think we can rise System errors using Control step.Control Step handles only Exceptions not System errors.(Confirm once).

But if you want to rise System errors go for Send Step Synchronous or Asynchronous.

Send Step Synchronous used when exception triggered by permanent system errors that occur in the pipeline or while transporting the message to or from the pipeline.Asynchronous Send Step:the exception will only be triggered if an error occurs during the transfer to the pipeline. Errors that occur during mapping in the pipeline, do not trigger an exception.

Transformation step used when to rise Permanent System error occurs.

Regards,

Raj

[Former Member]

I didn't mention transformation steps at all. It is in a send step precisely where I want to capture this system error, the thing is how to know in BPM the cause of the error and send it as a response of the BPM.

[rajasekhar_reddy14]

Then use send step only,it rises System error when an exception occurs in Pipeline steps,like message mapping exception.Better to confgure one simple one scenario and rise one exception using Send,The you will kow how its behaving.I never done ,thats why i dont know how eaxctly it will work.