NO_BACK_SYSTEM_IN_HOPLIST

Hi all,
I am working on PI7.1 Service pack 06. I developed RFC to file and File to RFC interface. both are working fine, but getting acknowledgement messages and failing in Technical Routing of Response with below error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">NO_BACK_SYSTEM_IN_HOPLIST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)</SAP:Stack>
These failed acknowledgement messages are getting stuck in SMQ2, which are giving trouble to some other messages.
I searched some forums, they are discussing about sap note: 1078317. Even when i am running interface from runtime workbench also i am facing ths acknowledgement failure. As this is async to async, i am sure i developed interface correctly. I found some posts in SDN with same type of query, but no one closed the with solution. Is this problem with RFC or Server????.
Thanks & Regards,
Madhu.

Hi Madhushudan,
May be this link might be useful for some extent
NO_BACK_SYSTEM_IN_HOPLIST
regards
guna

Similar Messages

Need help with File to SOAP sync scenario: NO_BACK_SYSTEM_IN_HOPLIST

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

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.

Soap receiver adapter exception

Hi,
I am using SOAP receiver adapter to access a web service that is hosted on SAP Web AS (in this case it is the integration server Web AS). I use the web services navigator to test the web service and the web service works fine. The name of the web service is 'RemoteCrossReferenceProcessor' and it has one operation 'crossReference'.
But with the soap adapter, I am getting OperationNotFoundException in the logs and my web service is not getting accessed. Here is the server log:
An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:RemoteCrossReferenceProcessor'; Key name:'SoapRequestWrapper' key value:'crossReference'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0003BA0FF9EA0022000000840000688D0003F9349A3C2D61#1118429251382#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######b40aca80d9be11d994360003ba0ff9ea#SAPEngine_System_Thread[impl:5]_47##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:#http://sapsand1:8000/sap/xi/engine?type=entry#
Here is adapter configuration:
Transport Protocol:HTTP
Message Protocol:SOAP 1.1
Adapter Engine:Integration Engine
Target URL: http://<server_name>>:50000/RemoteCrossReferenceProcessor/Config?style=document
User:
Password:
Default SOAP Action:
I imported the WSDL into the external definition and used the messages from the WSDL for defining my interface mappings.
I am using XI 3.0 SR1 (SP 09).
I am out of ideas as to why the SOAP adapter is not calling my web service. Please help me with your suggestions.
Thanks and Regards.

HI Dani,
I was looking for this error and I found this post AXIS SOAP Receiver. This post says about other errors, but sugests many ideas to found the soluction, like:
1- non-deployed all AXIS jars; (but in this case it deployed all)
2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).
3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".
By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.
I hope this helps,
Romerito Silva

Error Message in RWB for Receiver JDBC

Hi Everyone,
We are getting the following error with Receiver JDBC scenario:
Received XI System Error. ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)
Transmitting the message to endpoint http://server:8010/sap/xi/engine?type=entry using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:.
what could be the possible reasons?

Hi ,
Request Messages
The request message contains an acknowledgment tag, which specifies the event for which an acknowledgment is expected. This tag must be specified by the sender (or a sender adapter that supports acknowledgment messages).
 Message processing in SAP Exchange Infrastructure ensures that the acknowledgment message follows the same route from the receiver to the sender as the request message did from the sender to the receiver. For this purpose, the request message contains a hop list that logs the route of the request message. This information is provided by all Integration Engines and Integration Servers that are involved in the processing of the request message.
Acknowledgment Message
As soon as the request message processing encounters an event that requires an acknowledgment, a corresponding acknowledgment message is created and sent to the sender.
 An acknowledgment message receives a new message ID, but also has a reference to the message ID of the request message as well as the value Response in the Directory tag of the message header. The request message hop list is copied to the acknowledgment message header, thus enabling backward routing of the acknowledgment message.
 The poosible reason for the error you got ,might be due to you have not defined a particular sender port and client which acknowledgments are requested from the sender. OR configuration parameter has not been set in the respective catagory.
Probale Solution:
1-- You can use Acknowledgments function to define the acknowledgments you want to request for a sender port and client by using function Configuring Acknowledgment Requests :
 a)In the ABAP Editor (transaction SE38), under Program, enter IDX_NOALE and choose Execute.
 b)Enter a sender port and client.
 c)Decide whether acknowledgments are to be requested or not for the sender port and client. Choose either Request Acknowledgment or Do Not Request Acknowledgment.
The acknowledgments that can be requested are system error acknowledgments, application acknowledgments, and application error acknowledgments.
 d)To display all message types that are sent using the selected sender port and client, in the Exception List frame, select Display Entries followed by Execute.
 e)If you want to define a different rule for a specific message type, in the Exception List frame, select Insert Message Type or Delete Message Type.
 f) Select the relevant message type and choose Execute.
2-- You can change the configuration parameter by following the link:
http://help.sap.com/saphelp_nw04/helpdata/en/89/b5553bf3a76258e10000000a114084/content.htm
**Pls: Reward with Points if helpful **
Regards,
Jyoti

IDOC(3.1H)- XI- SOAP - Acknowledgment Problem

We are using IDOC(from 3.1H system) ->> XI ->> SOAP(Async) scenario for purchase orders. We have defined IDOC-Receiver in the communication channel for the SAP business system.
We are getting following error in adapter engine for sending the acknowledgment back to SAP(3.1) system.
Received XI System Error. ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)
Any help is appreciated.
Thanks!
MP

Hi,
have a look at this SAP note: 767681
for such an error and SOAP adapter
let me konw if it worked
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

File to Web Service - No back system in hoplist

Hi guys
I've implemented a File to Web service Scenario with XI. The file is picked up from the server.
The message monitoring in the Runtime Workbench shows the following error:
"XI-Systemfehler erhalten. ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)"
Has anybody a clue?

