Need help with File to SOAP sync scenario: NO_BACK_SYSTEM_IN_HOPLIST

[Former Member]

Hello,

I am setting up a new scenario where I get an XML file with PI, send that content via sync SOAP receiver call and direct the result of the web service response to SAP (just back to file as intermediate step).

So far I have the transaction working to the SOAP adapter receiver request / response. I see the correct approval response coming in my SOAP channel (RWB AE payload), but this message gets stuck there before routing back to my receiver interface and mappings.

General setup:

FILE Sender to SYNC OB SI.

OB SI Request is my source message type and Response is my final message output type.

OM Source is this Sync OB SI. Target is a SOAP Sync IB SI. Request Mapping program matches the source file message type and target SOAP layout. Response Mapping matches SOAP response and Target is my final file layout.

Routing for Sync OB SI ID uses this OM for Sync IB SI.

SYNC IB SI has Request and REsponse messages mapping the external SOAP call.

When I test the configuration I get success.

When I send messages through I get error in the adapter about this NO_BACK_SYSTEM_IN_HOPLIST (therefore the response message is not making it back into the IE so that it can be mapped again and forwarded).

Complete error message from RWB Adapter Log "Transmitting the message to endpoint http://[myhostname]:[myport]/sap/xi/engine?type=entry using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: NO_BACK_SYSTEM_IN_HOPLIST:." and the next line is "Received XI System Error. ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: null ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)"

Any ideas for me? (fyi not using BPM).

Regards, Aaron Myers

[Former Member · Accepted solution]

FYI I already have LOGGING_SYNC = 1

[Former Member · Accepted solution]

Hi AAron,

Looks like this problem has occured before. There are SAP Notes recommended. Below are some helpful links.

http://scn.sap.com/thread/848913

http://scn.sap.com/message/4659941#4659941

Thanks,

Divya.

[Former Member · Accepted solution]

Thanks, I've seen other people getting this alert in the forums also but the conditions don't seem to fit and our system is very up to date.

Now I'm thinking I need to make use of the RequestResponseBean and ResponseOnewayBean to make this Sync/Async bridge work.

AsyncSync & SyncAsync Bridge without BPM | SCN

[baskar_gopalakrishnan2 · Accepted solution]

There are plenty of blogs for using requestresponsebean and responseonewaybean modules to use async sync bridge.  You can do it  you might have to map the soap response to some psuedo interface at the end. like

file -> SOAP ->file.

If you want to ignore the soap response,  you can also do it.  Design level you keep the response synchronous... That is file to soap (request  mapping)  and soap to file (response mapping).  But you can configure the soap channel as EO instead of BE to avoid the response (if you dont need).  This is an another technique to ignore synchronous response by setting configuration object changes.

[Former Member · Accepted solution]

Thanks Baskar, I definitely want the SOAP response in this case. I am happy with FILE-> SOAP -> FILE, or I may shift to FILE -> SOAP -> IDOC.

In your experience, is using these beans the best and most reliable way to achieve that scenario?

-Aaron

[baskar_gopalakrishnan2 · Accepted solution]

Use this link

http://wiki.scn.sap.com/wiki/display/XI/Using+Request+Response+Bean+Module+in+FILE+Adapter

yes using these beans is reliable and I have used in my work. Then change your interface to FIle -> SOAP-> File

[Former Member · Accepted solution]

haa haa, scroll to the bottom of that link Baskar and you can see I was there today also 🙂

I am almost there...now I just have a namespace mismatch on the response message coming back from the web service. I think I can put a simple XSLT to fix it up and I will close this thread soon.

Interesting I see some examples saying alternate approach of having 2 async and one sync service interface vs having two sync SI.

I was very close with my own initial setup, just missing those beans really.

[Former Member]

Ok so I am trying to follow the model example in this SAP guide:

https://scn.sap.com/docs/DOC-43843

On page 8 is the scenario Asynch IDOC to Sync RFC to Asynch SOAP.

I'm confused on why we would need a SOAP Sender channel here if the SOAP is just an Asynch receiver in this case. If you understand this please help me understand the reason.