Problem in the scenario SOAP to RFC Syn

Hello All,
i developed one scenario for our client and development is same like below link.
http://www.riyaz.net/blog/xipi-consuming-xi-web-services-using-web-dynpro-part-i/technology/sap/6/
when i test the interface iam getting below error, Please tell me do i need to install any patch in Xi server or do i need to implement any note.
My SAP XI server version 3.0 and Service pack:19
2010-07-19 07:24:57     Operation performed     The message has been received by the mail system. Profile: XI URL: http://xxxxxxxxx:50000/MessagingSystem/receive/AFW/XI credential (User): XIISUSER
2010-07-19 07:24:57     Operation performed     With the connection RFC_http: / / sap.com / xi / XI / System. Attempted placement of the message in the queue of requests.
2010-07-19 07:24:57     Operation performed     Message queued dCaution
2010-07-19 07:24:57     Operation performed     The message has been retrieved from the queue dCaution queries.
2010-07-19 07:24:57     Operation performed     The status of the message has been activated on DLNG
2010-07-19 07:24:58     Operation performed     Paper channel: CC_R_RFC
2010-07-19 07:24:58     Operation performed     MP: entering
2010-07-19 07:24:58     Operation performed     MP: processing local module localejbs/RfcAFBean
2010-07-19 07:24:58     Error     MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
2010-07-19 07:24:58     Error     Exceptions occurred for Adapter Framework: Exception in method process.
2010-07-19 07:24:58     Error     The dissemination of the message to the application via RFC_http: / / sap.com / xi / XI / System failed due to com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method process.:
com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method Process .. Enabled message "Failed".
2010-07-19 07:24:58     Error     The status of the message has been activated on FAIL
2010-07-19 07:24:58     Error     Return of the synchronous error message to the calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method process.: Com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception method in process ..
Thanks and Regards,
Chinna
Edited by: chinnasapxi on Jul 19, 2010 10:55 AM
Edited by: chinnasapxi on Jul 19, 2010 10:56 AM

Hi Cinna,
>just now i checked the RFC it is working
this together with the header "Problem in the scenario SOAP to RFC Syn" is missunderstoobable. But ok, the error is inside RFC adapter: may be it cannot create the DIAG RFC call with the XML what you provided in RTW.
To be shure to have sent the right XML send a message but use a Message Mapping with RFC module as target.
Regards,
Udo

Similar Messages

Sld objects for SOAP to RFC syn.

Hai..All....
I am very new to Xi and i am doing a soap to rfc syn scenario..
pls give me a hint of what type of Sld object are required for the scenarion
like what should be the TS abd BSystem for the scenario and how many BS are required.
can it be done using a single BS for both the communications.
Dear experts i m waiing for ur responses.....
thx
simraan

Hi Simraan,
Can you please let me know the process flow.
Call to RFC is in the SAP system hence you need to create the Business system at SLD. You need to create the Business system and import it into ID and use that one.
Refer the below weblog for SOAP.
For SOAP you first need to generate the WSDL from ID and import that WSDL in IR external definition.
Refer the weblog for SOAP:
How to use webservices in XI
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
How to use SOAP adapter.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Refer the below weblog for RFC:
HTTP to RFC - A Starter Kit /people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
Thnx
Chirag

Error in scenario HTTP - XI - RFC SYN

In the monitor this registering the following 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="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: No response available.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
So that this can happen
Thank's

Hi,
1. Look into the Receiver RFC adapter and check its status.
2. Check the RFC request Message. Is it valid? Try to execute the RFC with the same data and check if it works fine.
Also refer into this blog and cross check the steps,
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
Regards
Bhavesh

To check the problem in the scenario

Hi experts,
I am currnetly working in an enhancement of 2 ODS "ZCCA_O1A" and 'ZOPZ_O1A" to add one more text field EBELP. The infopackage used for loading the data in First ODS existing in production server involves one more ODS ZCCA_O1 and infopackage used for loading the data in Second ODS existing in production server involves one more ODS and one infoCube. All set for delta mechanism. I just need to load updated data in enhanced ODS. So again doing init will disturb the loading in other data targets or not? because of making changes in r/3 side as it is our source system and we are using standard datasources 0CO_OM_OPA_6 AND 0CO_OM_CCA_9.
Please help me ... how to proceed in this scenario.

Hi Andrea,
Stardard adapter for ERP-CIC in CRM is /DSD/VC_REQDATES_GET.
You must have:
Config steps in DSD - Visit Control - Specify Allowed Sales Documents types
RFC connection to CRM
Visit Plans configured and created
Hope this helps you.
Kind regards,
Frank Di Polo

SOAP TO RFC scenario (where the R/3 is not in same network)

Dear Friends,
I am trying to configure a SOAP to RFC (syn).where my SAP R/3 system is in our network .And we dont have all the details for creating a BUSINESS SYSTEM. I tried with BS.but every time I am getting "FAILED TO CALL ADAPTER ENGINE Error ,,,witha no_receiver_aggrement clause".
but i have done the same scenario where the R/3 system is in the same network.
I would like know ,what are the pre-requites for confeguring such a scenarion.And please give a detailed idea...
where what is required and why........
thanks,
jeevan.

Hai Raj,
Thanks for your reply.
My admin says.....the particular IP has full permissions...
One more thing when i am trying to import the BAPI request.I am able to get the data from the remote SAP.
So i believe everything is fine from NETWORK side.
And in the receiver RFC communication side I have seen just by changing the sap IP address to the public IP (Earlier the scenario was working fine with the local SAP system).
I doubt do I have to do in the SLD business system level.
thanks,
jeevan.