Hi Gokhan,
please go thru the links below and see if u have followed the steps mentioned in it while defining the web service..if it still doesnt help you, pleease do let me know.
http://help.sap.com/saphelp_erp2004/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
/people/david.burdett/blog/2005/01/28/why-using-web-services-for-b2b-is-hard-to-do
/people/dj.adams/blog/2004/06/24/forget-soap--build-real-web-services-with-the-icf
/people/renald.wittwer/blog/2005/01/05/develop-a-web-service-that-sends-an-email
I hope the info provided will help you to atleast some extent solve your problem.
Regards,
abhy

File to WebService - unknown application error

Hi guys
I want to call a Web Service on my PC using an XML file. I'm monitoring the scenario with the RWB. I want to make sure that the Web Service call actually happened.
I used a Sender-SOAP adapter and a Receiver-File adapter for that purpose and got the following error in the RWB.
SOAP: response message received a89d5830-b1b2-11da-9b47-000c7680c55b
SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
In a further waiting message in the message monitoring I found the following error:
ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)
What is the easiest way to utilize the response from a Web Service call??
Thanks.

Hi Gökhan,
>>>>I used a Sender-SOAP adapter and a Receiver-File adapter for that purpose and got the following error in the RWB.
if you want to call web service from file
you need to use:
- sender file adapter - not receiver
- receiver SOAP adapter - not sender
if you want to be sure you're message
was delivered and processed (by web service)
you can use sync call (with BPM only)
and return something out of this web service
(like OK status)
BTW
have a look at this excellent weblog on
SOAP errors:
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Regards,
michal
XI FAQ - Frequently Asked Questions

XI Production Issue In Adapter Engine Messsege Monitoring

HI every one ,
I am facing a starnge problem. When I am going to SXMB_MONI to check flag status, all messeges are OK and processed. However when I am going to Runtime
workbench - >Messege monitoring - >Adapter Engine, and seeking for system errors/ waiting/ holding / I am getting this as an error.:
Time Stamp Status Description
2008-05-05 11:59:14 Success Admin action: Trying to fail message.
2008-05-05 11:59:14 Success Admin action: The message was successfully
set to status failed.
2008-05-05 11:59:14 Error Trying to deliver asynchronous error
notification (message ID: 94c7b8d0-1a6c-11dd-c9c9-00145e743aaa
(INBOUND)) to sending application:
com.sap.aii.af.ra.ms.api.DeliveryException: Message failed by admin..
2008-05-05 11:59:14 Success Asynchronous error notification
successfully delivered
This messege is available in the Error Log .
Can any one help me why this is happening , and where should I check to detect the probable reason for this!!
points would be Awarded .
Thanks in advance
Arnab
Edited by: Mohd Abdul Khalid on May 5, 2008 9:38 AM

Pls see the error below, this is all what I have......Incase u need some other information, revert back.
Time Stamp Status Description
2008-05-09 00:59:53 Success Trying to put the message into the send queue.
2008-05-09 00:59:53 Success Message successfully put into the queue.
2008-05-09 00:59:53 Success The message was successfully retrieved from the send queue.
2008-05-09 00:59:53 Success The message status set to DLNG.
2008-05-09 00:59:53 Error Received XI System Error. ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)
2008-05-09 00:59:53 Error Transmitting the message to endpoint http://isrxiprd:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:.
2008-05-09 00:59:53 Success The asynchronous message was successfully scheduled to be delivered at Fri May 09 01:04:53 GMT+05:30 2008.
2008-05-09 00:59:53 Success The message status set to WAIT.
2008-05-09 01:04:53 Success Retrying to send message. Retry: 1
2008-05-09 01:04:53 Success The message was successfully retrieved from the send queue.
Thanks in advance!!!
Arnab

Fault Message data

Hi,
We are sending data from HTTP to PI and than to SAP via Proxy. In SAP, proxy receives it and calls the BAPI to post the data.
If there is an error , it invokes the Fault Message data. Somehow i am not getting the fault message back to PI. In some case i am seeing another window of acknowledgement in PI MONI whcih has this error.
<?xml version="1.0"; encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">NO_BACK_SYSTEM_IN_HOPLIST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)</SAP:Stack> <SAP:Retry>M</SAP:Retry>
</SAP:Error>
How to configure the Fault message type in async scenario. I read the blog but looks like still some config is missing from my end
Also If SAP send the error message & PI receives it, how can we send this error info back to HTTP while remaining in Async mode .
Regards,
Edited by: XI_Fan on Sep 11, 2008 11:22 PM

Thanks all for reply. My scenario is slightly bit different. We are not using BPM and nether synchronous call.
The scenario is 3rd party sends Purchase REQ to PI and PI via Server proxy pushes that to ECC. Once ECC receiver,
it tries to post via BAPI If the BAPI fails aim is to send the data back to 3rd party with error and key so that they should
not do further processing of PR ( like creating PO etc) We have fault message that is being called in SAP ECC when the BAPI is in error. Now I have 3 points here
(1) What configuration are needed to send the information ( fault message data) from SAP to PI ?
(2) What is the best way to send this information back to 3rd party, considering that we are in using ASYNC Proxy
and Async HTTP adapter?
(3) Do we have to create another interface ( Client proxy) to send the data to ECC -> PI ->HTTP.
How this would be done online ( without time gap and without BPM)
I think one way is to call the client proxy code where BAPI BAPI error out( server proxy code)
Do a mapping between this fault message of SAP and fault message of HTTP and than push the data back to HTTP.
Any comments on this appreciated.
Regards,

NO_BACK_SYSTEM_IN_HOPLIST

Similar Messages

Maybe you are looking for