SOAP- XI- RFC "NO_RECEIVER_CASE_BE"

Hi:
The scenario is SOAP->XI->RFC.
When i try to execute the scenario i get an error "NO_RECEIVER_CASE_BE"
receiver determination is true
Edited by: sky yuyi on Dec 23, 2008 6:36 AM

HI
there are some error log from Message Display Tool (Detail Display) .
Error Category: XI_J2EE_ADAPTER_XI_HANDLER
Error Code :CALL_CONSUMER_ERROR
Audit Log for Message: b6577f11-d31e-11dd-cc12-000f1f6bbad3
Time Stamp Status Description
2008-12-26 07:27:55 Success SOAP: request message leaving the adapter (call)
2008-12-26 07:27:55 Success Application attempting to send an XI message synchronously using connection AFW.
2008-12-26 07:27:55 Success Trying to put the message into the call queue.
2008-12-26 07:27:55 Success Message successfully put into the queue.
2008-12-26 07:27:55 Success The message was successfully retrieved from the call queue.
2008-12-26 07:27:55 Success The message status set to DLNG.
2008-12-26 07:28:03 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: Es konnte kein Empfänger ermittelt werden.
2008-12-26 07:28:03 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.
2008-12-26 07:28:03 Error Transmitting the message using connection http://dlxt:8000/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.
2008-12-26 07:28:03 Error The message status set to FAIL.
pls give me some ideas.

Similar Messages

NO_RECEIVER_CASE_BE error in a SOAP - XI - RFC scenario

Hi gurus:
I'm configuring a SOAP -> XI -> RFC scenario and I'm getting a "NO_RECEIVER_CASE_BE" error when I send a test message using the SOAP adapter.
I have another interfaces using the SOAP adapter of the same XI server and no problems with it. So I think my problem is not into the SOAP adapter.
Thanks to all in advance,
Alejandro Gomez.
Edited by: Alejandro Gómez on May 27, 2008 10:24 AM

Hi:
The entire XML result from MONI is next:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SOAP:Header><SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>synchronous</SAP:ProcessingMode><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:TimeSent>2008-05-27T09:10:24Z</SAP:TimeSent><SAP:Sender><SAP:Service>Openlab_Desarrollo</SAP:Service><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Sender><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>BestEffort</SAP:QualityOfService></SAP:ReliableMessaging><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="AE">af.xi2.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="IS">is.00.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20080527</SAP:Date><SAP:Time>101024</SAP:Time><SAP:Host>xidserver</SAP:Host><SAP:SystemId>XI2</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>023</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>3</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>001</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService><SAP:QIdInternal/><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID"/><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>508</SAP:MessageSizePayload><SAP:MessageSizeTotal>2985</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>508</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>INIT</SAP:InterfaceAction><SAP:RandomNumber>00</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.616</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = xidserver:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.137.73.104</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = S</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = BD9B57A12BCC11DDC738001B7899027A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message </Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"></Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start without given receiver </Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-bd9b57a22bcc11dd95bc001b7899027a#sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
Thanks,
Alejandro Gomez.

SOAP- XI- RFC , while posting soap request thru SPY , getting exception,

Hello friends,
I am trying SOAP->XI->RFC scenario. would like to explain in brief about requirement then let me know if this is correct approach
Our client wants a pull approach from R/3 , for example lets say he wants to get Material Master data from R/3.
So he will send a SOAP request with the material number and r/3 should return back the details.
So we have decided to go with SOAP->XI->RFC approach
That means a sender SOAP Adapter and a receiver RFC adapter,
I have done all the designing, like creating my own DataType,MessagType all interfaces etc.
then i created a Bussiness system of type third party with host name as XI host name to use for sender, and a business system of type Web As ABAP and used one of the R/3 as receiver system.
Doubts: Once i created Soap channel in my sender businees system(where Interface name i gave my Message Interface name and its Namespace), and the receiver channel in my another bussiness system, i created the entire scenario using Configuration Wizard.
NOW THE PROBLEM STARTS.
After clicking Define Web Service , it asks for URL
i gave following url
http://ps3181:50000/XISOAPAdapter/MessageServlet?channel=TPBS_Rohit:soapChannel
TPBS_Rohit is my Sender (third party bussiness system name), and soapChannel is the channel under it.
tell me if this is right
Then in the Message Interface i selected my Message Interface name that i had created in Design for publishing.
MAJOR DOUBT
It Asks for
Service :
Interface Name :
Interface NameSpace :
what do i give here.
this is what i have given
Service : TPBS_Rohit, Sender (third party bussiness system name)
Interface Name : MI_SOAP <again the same message interface name that i have published earlier>
Interface NameSpace : same namespace.
AM i right ???
I am sure somthing is wrong since when i tried sending a SOAP request using XML SPY , this is what i get.
[code]<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>Exception</code>
 <text><![CDATA[
java.lang.Exception: invalid channel (party:service:channel) = TPBS_Rohit:soapChannel
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:498)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>[/code]
Please Let me know where have i gone wrong ?

hi manikandan,friends
i changed the url to http://ps3181:50000/XISOAPAdapter/MessageServlet?channel=:TPBS_Rohit:soapChannel
colon included.
but now i get the following error trace in SPY ..
[code]<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>failed to call the adapter engine</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>DeliveryException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:543)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
 at com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:122)
 at com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)
 at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)
 ... 20 more
Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:366)
 at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:123)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:419)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>[/code]

