Skip to Content
avatar image
Former Member

EOIO backlog in Adapter engine with NDLV status

Hello Everyone,

I am working on SAP PI 7.1 . We sent around 6000 idocs to sql and everything was good until we realised that all the messages got stuck in the Adapter engine.

After investigating we found some messages had a system error because the sql procedure they were executing errores out as it was expecting a particular field.

We cancelled the system error message but still found that messages in HOLD status are not going through. It looks like there are other messages in the queue with system error and it has become a tedious task to look for system error messages and cancel them.

We have been going to RWB --> Engine status --> additional data to look for system error messages. We see around 6000 backlog messages.

Also we cancelled them by going to Message monitoring in the RWB.

Is there a way i can skip the EOIO protocol ? How does PI handle if one message fails? Does it always block the rest of the messages in the respective queue ?

Please advice.

Thanks ,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Nov 10, 2011 at 04:22 PM

    Hi Teresa,

    Avoid Maintain order processing in Interface determination and delete blocked messages and clear all queues and restart fialure messages.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      hi Teresa,

      you have to find the first message HOLD or the new NDLV (*) of your serialization group.

      (*) because after your action, maybe the next messages are also shut down.

      Go back in Engine Status -> Tab u201CAdditional Datau201D -> Category u201CMessages Detailsu201D.

      Get the "Serialization Context" name (e.g INBOUND_XI_SERIALxxxx), and the first message_ID of this queue.

      Go back in RWB -> Message Monitoring.

      In the selection-screen, select button u201CShow Additional Criteriau201D, and paste the "MessageId"

      Then try to Resend it or take the decision to Cancel it.

      After that, return to Engine Status and get the 2nd MessageID.

      Go back in RWB -> Message Monitoring.

      Then try to Resend it or take the decision to Cancel it.


      Note: in RWB, with u201CShow Additional Criteriau201D, you have also the possibility to give the Serailization Context (e.g INBOUND_XI_SERIALxxxx), , and so to have all messages of this queue. I don't remind if the parameter field is "queue" (I think) or "sequence id".