Holding Message not restarted after remove predecesor by Extended EOIO Error Handling

[xavisanse]

The scenario is very clear.

I have a queue that we use Extended EOIO Error Handling.

This part works as intended: Message in error is canceled & generated a copy with QoS EO and status copied.

But, when the message that fails is canceled the other messages in queue doesn't being triggered for delivering.

I tryed to use the background job of restart filtering for interface but just restart the system error messages, not the holding messages.

How I can automatically restart the holding message? I'm almost sure that it's a problem with the Extended EOIO Error Handling, but maybe the problem is related that we have a splitting mapping (we generate one idoc or other in the same operation mapping).

We have a SAP PO 7.4 SP12 Patch Lvl 40

Maybe should I open a message to SAP but i prefer ask to community before.

[ArielBravo]

Hi Xavier, I once had this issue and the underlaying reason what that the status was not updated into the database because of an issue when activating a higher level of trace/staging. This was resolved implementing the note https://launchpad.support.sap.com/#/notes/2176374 However, having a look at your SP/PL, this shouldn't be a problem in your system and i would open a call with SAP.

What is the status of the following messages?

[xavisanse]

We have seen another note that apply for us. https://launchpad.support.sap.com/#/notes/2381352