Why getting "DeliveryExcetion" in SOAP- XI- RFC scenario?

Hi,
This is the scenario :
i) I made a Integration Scenario for updating a Network in Project System(SAP-CE8) from my Web application in SOAP->XI->RFC context. I was able to update it using transaction SE37 on SAP R/3. But when i wanted to update it through XI using web service approach. The Web service returned "DeliveryException" message. Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE. Upon looking into Runtime Workbench in XI ... i found that a call was made across XI in Message Monitoring with "System Failure".
ii) To correct this situation, I reconfigured my XI scenario by deleting the previous sender channel(SOAP) and recreating a new channel(SOAP) and redefined the webservice. This time the problem got worse as I got "ModuleUnknownException" and no entry in message monitoring. However when i tried with the old channel i still got the "DeliveryException" message.
My Queries are following :
a) What are the causes of "DeliveryException".
b) When is the web service created ... after just defining the web service in configuration builder ... or after some time ?
c) Why could it be possible to access the web service using old communication channel path while it was already deleted and change list activated ...
d) What is the possible causes of Module Exception...

Hi Ranjan,
Thanks for reply.
1) You get the System Failure message when the message coming into the Integration server is not valid and if it can't interpret properly.
Check the message you are receiving from the Web Services and your message interface and make sure they are the same or at least correct.
Does it mean that return message from web service is not mapped properly? I have checked all the message mappings are correct in my scenario. What may be the possible causes of "DeliveryException".? Can you please specify any particular thing to be taken care of while doing Message Mapping?
3) Check your Cache, if the changes has actually been activated. Cache may not have been updated hence the old objects still exists.
I had activated the changes and cleared the cache after deleting the communication channel. But still I was able to use that old communication channel.
Regards,
Vikas Khandpur

Error while Testing Soap To RFC

Hi All,
While doing Soap To RFC I got the following error in testing part :
The SOAP response indicates that an error occurred:
Server Error
<detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text><![CDATA[
com.sap.aii.af.lib.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xpi.adapters/NW07_04_REL/src/_soap_application_web_module/webm/api/com/sap/aii/adapter/soap/web/MessageServlet.java#1 $)
 at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:428)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
 ]]></text>
 </s:SystemError>
 </detail>
Please help me out to solve this.
Regards,
Nutan

1 Check your seder soap url.
2 check your host in RFC destination
use these links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79 - how to use soap adapter
RFC -> XI -> WebService - A Complete Walkthrough (Part 1) - rfc to xi to webservice(soap)
RFC -> XI -> WebService - A Complete Walkthrough (Part 2) part-2
Invoke Webservices using SAPXI - invoke the web service
The specified item was not found. - sender rfc adapter steps
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131- [original link is broken] [original link is broken] [original link is broken] Looking for replacing SAP.NET connectors with SAP XI

SOAP to rfc XMLSPY not conneting with PI 7.1 server

