RFC - XI - SOAP ERROR.

I get a difficult error now, following is the error.
my scerio is rfc -> xi -> soap.
http://90.3.9.11:7001/axis/DocumentService.jws?wsdl
  <?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions targetNamespace="http://90.3.9.11:7001/axis/DocumentService.jws" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://90.3.9.11:7001/axis/DocumentService.jws" xmlns:intf="http://90.3.9.11:7001/axis/DocumentService.jws" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <!--
WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)
  -->
- <wsdl:message name="exportFileBySapIDRequest">
  <wsdl:part name="userID" type="xsd:string" />
  <wsdl:part name="mySingleID" type="xsd:string" />
  <wsdl:part name="sapID" type="xsd:string" />
  </wsdl:message>
- <wsdl:message name="exportFileBySapIDResponse">
  <wsdl:part name="exportFileBySapIDReturn" type="xsd:string" />
  </wsdl:message>
- <wsdl:portType name="DocumentService">
- <wsdl:operation name="exportFileBySapID" parameterOrder="userID mySingleID sapID">
  <wsdl:input message="impl:exportFileBySapIDRequest" name="exportFileBySapIDRequest" />
  <wsdl:output message="impl:exportFileBySapIDResponse" name="exportFileBySapIDResponse" />
  </wsdl:operation>
  </wsdl:portType>
- <wsdl:binding name="DocumentServiceSoapBinding" type="impl:DocumentService">
  <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="exportFileBySapID">
  <wsdlsoap:operation soapAction="" />
- <wsdl:input name="exportFileBySapIDRequest">
  <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://DefaultNamespace" use="encoded" />
  </wsdl:input>
+ <wsdl:output name="exportFileBySapIDResponse">
  <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://90.3.9.11:7001/axis/DocumentService.jws" use="encoded" />
  </wsdl:output>
  </wsdl:operation>
  </wsdl:binding>
- <wsdl:service name="DocumentServiceService">
- <wsdl:port binding="impl:DocumentServiceSoapBinding" name="DocumentService">
  <wsdlsoap:address location="http://90.3.9.11:7001/axis/DocumentService.jws" />
  </wsdl:port>
  </wsdl:service>
  </wsdl:definitions>
Design **************************************
DT_exportFileBySapIDRequest
--> exportFileBySapIDRequest
     -> userId
     -> mysingleId
     -> sapId
DT_exportFileBySapIDResponse
--> exportFileBySapIDResponse
     -> exportFileBySapIDReturn
exportFileBySapIDRequest(Message Types)
exportFileBySapIDResponse(Message Types)
MI_RFC_TO_Webservice (Synchronous Inbound)
exportFileBySapIDRequest
exportFileBySapIDResponse
MM_RFC_TO_Webservice_Req
Z_XI_FI_MAILTEST  <----> exportFileBySapIDRequest
MM_RFC_TO_Webservice_Resp
exportFileBySapIDResponse <-----> Z_XI_FI_MAILTEST.response
IM_RFC_TO_Webservice
Z_XI_FI_MAILTEST     MI_RFC_TO_Webservice
Configuration ************************************
Communication Channel
sender  : SAP_Sender_RFC_SEP
receiver : RFC_TO_Webservice
              target url : http://90.3.9.11:7001/axis/DocumentService.jws
sxmb_moni Trace ************************************
  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Response
  -->
