No restart capability during mapping failures in ABAP mapping

[krishg]

I am doing ABAP mapping and would like to fail the ABAP mapping (during certain application scenarios) in such a way that message cannot be resent? Is this possible during the mapping.

[Former Member · Accepted solution]

Hello Krish,

why would you have such a requirement? Wouldn't a restart of the same message result in another error? So you could always cancel these messages afterwards by a job. I wouldn't recommend start these jobs from message processing or even change message status on standard SAP tables.

Regards,

Jörg

[krishg · Accepted solution]

Yes, Jorg! I came to the same realization (if you see in my previous post). Thank you.

[iaki_vila]

Hi Krish,

My few cents.

You can resend only the asynchronous scenarios.If you resend you need to develop the logic that in the resend the exception will not generate.

From my point of view, if you want to throw a controlled exception you should do via UDF like this blog explains

If you work with ABAP mapping you have setting more difficulties if in the future your PI go to be upgraded to PI java only version stack.

Hope this helps.

Regards.

[former_member184720]

I don't think so.. Unless you update the standard table "SXMSPMAST" and set the message state to 23 or 24 for that particular message ID.

Examining the status of messages in a PI system - Process Integration - SCN Wiki

[krishg]

I guess the only option would be to automatically Cancel the messages using the RSXMB_CANCEL_MESSAGES program (for your predefined scenario), so that messages cannot be resent.