hiii gurus,
I am trying soap to rfc scenario. i have completed all the steps.. generated the webservice . now i am testing from XMLSPY
when im sending the soap request to sender i m getting the following error.
"<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text><![CDATA["
"com.sap.aii.af.lib.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xpi.adapters/NW07_04_REL/src/_soap_application_web_module/webm/api/com/sap/aii/adapter/soap/web/MessageServlet.java#1 $)
The Channel has been configured correctly.. i dont know what is the problem... In some conversion i saw something like the userid which im giving should have the role as SAP_XI_APPL_SERV_USER. when i checked it not assigned .. so i assigned manually. but still the same problem exits..
please help me experts.
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Sep 2, 2009 5:20 PM
Edited by: Balaji Pichaimuthu on Sep 2, 2009 5:21 PM

<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions name="aryan_soap_rfc_mi" targetNamespace="http://aryansoap2rfc" xmlns:p1="http://aryansoap2rfc" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:documentation />
- <wsdl:types>
- <xsd:schema targetNamespace="http://aryansoap2rfc" xmlns="http://aryansoap2rfc" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="aryan_req_soap_mt" type="file_req_soap_dt" />
<xsd:element name="aryan_soap_rfc_mt" type="file_res_soap_rfc_dt" />
- <xsd:complexType name="file_req_soap_dt">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/VersionID">5bf85d84978d11deab10001422b066ca</xsd:appinfo>
</xsd:annotation>
- <xsd:sequence>
<xsd:element name="company_code" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
- <xsd:complexType name="file_res_soap_rfc_dt">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/VersionID">811a2213978d11dec05a001422b066ca</xsd:appinfo>
</xsd:annotation>
- <xsd:sequence>
<xsd:element name="company_code" type="xsd:string" />
<xsd:element name="company_name" type="xsd:string" />
<xsd:element name="city" type="xsd:string" />
<xsd:element name="Country" type="xsd:string" />
<xsd:element name="Language" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="aryan_req_soap_mt">
<wsdl:documentation />
<wsdl:part name="aryan_req_soap_mt" element="p1:aryan_req_soap_mt" />
</wsdl:message>
- <wsdl:message name="aryan_soap_rfc_mt">
<wsdl:documentation />
<wsdl:part name="aryan_soap_rfc_mt" element="p1:aryan_soap_rfc_mt" />
</wsdl:message>
- <wsdl:portType name="aryan_soap_rfc_mi">
<wsdl:documentation />
- <wsdl:operation name="aryan_soap_rfc_mi">
<wsdl:input message="p1:aryan_req_soap_mt" />
<wsdl:output message="p1:aryan_soap_rfc_mt" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="aryan_soap_rfc_miBinding" type="p1:aryan_soap_rfc_mi">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
- <wsdl:operation name="aryan_soap_rfc_mi">
<soap:operation soapAction="http://sap.com/xi/WebService/soap1.1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
- <wsdl:input>
<soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="aryan_soap_rfc_miService">
- <wsdl:port name="aryan_soap_rfc_miPort" binding="p1:aryan_soap_rfc_miBinding">
<soap:address location="http://pi71server1.domain.com:50200/XISOAPAdapter/MessageServlet?channel=:aryan_3rdparty_recv_BS:aryam_soap_rfc_sender_cc&version=3.0&Sender.Service=aryan_3rdparty_recv_BS&Interface=http%3A%2F%2Faryansoap2rfc%5Earyan_soap_rfc_sender_cc" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Hii im trying to post my content of my wsdl file.. but in preview mode its loook like above ... actually thats my wsdl file only.. but when post a message .. it coming like above string.
Edited by: Balaji Pichaimuthu on Sep 3, 2009 7:02 AM

Soap to rfc scinario

In general in the soap to rfc scinnario if we will send the purchese order as request and we will get purchase order number as response. after getting the number what we will do with that number. is there is any imporatance. or we have to save that number some where?

Hi Ramakrishna
You can say this scenario like this
PO Number is the invoice created coresponding to your order. If you want you can trace your order by this PO number
and this info is stored in the Data Base
for more details on SOAP to RFC scnario follow these threads
/people/shabarish.vijayakumar/blog/2007/11/07/walkthrough--soap-xi-rfcbapi
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
/people/baris.buyuktanir2/blog/2007/03/06/how-to-create-a-web-service-with-attachments-soap-with-attachments
Regards
sandeep
if helpful kindly reward points

SOAP --XI ---RFC or Java Client Proxy