- <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="T">Party normalization: receiver</Trace>
  <Trace level="1" type="T">Receiver scheme external =</Trace>
  <Trace level="1" type="T">Receiver agency external =</Trace>
  <Trace level="1" type="T">Receiver party external =</Trace>
  <Trace level="1" type="T">Receiver party normalized =</Trace>
  <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!--  ************************************
  -->
  <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 = sscxidev:8001</Trace>
  <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
  <Trace level="2" type="T">Remote address = 90.3.9.13</Trace>
  <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!--  ************************************
  -->
  <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!--  ************************************
  -->
  <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 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 = SXD</Trace>
  <Trace level="3" type="T">client = 001</Trace>
  <Trace level="3" type="T">language = E</Trace>
  <Trace level="3" type="T">user = PIAFUSER</Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9</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 level="1" type="T">Message-GUID = 5B0889208B6711DBC8380018717400ED</Trace>
  <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
  <Trace level="1" type="T">QOS = EO</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">QOS = EO</Trace>
  <Trace level="3" type="T">Message-GUID = 5B0889208B6711DBC8380018717400ED</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">Get definition of internal pipeline = SAP_CENTRAL</Trace>
  <Trace level="3" type="T">Generate prefixed queue name</Trace>
  <Trace level="1" type="T">Queue name : XBTI0004</Trace>
  <Trace level="1" type="T">Generated prefixed queue name = XBTI0004</Trace>
  <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
  <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
  <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
  <Trace level="3" type="T">Call qRFC .... MsgGuid = 5B0889208B6711DBC8380018717400ED</Trace>
  <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
  <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
  <Trace level="3" type="T">OK.</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="T">Going to persist message</Trace>
  <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
  <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
  <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
  <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="3" type="T">Version number = 000</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">Persisting message Status = 001</Trace>
  <Trace level="3" type="T">Message version 000</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
  <Trace level="3" type="T">Trace object available again now. OK.</Trace>
  <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
  <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
  <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
  <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
  </Trace>
  <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
  <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
  <Trace level="2" type="T">Increment log sequence to 001</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
  <Trace level="3" type="T">system-ID = SXD</Trace>
  <Trace level="3" type="T">client = 001</Trace>
  <Trace level="3" type="T">language = E</Trace>
  <Trace level="3" type="T">user = PIAFUSER</Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9</Trace>
  <Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
  <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 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 level="3" type="T" />
  <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 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 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 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 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 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 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 level="3" type="T" />
  <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
  <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 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 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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <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="2" type="T">Classic Receiver Determination via Rules.</Trace>
  <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
  <Trace level="2" type="T">...valid Receiver w/o Condition: - MYS</Trace>
  <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
  <Trace level="2" type="T">Number of Receivers:1</Trace>
  </Trace>
  </Trace>
  </Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
  </Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
  <Trace level="3" type="T">Persisting message after plsrv call</Trace>
  <Trace level="3" type="T">Message-Version = 001</Trace>
  <Trace level="3" type="T">Message version 001</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
  <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
  <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
  <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
  <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_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_ID_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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
  <Trace level="1" type="T">I N T E R F A C E - 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">Check conditions for (Inb: Party Srvc If) MYS MI_MYS_Resp_IN_Async</Trace>
  <Trace level="2" type="T">...valid InbIf without Condition: MI_MYS_Resp_IN_Async</Trace>
  <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
  </Trace>
  </Trace>
  </Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
  </Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
  <Trace level="3" type="T">Persisting message after plsrv call</Trace>
  <Trace level="3" type="T">Message-Version = 002</Trace>
  <Trace level="3" type="T">Message version 002</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </Trace>
  <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!--  ************************************
  -->
  <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
  <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
  <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
  <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
  <Trace level="3" type="T">PLSRVTYPE =</Trace>
  <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
  <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
  <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
  <Trace level="2" type="T">got property produced by receiver determination</Trace>
  <Trace level="1" type="T">number of receivers: 1</Trace>
  <Trace level="1" type="T">Single-receiver split case</Trace>
  <Trace level="1" type="T">Post-split internal queue name = XBTO6___0000</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
  <Trace level="1" type="T" />
  <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
  <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
  <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
  <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">Persisting message Status = 012</Trace>
  <Trace level="3" type="T">Message version 003</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
  <Trace level="3" type="T">Trace object available again now. OK.</Trace>
  <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
  <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
  <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
  <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
  </Trace>
  <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
  <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
  <Trace level="2" type="T">Increment log sequence to 005</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
  <Trace level="3" type="T">system-ID = SXD</Trace>
  <Trace level="3" type="T">client = 001</Trace>
  <Trace level="3" type="T">language = E</Trace>
  <Trace level="3" type="T">user = PIAFUSER</Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!--  ************************************
  -->
  <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 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 level="3" type="T" />
  <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 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 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 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 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 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 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 level="3" type="T" />
  <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
  <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
  <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
  <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
  <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
  <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
  <Trace level="3" type="T">PLSRVTYPE =</Trace>
  <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
  <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
  <Trace level="2" type="T">......attachment XI_Context not found</Trace>
  <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
  <Trace level="3" type="T">Object ID of Interface Mapping BA9D2B14DB953699A6F72BB0C992416E</Trace>
  <Trace level="3" type="T">Version ID of Interface Mapping CAB00A010BF111DBCC73F1B85A1E0C79</Trace>
  <Trace level="1" type="T">Interface Mapping http://xi.mySingle.draft.send IM_MYS</Trace>
  <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_MYS_</Trace>
  <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
  <Trace level="2" type="T">Mode 0</Trace>
  <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_MYS_.</Trace>
  <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_MYS_</Trace>
  <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_MYS_ completed. (executeStep() of com.sap.xi.tf._MM_MYS_</Trace>
  <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
  </Trace>
  </Trace>
  </Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
  </Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
  <Trace level="3" type="T">Persisting message after plsrv call</Trace>
  <Trace level="3" type="T">Message-Version = 005</Trace>
  <Trace level="3" type="T">Message version 005</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
  <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
  <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
  <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
  <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
  <Trace level="3" type="T">PLSRVTYPE =</Trace>
  <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
  <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
  <Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
  <Trace level="2" type="T">Cache Content is up to date</Trace>
  <Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
  <Trace level="2" type="T">-MYS</Trace>
  <Trace level="2" type="T">-MYS</Trace>
  <Trace level="2" type="T">http://xi.mySingle.draft.send.MI_MYS_Resp_IN_Async</Trace>
  <Trace level="2" type="T">Channel found: - MYS - FS_MysEmpty</Trace>
  <Trace level="2" type="T">no header mapping defined</Trace>
  </Trace>
  </Trace>
  </Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
  </Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
  <Trace level="3" type="T">Persisting message after plsrv call</Trace>
  <Trace level="3" type="T">Message-Version = 006</Trace>
  <Trace level="3" type="T">Message version 006</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
  <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
  <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
  <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
  <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
  <Trace level="3" type="T">ADRESSMOD = SD</Trace>
  <Trace level="3" type="T">P_CLASS =</Trace>
  <Trace level="3" type="T">P_IFNAME =</Trace>
  <Trace level="3" type="T">P_METHOD =</Trace>
  <Trace level="3" type="T">FL_LOG =</Trace>
  <Trace level="3" type="T">FL_DUMMY = 0</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Unknown channel type: File</Trace>
  <Trace level="3" type="T" />
  <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
  <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
  <Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
  <Trace level="3" type="T">ADRESSMOD = SD</Trace>
  <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!--  ************************************
  -->
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
  <Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
  <Trace level="2" type="T">return fresh values from cache</Trace>
  <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
  <Trace level="3" type="T">URL = http://sscxidev:50100/MessagingSystem/receive/AFW/XI</Trace>
  <Trace level="3" type="T">User = PIISUSER</Trace>
  <Trace level="3" type="T">Cached = X</Trace>
  <Trace level="3" type="T">Creating HTTP-client</Trace>
  <Trace level="3" type="T">HTTP-client: creation finished</Trace>
  <Trace level="3" type="T">Security: Basic authentication</Trace>
  <Trace level="3" type="T">Serializing message object...</Trace>
  <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
  <Trace level="3" type="T">HTTP-client: request sent</Trace>
  <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
  <Trace level="3" type="T">HTTP-client: response received</Trace>
  <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
  <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
  <Trace level="3" type="T">Deserializing message object...</Trace>
  <Trace level="3" type="T">HTTP-client: closing...</Trace>
  </Trace>
  </Trace>
  </Trace>
  </Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
  </Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
  <Trace level="3" type="T">Persisting message after plsrv call</Trace>
  <Trace level="3" type="T">Message-Version = 007</Trace>
  <Trace level="3" type="T">Message version 007</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </Trace>
  <Trace level="3" type="T">Async processing: skip mapping of response</Trace>
  </Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="T">Async processing completed OK.</Trace>
  <Trace level="3" type="T">system-ID = SXD</Trace>
  <Trace level="3" type="T">client = 001</Trace>
  <Trace level="3" type="T">language = E</Trace>
  <Trace level="3" type="T">user = PIAFUSER</Trace>
  <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9</Trace>
  <Trace level="1" type="T">----
</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--  ************************************
  -->
  <Trace level="3" type="T">Persisting message Status = 003</Trace>
  <Trace level="3" type="T">Message version 008</Trace>
  <Trace level="3" type="T">Pipeline CENTRAL</Trace>
  </SAP:Trace>
Thanks.

Have you cheked this blogs?
If you havenot,
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2

Similar Messages

  • RFC to SOAP error

    Hi,
      I am configuring Rfc to SOAP scenario. After all the configuration steps are done as they are required. When I am testing the scenario i.e when I am executing RFC in in one of R3 instance system message is going to XI but message status in XI shows in "logversion" neither green nor red status in gray color. After techinal routing step, call to adpater is not showing. When I watch adapter status for RFC. I observe Http status code: 500 Time out. Appreciate for your reply.
    Thanks,
    Mallikarjun.M

    Hi,
    The SOAP adapter will remain grey until a message is sent through it.
    You are getting a Timeout message so I would check 2 things:
    1. The firewall is not stopping the communication between XI and the destination for your Web service.
    2. You URL for the Web Service is correct.
    I would also set up a dummy SM59 destination in XI for the destination system with the IP address / DNS name and see if you can connect. If you cannot you are likely to have firewall issues.
    Kind regards
    Colin.

  • Error in SAOP adapter : RFC to SOAP Synch Scenario

    Hi Experts,
    Scenario is "RFC to SOAP Synch".
    For creating this following this link : **************** - Scenario on RFC to SOAP
    Trying to send XML to SOAP receiver.
    Using Below details for SOAP:
    Website : http://www.webservicex.net/WS/WSDetails.aspx?WSID=59&CATID=4
    Target URL : http://www.webservicex.net/SendSMS.asmx?WSDL
    SOAP Action: http://www.webserviceX.NET/SendSMSToIndia
    But when I try to send showing this error:
    "Error in processing caused by: com.sap.aii.af.lib.mp.module.ModuleException: call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket".
    Any one please suggest how resolve this issue?
    Is there any setup necessary in PI server to send message through SOAP?
    Thanks,
    Arthita

    Is there any setup necessary in PI server to send message through SOAP?
    No
    Solution
    Check if there are any firewall rules in place which are restricitng the PI system to connect with the URL
    : http://www.webservicex.net/SendSMS.asmx?WSDL
    Suggestion
    Copy paste this URL in browser and verify if it is accessible
    Sourabh

  • Error in Interface Sync RFC-XI-SOAP

    Hi,
    I have an interface RFC - XI - SOAP Sync.
    The error appears only in PRD environment and is intermittent error.
    Follow the message error in sxmb_moni:
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Security.SecurityException: The event source ExceptionManagerInternalException does not exist and cannot be created with the current permissions. ---> System.Security.SecurityException: Requested registry access is not allowed. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at System.Diagnostics.EventLog.CreateEventSource(String source, String logName, String machineName, Boolean useMutex) at System.Diagnostics.EventLog.CreateEventSource(String source, String logName, String machineName) at System.Diagnostics.EventLog.CreateEventSource(String source, String logName) at Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher.VerifyValidSource() --- End of inner exception stack trace --- at Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher.VerifyValidSource() at Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher.Publish(Exception exception, NameValueCollection additionalInfo, NameValueCollection configSettings) at Microsoft.ApplicationBlocks.ExceptionManagement.ExceptionManager.PublishInternalException(Exception exception, NameValueCollection additionalInfo) at Microsoft.ApplicationBlocks.ExceptionManagement.ExceptionManager.Publish(Exception exception, NameValueCollection additionalInfo) at Microsoft.ApplicationBlocks.ExceptionManagement.ExceptionManager.Publish(Exception exception) at mServices.WebServices.mServices.CancelServiceOrderList(OrderTypeCancelTO[] orders) --- End of inner exception stack trace ---</SAP:AdditionalText>
    Could you help me?
    Thank a lot.
    Maicon.

    > {quote:title=Rosa Maicon wrote:}
    > Hi,
    > I have an interface RFC - XI - SOAP Sync.
    > The error appears only in PRD environment and is intermittent error.
    > The event source ExceptionManagerInternalException does not exist and cannot be created with the current permissions.
    This looks like a permission error for the user role provided in production. try sending soap request from web client tool and see whether you get the same error.
    Check whether you have all the permissions required and also check whether there is WS security in the production environment.
    Regards,
    Pavan

  • RFC to SOAP Scenario error

    Hello ALL
    I am trying to working in RFC to SOAP scenario in sap pi 7.31 single stack system.with help of blog **************** - Scenario on RFC to SOAP
    i am trying to pass input values from ECC through RFC  to web service .
    while sending data using  function module from ECC system i got following error
    thnx in advance

    Hi Ganesh,
    are you getting any error is SM58? Please check the below blog for configuration
    Michal's PI tips: How do you activate ABAP Proxies with AEX - simplified version
    IDOC_AAE To File with all Configurations
    the below discussion will be useful
    RFC to FILE(7.3) single stack

  • RFC to SOAP sync error

    Hi All,
    I am doing the RFC to SOAP sync scenario. request R3 data is coming to XI and its triggering to SOAP receiver.
    Information SOAP: continuing to response message e9598290-a14f-11df-969a-00145e474044
    Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    i have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request and soap response to file response.
    the same way i have done the RFC request to soap request and soap response to rfc response.
    in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP.
    I have tested the test mapping and its working fine.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  XML Validation Outbound Channel Response
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>application fault</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="http://www.webMethods.com/2001/10/soap/encoding">exception</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    the r3 request stacture is:
    <filed1>
    <filed2>
    <filed3>
    <ITEM>
    <ITEM1>
    <ITEM22>
    </ITEM>
    the soap request stacture is:
    <filed1>
    <filed2>
       <Header>
        <filed1>
        <filed2>
        <filed3>
       </header>
       <Item>
        <item1
        <item2>
        <item3>
       </Item>
    </field2>
    </field1>   
    is there any issue with mapping?
    RFC sender CC error is Error in processing caused by: com.sap.aii.adapter.rfc.core.server.RfcServerException: got unexpected document type:DOC_TYPE_UNKNOWN
    Can you pls let me know the some inputs to reslove this issue
    Thanks,
    Venkat

    have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request
    and soap response to file response. the same way i have done the RFC request to soap request and soap response to rfc
    response.
    FILE to SOAP Sync scenario....did you use RequestResponseBean and are you using the same to process RFC to SOAP Sync scenario? If yes, then you dont need the RequestResponseBean for RFC <--> SOAP.
    in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP. I have tested the test mapping
    and its working fine. - - Application APPLICATION_ERROR application fault exception M the r3 request stacture is: the soap
    request stacture is: is there any issue with mapping?
    I hope you have included a mapping program for Request Mapping and also for Response Mapping in the Interface/ Operation Mapping and included the same in Interface Determination!
    Regards,
    Abhishek.

  • RFC to SOAP Scenarion : Error while communication

    Hi Experts,
    We are trying RFC to SOAP Scenario. When we trigger the message from RFC we get error as Communication error . when we re-activate the Sender communication channel in PI , the program-ID gets registered and we can trigger the message. This problem we are facing regularly and we have to re-activate the Sender RFC communication channel everytime.
    How can we solve this problem.
    Regards,
    Syed

    Have you tried increasing the parameter "Maximum Connections"? Is it possible that the same program ID is used for more than one scenarios?
    Regards,
    Prateek

  • Error RFC to SOAP Scenario

    Hi Experts,
    I am getting an error while dealing with RFC to SOAP scenario::
    soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
    IS it problem from the webserver in sending the response?
    Please suggest.
    Thanks & Regards,
    Sushama

    Hi Suraj,
    Thanks for the imputs.
    We are given with the webservice by separate team, also I am accessing the application via Citrix. I cant test the WS outside the client network and in client desktop they haven't installed Altova Xml Spy
    Request and response both are generated in Moni. It seems problem in receiving response only ?? WS url is also correct.
    Regarding Receiver Soap parameters:
    I have checked adapter specific identifiers and Variable transport binding.
    Please suggest, if this is problem with the WS, I need to check with the team.
    Thanks & Regards,
    Sushama

  • RFC to SOAP - Mapping Error

    Hi All
    I am working on RFC to SOAP Scenorio.
    The requirement is RFC will make a querry and all the vendor details will be received in the return table structure of the RFC Function module.
    There will be multiple entries in the Return table.
    I am getting the sucess message and the number of records is also matching.
    But the Data is not getting mapped to the right field in the Return table.
    But if i see the SXMB_MONI response message, Data is correctly mapped
    Regards
    Madhan D

    You are getting the right XML from the target and its not getting placed correctly in the return tables.
    The only problem can be with the ABAP code/logic which you wrote for assigning and populating the response values into the tables.
    Regards
    Sunil.

  • RFC to SOAP Interface - Problem in Request Message Mapping

    Dear All,
    We are working on RFC to SOAP Scenario i.e. pulling out data from an WebService from SAP via PI.
    In Request Message Mapping, when the wsdl file is uploaded as Target Message, the wsdl request shows the nested elements like below.
    <Request>
       <Request_New>
          <PAR1>xyz</PAR1>
          <PAR2>123</PAR2>
       </Request_New>
    </Request>
    But the desired Request should go like below.
    <Request>
       <PAR1>xyz</PAR1>
       <PAR2>123</PAR2>
    </Request>
    Hence it gives an error saying that the tag Request_New does not exist.

    Dear All,
    Our target webservice cotains multiple methods.
    The every method contains its corresponding request, response and SQL ecxeption as messages.
    In case of request structures, every method (except crmPaymentReceived) contains more than 1 root element.
    So while calling those methods having more than 1 root element, the additional header tag will always appear(not avoidable) in the request coming from SAP PI.
    For Example,
    Request Structure for method u2018isLoginIdExistu2019 (having more than 1 root element)
    <?xml version="1.0" encoding="UTF-8"?>
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
    <ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing">      -
    >>>>>  u201CThis Header tag will always appear u201D
    <isLoginIdExistin0>asp</isLoginIdExistin0>
    <isLoginIdExistin1>1</isLoginIdExistin1>
    </ns1:isLoginIdExistRequest>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the error(saying that ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing" does not exists).
    Request Structure for method u2018crmPaymentReceivedu2019 (having only 1 root element)
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=http://www.w3.org/2001/XMLSchema-instance xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soap:Body>
    <ns1:crmPaymentReceivedin0 xmlns:ns1="http://netpricing">false</ns1:crmPaymentReceivedin0>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the success response.
    I tested their wsdl URL in XMLspy and wizdal(a wsdl testing tool), it shows request in the format having only root elements and not the header tags.
    But header tags will always appear when header tag contains more than 1 root element.
    Can anybody suggest me how do I tackle this?
    Thanks in Advance.

  • RFC TO SOAP SCENARIO

    Dear Experts,
    I am facing the Following error for RFC to SOAP Scenario, i Tried
    1. Full Cache Refresh
    2.Delete and create Sender Agreement Again
    3.Specifying the Program id Again
    yet the Scenario is not Working, could you please help me in Resolving this at the Earliest
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'ISU64', toParty '', toService '', interface 'YGVK_SEND_WS_TO_WS', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_YGVK_SENDER_WS_TO_WS' (channelId f1219fd41be734a2a72cd3ddcb779475)
    Regards,
    Vijay Karthik G

    Hi,
    copy the sender agreement to the same one but in party field
    remove the " * " (it has to be empty)
    test it and let me know
    Regards,
    Michal Krawczyk

  • RFC To SOAP Synchronus Scenario

    Hi,
    I am doing the scenario like RFC To SOAP sync.When i am running the RFC in R/3 it's going to dump. In the dump it's giving the message             
    "senderAgreement not found: lookup of binding via CPA-cache failed for" .
    Thanks & Regards,
    Mouli.

    HI Chandra,
    Check these links
    XI3.0 Sender RFC Adapter fails
    Re: RFC as Sender Problem
    Re: RFC Call from R/3 to XI
    Re: RFC adapter as sender
    RFC Sender adapter - Sender agreement not found Error
    Hope they help to fix your issue
    Regards
    Vishnu

  • RFC  to SOAP Scenario -- Delivery Exception

    Hi All,
    I am working on RFC to SOAP scenario.
    On executing a program in the SAP system, the system is throwing a dump stating                                                   "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML".
    I feel that the error is because of the response not being sent back by the webservice. On executing the webservice independently, it is working fine i.e. sending back the response.
    Can anyone suggest the possible reasons for this error and what needs to be done to rectify this?
    Thanks,
    Ravi Kiran

    the return from the Web service must have been an HTML(may be an error page or something)...What kind of authorization does this WS look for ?
    Pls check these threads...
    SOAP Receiver Adapter Proxy Settings
    Receiver SOAP Adapter Error: invalid content type for SOAP: TEXT/HTML

  • RFC TO SOAP ASYNCHRONOUS

    Hi all,
    My scenario is rfc to soap asynchronous.  when i am sending data from rfc it is showing success in sxmb_moni and in RWB.
    but it is reaching to third party webservice but it is not taking the data. then it is showing following error in SXMB_MONI response what was the issue
       *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Call Adapter*
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>HTTP 415 Unsupported Media Type</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    and the version are PI 7.1,  and third party webservice is  Oracle 11g and weblogic server 10.3.2.0
    and my next question is in same scenario
    I checked using TCP Gateway PI to third party webservice .it is showing following error
    This is posted data
    POST /AdvancedMeteringInfrastructure-UtilitiesDeviceERPSmartMeterBulkCreateRequest-context-root/UtilitiesDeviceERPSmartMeterBulkCreateRequest_OutPort?wsdl HTTP/1.0
    *Accept: /*
    Host: 172.16.5.211:7002
    User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
    content-id: payload-a3368e536e4311dfa3dc00237d5e14c0(at)sap.com
    content-type: application/xml
    Content-Length: 1662
    SOAPACTION: "http://sap.com/xi/IS-U/Global2/UtilitiesDeviceERPSmartMeterBulkCreateRequest_Out"
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:UtilitiesDeviceERPSmartMeterBulkCreateRequest xmlns:ns1="http://sap.com/xi/SAPGlobal20/Global"><MessageHeader><ID schemeID="Device" schemeAgencyID="www.infotech.com">4446364534314343</ID><UUID schemeID="Device" schemeAgencyID="www.infotech.com">DF6E41CC-79E7-81F1-B9A3-0013725B3FAB</UUID><CreationDateTime>2010/06/02 T18:07:42</CreationDateTime><TestDataIndicator>true</TestDataIndicator><ReconciliationIndicator>true</ReconciliationIndicator><SenderBusinessSystemID>SLD_B001</SenderBusinessSystemID><RecipientBusinessSystemID>SLD_B002</RecipientBusinessSystemID></MessageHeader><UtilitiesDeviceERPSmartMeterCreateRequestMessage><MessageHeader><ID schemeID="Device" schemeAgencyID="www.infotech.com" schemeAgencySchemeAgencyID="001">4446364534314343</ID><UUID schemeID="Device" schemeAgencyID="www.infotech.com">DF6E41CC-79E7-82F1-B9A3-0013725B3FAB</UUID><CreationDateTime>2010/06/02 T18:07:42</CreationDateTime><TestDataIndicator>true</TestDataIndicator><ReconciliationIndicator>true</ReconciliationIndicator><SenderBusinessSystemID>SLD_B001</SenderBusinessSystemID><RecipientBusinessSystemID>SLD_B001</RecipientBusinessSystemID></MessageHeader><UtilitiesDevice><ID schemeID="DEID" schemeAgencyID="115">1200000120001564</ID><StartDate>2010.06.02</StartDate><EndDate>9999.12.31</EndDate><SerialID>1200000120001564</SerialID><MaterialID schemeID="MaterialID" schemeAgencyID="MPL_002">85</MaterialID><ProductUniqueItemID schemeID="Smart Meter" schemeAgencyID="MPL_002">SM1165HS</ProductUniqueItemID></UtilitiesDevice></UtilitiesDeviceERPSmartMeterCreateRequestMessage></ns1:UtilitiesDeviceERPSmartMeterBulkCreateRequest>
    ERROR
    HTTP/1.1 415 Unsupported Media Type
    Connection: close
    Date: Wed, 02 Jun 2010 12:26:33 GMT
    Content-Length: 0
    X-ORACLE-DMS-ECID: 0000IZsc9VaF^6WFLzyGOA1Bpe3k00007J
    X-Powered-By: Servlet/2.5 JSP/2.1
    Please give me the solution.
    Thanks
    Anil

    Hi,
         looks like there can be a problem with the webservice provider to which you are passing the data via SOAP adapter...
    check that webservice using some other tools like XMLSPY or SOAPUI...
    if everything is fine with that then test the entrie scenario by passing the same data...then you will get to know the exact problem...
    HTH
    Rajesh

  • RFC-to-SOAP webservice using HTTPS

    Hi experts,
    I have a RFC-to-SOAP (sync) and the URL of the webservice is using HTTPS. I'm not the owner of the webservice.
    Encountered these errors
    - for sender comm :
    com.sap.aii.af.ra.ms.api.DeliveryException: Peer sent alert: Alert Fatal: illegal parameter
    - receiver comm :
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Peer sent alert: Alert Fatal: illegal parameter: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: illegal parameter
    We are not using certificate authentication so I don't think that's the cause.
    Have checked that the https is running ok for ABAP but I don't think that got anything to do with the errors. Is there something wrong with SSL setting for J2EE? If yes, how may I check?
    Are there some parameters to be set up? In the RFC sender comm & SOAP receiver comm, I do not find any special settings for https.
    I have read this link : http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm. Is it necessary to set the Exchange Profile Parameters? My BASIS colleague is now checking it.
    Thanks for reading and will appreciate any advice!

    Thanks Prateek for the quick reply!
    Re HTTPS certificate, do you mean the cert for my XI server or the cert from the web service?
    I have tested calling the web service using SOAPUI and it works fine without using the cert given by the web service (which is expired anyway)...

Maybe you are looking for

  • Commit session

    Hi I have some requirement such that i have to fill a table thru DBlink and number of records are too high... Is there any way i can Commit the session after regular intervals say after every 1 million recrds or so. Thanks in advance.

  • Scaling object by %

    I have pairs of objects of different sizes that have to be scaled in proportion to each other and, as one can't move the rules in Pages 5 [cf PageMaker] this has to be done visually for one and then to the same % for the other. Even if both objects a

  • Google Mobile App broken

    Since 5/2/11, the Google Moble app returns results in which the page links are not active, i.e. they will not open.  Normally they either open from with the Google Mobile app, or open within the s60 browser (shown as "Web" in the applications folder)

  • Firefox wont load

    displays missing profile or inaccessable,i have spent hours trying to correct this without success, any help greatly appreciated,thanks Terry

  • Can Firefox 6 be configured to remember more than 5 prior pages for each tab so that the "go back one page" feature will allow me to retrace my steps as many as 20 pages back?

    Before Firefox 5, the "go back one page" history would show 10 or more prior pages for each tab, so that I could go back quite a way in retracing my browsing steps. With Firefox 5.0.1 and 6, however, the list of prior pages seems to have been capped