Skip to Content
avatar image
Former Member

SM58: Failed to resolve repository reference-@XI_IDOC_DEFAULT_DEST_XXX

Hi Experts,

we are facing issue on SM58 where IDOCs entries are stuck.

I read all the below blogs but nothing help much.

Problem here is that, when i retrigger, it pushed successfully. so I couldn't confirm that configuration issue, IDOC issue as it passed by reprocess.

Flow - SAP ECC to SAP PI

Right now we manually reprocessing it everyday, but it is not ideal and would like to fix it permanently. please suggest us- what need to be check.



SAP Netweaver Consultant

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Nov 15, 2016 at 01:17 PM

    Hello Prabhakaran

    in our system we have hourly jobs that execute the following reports to reprocess tRFC and qRFC

    RSARFCEX: Restart tRFC LUWs



    With them you will not have to reprocess manually.

    Add comment
    10|10000 characters needed characters exceeded

    • forgot to say, it will be a difference if ECC to PI communication is based on Integration Engine or Advance Adapter Engine

      in first case the communication is done through RFC and you can check logs in RFC devs, in second case if it goes through AAE proxy you will need to check in default trace of Java to see what errors in Java might have been caused not to accept the communications, maybe PI java is under heavy load and no threads are available.