Hello Gurus,
Need your adivce for a scenario in XI
Scenario --- To implement XI with SAP SCEM(Supply Chain Event Management).
Client is sending data from Web Portal (JSP Page) and wants to integrate with R/3.
(Request from client and Response from R/3 shown again at browser )
Web Portal (JSP Page) is on server A and XI on server B
Queries ---
1. Can I use Java Client Proxy Approach --- proxy --- xi -- rfc approach
If Web Portal (JSP page) is working in server A and XI in server B then can I call xi server from jsp page by passing xi server credential (username,password,bus service) and using sync Interface I can show result back to browser.
2. For SOAP Approach -- SOAP -- XI --- RFC approach
Suppose I need to send two parameters from my Web Portal (JSP page) to xi to R/3 and it will return some result.
Concept of Webservice --- any application (like BAPI ) exposed.
a. Pls tell me all the steps required for IR and ID
b.How can I invoke that generated webservice from my jsp page --- so that my request parameters values go to xi from my jsp page and to R/3 and then result from R/3 to xi and to my jsp page.
Regards

I think second approach is more appropriate ie. SOAP>XI>RFC
Some of the blogs you can refer:
/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
Sender SOAP adapter config: http://help.sap.com/saphelp_nw04s/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Hope this helps,
Rgds,
Moorthy

SOAP to RFC sync scenario

Hello members:
we have a business scenario: SOAP to RFC sync
an external system (ABC) sends documentrequest thru XI SOAP adapter and makes an RFC call to a BAPI and gets back the resposne to the ABC system.we are handling 4 mappings. 1. request msg to a common msg 2. common msg to BAPI request3.bapi response to common msg 4. common msg to response msg(which is same as the req msg)
i have the request msg and common msg as external definitions. I did the following steps and wanted to
know if i am right.
1. there are no data type & msg type needed for this
2. 4 msg interfaces
i) document o/b sysnc
ii) document i/b sync
iii)common o/b sync
iiii) common i/b sync
3) 4 mappings
i) document to common
ii) common to bapi req
iii) bapi resp to common
iiii) common to req/response
4) 3 intf mappings
source intf**********               target intf
i)document o/b               common o/b uses mapping #1
ii)request :common i/b         bapi i/b uses mapping #2
   resposne:bapi i/b           common i/b uses mapping #3
iii) common i/b             document i/b uses mapping # 4
pls provide your inputs if my approach is rite? do i need to have 4 msg intefaces?has any made mappings where 4 mappings are involved ( without BPM)
Thanks in advance

Hi,
I think you will have only 2 interfaces.
1. Sync Outbound interface (SOAP Structure)
    Two message types Req and Res
2. Sync Inbound interface (RFC Structure)
    Two message types Req and Res
Then two message mapping
1. SOAP Request to RFC Request
2. RFC Response to SOAP Response
and finally one Interface mapping.
Thanks,
Prakash

*Soap TO RFC :-Empty SOAP RESPONSE*

Dear Friends,
 I am doing a SOAP TO RFC scenario.And while testing the scenario using SOAP UI TOOL the response is EMPTY its like this.
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Header/>
 <SOAP:Body/>
</SOAP:Envelope>
Monitoring:-
In message monitoring :- its successful
In SXMB_MONI :-Its a checked Flag.
My Mapping is working fine.
Please help me in Tracing the Problem.
Regards,
jeevan

Hi Jeevan,
Did you check the payload in mapping editor? also check the mappings once more and check the thread
In RFc Response no data is coming
Thanks!

Soap to RFC synchronous scenario

Dear experts,
i am doing a SOAP to RFC(BAPI_INTERNALORDER_GETDETAIL) sync scenario and the rfc returns a structure with the records as well as the BAPIRET2 records .
Do i need to use fault message types here ?
If yes what would be its purpose in this scenario ?
Ravi

Hi,
if you have BAPIRET2 then all the errors will be over there
so I guess there is no need to use a fault message
Regards,
Michal Krawczyk

SOAP to RFC Scenario

Hi,
I have a scenario, SOAP to RFC with R/3 as receiver and MDM as sender. From PI side the scenario is working fine, but when the actual data is passed from MDM the data is not getting posted to R/3. Please guide how to test this scenario end to end. Also please tellme how to check if the data si posted to R/3 where RFC adapter used.
Eg - we have T-code we02 to check whether an Idoc is posted to R/3... In a similar way please tell me how to check for this scenario.
Thanks

