BPM Transformation Error not Raising Exceptions

[Former Member]

Hi,

I've got a BPM receives a message, then call a transformation step and then send the message. I've created exception branches for the transformation and send steps. If the message mapping called in the transformation step works, the message is send, no problems. If a message mapping exception occurs, for example a string index out of bounds, the exception branch is not executed. Instead the BPM continues to the send step and an error occur because of the empty container element.(the container is empty because the mapping fails). SAP Help states that an exception is "Thrown when a permanent system error occurs" in the Transformation step. My question is what exactly is a permanent system error if normal message mapping exceptions is not a permanent system error? And also, how do I generate a permanent system error when a message mapping exception is thrown in order for the exception branch in my BPM to execute?

Any suggestions will be appreciated.

[henrique_pinto · Accepted solution]

Rudi,

just observe that a mapping that creates an empty target message does not necessarily has raised an exception. That seems to be your case.

Properly test your mappings in test tab of interface mapping in order to check the expected behaviors.

Regards,

Henrique.

[Former Member · Accepted solution]

Hi Henrique,

thanks for the response. The mapping definitely raise an exception, if I go into the BPM logs I can see the mapping exception and if I take the message through the test tool the same mapping exception occurs. It looks if the problem is what the previous reply states and that is that a mapping exception is not a permanent system error and that is why the exception branch is not executed. Have you ever tried to test this?

[Steven_UM · Accepted solution]

Hi Rudi,

Normally this works fine ( we use it all the time ) but we found out that it stopped working after we upgraded our 2004 to SP19.

SAP note '1086654' contains a bug fix to solve this ...

Regards,

Steven

[Former Member · Accepted solution]

Thanks Steven, we just upgraded to SP20 from SP18 so this seems to be the answer I was looking for. Much Appreciated.

[Former Member]

Hi

The exception handler in your case will work only for the permanent system error and the mapping error like in your case array out of index is not a system error .

for handling this type of case use the UDF for creating the alert in your mapping and creating the alert configraution.

Thanks

sudhir sharma

[prateek]

I dont think there is a direct way to raise such error in mapping

What is the sxi_cache status for ur integration process?

Here r the steps for which permanent error is thrown

http://help.sap.com/saphelp_nw04s/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm

Regards,

Prateek

[Former Member]

Hi Prateek,

the cache is up to date and the return value for the BPM = 0

Everything on the BPM works fine, except that a mapping exception is not executing the exception branch it is setup to do.

[prateek]

Make sure that the process instance is not stuck due to correlation.

If so, delete the workitem using tcode SWWL

Regards,

Prateek

[Former Member]

Hi Prateek,

have you ever managed to do a BPM where a message mapping executed in the transformation step executes the exception branch linked to it if a message mapping exception occurs?

[Former Member]

Hi,

Do you have an exception handler defined on the block ? Does the transformation error raise this exception ?

Cheers

Colin.

[Former Member]

Hi Colin,

yes, I do have an exception handler and the transformation step is setup to raise the exception, but it does not. I also have a exception handler for the send step which is executed 100% if an exception occurs in the send step.

Thanks