Soap- XI- RFC scenario problem

Dear all,
i am configuring a scenario like SOAP->XI->RFC.the third party software send the PM notification message to R3 via XI and the notification is created in R3.now i am facing the problem that the scenario works fine but i can't monitor the message in the Integration server and the message is also not monitored in the adapter engine.
appreciate if anybody can give me some advice.
P.S.
some message can be monitored,but the status is system error.the error message lis like below:
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated??????????????????????????</SAP
thanks for your attentions.
best regards
xiao feng
SAP china

Xiao
For you to see synchronous messages in Xi, you've got to go
>sxmb_adm
>integration engine configuration
>specific configuration
>add a new entry
category : Runtime
param : logging_sync
value : 1
set this settings and you should be able to see messages in sxmb_moni
How have you configured the RFC adapter? Have you set the client and login/password?

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 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 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 error when testing through xml spy

Dear All,
I have a scenario soap-to-rfc.I have created a WSDL using the url as :
http://<myhost>:<port>/XISOAPAdapter/MessageServlet?channel=:BS_Legacy:CC_SOAP_Sender
I am getting an error as mentioned below when i tried to test it throug altova xml spy.
HTTP error: could not POSt file '/XISOAPAdapter/MessageServlet?channel=:BS_Legacy:CC_SOAP_Sender' on server 'host:port' (407).
I have gone through all the related threads which are already there in forum but still couldn't find what's going wrong.
I modified soap:address tag in wsdl
<soap:address location="http://covmdvpi01.mhril.com:50000/XISOAPAdapter/MessageServlet?channel=:BS_Legacy:CC_SOAP_Sender"
Please suggest.
Regards
Kumar

Hi ,
Thanx for quick reply.
I am using 7.3 and created wsdl in ID>Tools->Disply wsdl
my sender business system : BS_Legacy
sender channel : CC_SOAP_Sender
my url
http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Legacy:CC_SOAP_Sender
i have given my host name in the place of host.
my scenario is synchronous and given qos as BE.
Use this URL in soapui and check what you get...do u mean that u want me to test using soap ui?
if so i have tested it in soapui also
new soap ui project-->project name and Initial wsdl/wadl(i have selected wsdl file from system location where i saved it) ...created...given input parmeters then i clicked on Submit Request to Endpoint URL button.
still couln'd see response.
you can see below response what i've got in soapui
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
 td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
 A:link
 A:visited
 A:active
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
 <tr bgcolor="#FFFFFF">
 <td align="left" colspan="2" height="48"> 401 Unauthorized</td>
 </tr>
 <tr bgcolor="#3F73A3">
 <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
 <td height="23"><img width=1 height=1 border=0 alt=""></td>
 <td align="right" height="23">SAP NetWeaver Application Server </td>
 </tr>
 <tr bgcolor="#9DCDFD">
 <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
 </tr>
</table>
 
 Error: Unauthorized
 <a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
 <tr>
 <td valign="top"> Details:</td>
 <td valign="top"><PRE>No details available.</PRE></td>
 </tr>
</table>
</body>
</html>
Thanks
Kumar

SOAP to RFC - Sync Scenario. How to find where the response is going to?

Hello All
I have a SOAP to RFC sync scenario.
In SXMB_MONI, i see that both the initial message and the response message are successfully processed.
But, the SOAP sender is not receiving the response message.
How can i trouble shoot this scenario? How can i findout what is going wrong?
Most importantly, How can i find out the web address of the SOAP sender? I do not see it anywhere.
Thanks

Hi Chandra,
Please check this blog.
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
You can by pass your message through a TCPIP gateway , this will help you to see the message contnet and the SOAP header information.
TCPIPGW application is availabel in one of the SAP notes for Monitoring SOAP adapter. and 2 SAP SDN PI blogs are also there on how to use this application...
Regards
Sunil.

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.

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

Creating Custom SOAP header in the Sender soap scenario

Hello Experts,
Currently i have a SOAP to RFC scenario . In which in the request parameter i have single input parameter. But as per the requirement we need to have some xml parameters in the soap header .
So i want the soap request looks like below,
<?xml version="1.0"?>
-<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
-<SOAP-ENV:Header>
-<ns0:TestHeader xmlns:ns0="http://testcustomer.com">
-<MessageDetails>
<ServiceType/>
<ServiceAction>String</ServiceAction>
<MessageRole rtype=""/>
-<MessageSource>
<SourceName/>
<SourceID idtype=""/>
</MessageSource>
-<MessageDestinations>
-<MessageDestination>
<DestinationID idtype=""/>
<DestinationName/>
</MessageDestination>
</MessageDestinations>
<Property Name=""/>
</MessageDetails>
</ns0:TestHeader>
</SOAP-ENV:Header>
-<SOAP-ENV:Body>
-<m:MT_CERT_IP xmlns:m="http://mydzit.gov.sa/zakat">
<INPUT1>102140000007</INPUT1>
</m:MT_CERT_IP>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Kindly let me know the steps, how can i achieve this ??
I have referred the AddSOAPHeaderBean module but still not received the needed output.
Best Regards,
Amit

Hi Amit,
My few cents.
You have an example in Dimitri Sannen's blog Read SOAP header information doing the mapping with XSLT.
Also, you have an other example like Dev Noronha suggestion, in William Li's blog How to Read SOAP Header Information
Regards.

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

Problem in the scenario SOAP to RFC Syn

Similar Messages

Maybe you are looking for