hi,
first go to Runtime Workbench>Component Monitoring>Adapter Engine>Communication Channel Monitoring>check the SOAP sender channel
If no problem,go to SXI_MONITOR and check if exist any record of your escenario. if no, go again to Channel Monitoring and check the RFC Channel.
Now if you send the data from MDM and you cannot trace it in the first Step you have a problem in the MDM when it send data, so you must trace whats happening there.
Let usknow

Soap to rfc scenario error

Hi PI Experts,
For the first time i was doing soap to rfc scenario. I have created all the objects in the ID and in the IR and also created a web service from ID an then i have saved the wsdl in my system. I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
so kindly please help me to solve this scenario.
Thanks & Regards,
B.Srinivas Prasad.

I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
Make sure that its in the below format :
From SAP help :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
and check Sender Soap Channel Status is it activated/not and check Cache Status

SOAP to RFC scenario (SFDC - ECC synch)

Working on a SFDC to ECC synch scenario using SOAP to RFC interface. I generated the WSDL for SFDC team and tested on soapUI, I am able to see the successful request/response structure in sxmb_moni.
However, when the SFDC team is sending the request in real time from SFDC, the request is successful in SFDC but not reaching PI and hence there is no response. The error I see in sxmb_moni for this is
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PROXY_NOT_ALLOWED_ON_IS</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Proxy calls are not permitted on sender or receiver side on the IS (client)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Are there any additional setting need to be done.
Please guide on this issue . Thanks
Edited by: jbagga on Nov 14, 2011 7:42 AM

SFDC sending request to PI. SFDC Request is not hitting PI, neither traceable in MONI or RWB.
SFDC request is not hitting PI . The ForeFront has allowed the SFDC IP range to target PI using reverse proxy rules. But SFDC and Forefront both get the "HTTP 500 internal server error"
The question is , I am helpless until the request is monitored anywhere in MONI or RWB_communication channel
Also SFDC receives some fault message error along with HTTP 500 i.e. Header Missing in Soap Message Header. In this case, also if its PI related error there should be at least some track of request hitting PI in MONI or RWB. also tried creating a WSDL with PI username and password in the WSDL under Header tags, still the same situation
ALL Ports are open by BASIS team.
Can someone point out any helpful solution. URGENT !! Thanks a ton in advance.
EVERYTHING , THE ENTIRE REQUEST/RESPONSE STRUCTURE WORKS PERFECT WITH SOAPUI.

SOAP to RFC scenario prolem

Hello Guru's
 Im trying the basic SOAP TO RFC scenario, in which RFC is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL
and the out bound interface consists of only basic feilds i.e.
REQUEST MESSAGE TYPE : AirlineID
 ConnID
 Fldate
RESPONSE MESSAGE TYPE : Ecnofree
 Bussfree
 Firstfree
and no fault message type.
i created the scenario with out any errors, and i defined webservies in ID with the following URL
http://starxi:50000/XISOAPAdapter/MessageServlet?Channel=:SXI_BS_SOAPRFC_SENDER:SOAP_RFCSENDER
it is according to the following syntax
htt://<xi server>:<J2EE Port>/XISOAPAdapter/MessageServlet?channel=:<sender business system>:communication channel.
But im not able to post SOAP request to the xi server. it is saying following error
"SOAP Request cannot be posted <with url > 403"
403 is the error code.
please can anyone help me in overcoming the above problem. and where iam wrong.
Thanks in advance
arjun

Hi!
Please check once again reg SOAP URL while generating the WSDL.
[http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>]
[Re: Using SOAP Sender adapter in PI 7.1]
1. Check whether your SOAP URL s correct or not which you are giving in the receiver SOAP adapter
2. Also check you are giving the SOAP action in the receiver SOAP adatper correctly or not.
3. Finally check the SOAP service is activei or not in SAP>BC>XI-->SOAP in ABAP stack
4. Since FIle is only for ASYN comm and while using FILE for sync interface you need to pass module paramters in the Sender File CC
ERROR 403 means::
This error will be comming mostly in the synch scenarios like SOAP to RFC - SOAP and FIle to RFC--FILE
when the target system is down or service is inactive.
Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484
u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726
u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not correctly deployed.
Regards::
Amar Srinivas Eli

SOAP- XI- RFC "NO_RECEIVER_CASE_BE"

Similar Messages

Maybe you are looking for