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.

Similar Messages

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" ?>
- 
- <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 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 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

SOAP mapping error

Hi Everyone,
I created the following scenario SOAP> XI>IDOC.
In the mapping, some of the fields are constant and other fields are mapped from the SOAP message.
e.g.
<constant>
<constant>
<constant>
<Mapped from the SOAP message>
<Mapped from the SOAP message>
<Mapped from the SOAP message>
When, I tested the mapping in the IR,it is working fine. But when I tested the whole scenario then only the constants are mapped to the IDOC. Can any one give me an idea how to trouble shoot?
Thank you
Bhaskar

Hi,
When i checked the Tcode "SXMB_MONI", i can seen only three sections
1.) Inbound Message --->SOAP message (Whole message is available)
2.) Receiver Grouping -->SOAP message (Whole message is available)
3.) Response --> Only constants are mapped an´d sent to the receiver.
From this point, i am sure that only constants are mapped. But, when i test the same mapping in the IR it is working fine, every thing is mapping.
Just to conform this, i changed the whole structure of the mapping and tested in the IR it is working fine, where as in the whole scenario it is only mapping the consants.
Wheather i have to tick any flag to map all the contents of the SOAP message, any where?
Thank you
Bhaskar

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: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" ?>
- 
- <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

RFC Lookup mapping error in PI 7.1

Hi Experts,
I´m getting mapping error when executing interface SOAP -> WS (SAP ECC) . The message mapping call RFC Lookup to SAP ECC.
When test the message mapping in Integration Builder the interface calls communication channel by RFC Lookup and works fine.
That interface was imported from QAS environment and was working fine, but in PRD it doesn´t works.
I checked the Interface Determination and the parameter is filled correctly with communication channel. The same communication channel was used on message mapping test.
The Interface Determination in SXI_CACHE has no value assigned to parameter in PRD environment, otherwise, the same interface determination in SXI_CACHE in QAS environment there is value (CC ID).
The problem persists after Cache Refresh in SXI_CACHE and CPA Cache.
Can anyone help me ?
Thanks in advance,
Regis Ferrato
Bellow the trace of error ocurred:

Hi Regis,
Please check my reply in your other thread:
Re: RFC Lookup error cache in PI 7.1
Regards,
---Satish

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.

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

Soap response mapping error

hi
i got payload of response from webservice as below;
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <m:requestResponse xmlns:m="http://tempuri.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<result xsi:type="xsd:string">20060911tt11</result>
</m:requestResponse>
when i test mapping with above contents in mapping test tab, i got mapping error as blow;
16:03:59 Start of test
Cannot produce target element /ns1:Rnumber_MT/rnum. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns1:Rnumber_MT/rnum. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
16:03:59 End of test
source side in MM_response, comming from wsdl for MT.
result          xsd:string
target side in MM_response, i created DT, MT.
Rnumber_MT
         |__
             rnum xsd:string
i sent data to webservice succesfully, and i can see return value as well, but mapping error.
please guide me.
thanks in advance
venjamin

hi
in response procedure;
my scenario abap proxy 2 soap sync
1. response from webserivce --> r/3
there is no DT, MT due to coming from wsdl.
only i can see result xsd:string
2. data type for r/3
   Rnumber_DT
       rnum xsd:string
   message type Rnumber_MT
   Rnumber_MT
       |_
           rnum xsd:string
3. mapping for response
   1. source (webservice)
     external message : requestResponse
     result xsd:string
   2. target (r/3)
   Rnumber_MT
       |_
           rnum xsd:string
   i did map ,,, result ---> rnum..
here is payload for response from webservice....
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <m:requestResponse xmlns:m="http://tempuri.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<result xsi:type="xsd:string">20060911tt11</result>
</m:requestResponse>
please help me
thanks in advance
venjamin

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

ABAP Mapping in RFC to SOAP Scenario

Hi Folks,
I have a scenario to send data from RFC to SOAP. I want to use the ABAP MApping for this case. Can anybody guide me how to do the ABAP Mapping for this case ? It will be real help if somebody can give a step by step guide ?
Regards,
Santosh

Hello Again,
HOW TO DO ABAP MAPPING:
Use this link and go to sec 3.1 Do exactly as mentioned in this link.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5c46ab90-0201-0010-42bd-9d0302591383
OR
1. Open http://<host>:<port>/exchangeProfile/index.html
2. Choose IntegrationBuilder -> IntegrationBuilder.Repository ->
com.sap.aii.repository.mapping.additionaltypes
3. Maintain the following entry:
R3_ABAP|Abapclass;R3_XSLT|XSL (ABAP Engine)
4. Open http://<host>:<port>/rep/support/admin/index.html
5. Choose Administration of Properties -> All Properties
6. If the value associated to parameter com.sap.aii.repository.mapping.additionaltypes is not correct, choose REFRESH at the top of the page.
How to call XI ABAP Mapping via RFC:
/people/ricardoandres.maienza/blog/2007/04/06/how-to-call-xi-abap-mapping-via-rfc
XI: ABAP mapping blogs
/people/michal.krawczyk2/blog/2006/09/20/xi-abap-mapping-logs--more-standard-better-visibility
/people/rahul.nawale2/blog/2006/11/01/dynamically-sending-a-mail-to-the-po-creator-using-xslt-abap-mapping
PART 1
/people/r.eijpe/blog/2005/11/10/xml-dom-processing-in-abap-part-i--convert-an-abap-table-into-xml-file-using-sap-dom-approach
PART 2
/people/r.eijpe/blog/2005/11/21/xml-dom-processing-in-abap-part-ii--convert-an-xml-file-into-an-abap-table-using-sap-dom-approach
PART 3
Convert an ABAP table into XML file using SAP DOM Approach
/people/r.eijpe/blog/2006/02/19/xml-dom-processing-in-abap-part-iiia150-xml-dom-within-sap-xi-abap-mapping
Testing ABAP Mapping
/people/sameer.shadab/blog/2005/09/29/testing-abap-mapping
Regards,
Madan Agrawal

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

HTTP to RFC Mapping error:com.sap.aii.utilxi.misc.api.BaseRuntimeException:

hi all,
I am doin a http to rfc scenario.In moni it is showing a mapping error in the request mapping and showing this error.In IR my mapping is working fine but in payload runtime i found the error is because it is showing <?xml version="1.0" encoding="UTF-8" ?> twice.Below is the payload message
<i><?xml version="1.0" encoding="UTF-8" ?>
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Lspm_Request_SampledueGrid_MT xmlns:ns0="http://satyam.com/xi/LSPM">
<KUNNR>100000</KUNNR>
<FROM_DATE>15.11.2006</FROM_DATE>
<TO_DATE>10.12.2006</TO_DATE>
- <EQUIPMENTID>
- <item>
<EQUIPID>wb</EQUIPID>
</item>
</EQUIPMENTID>
+ <LOCATIONID>
- <item>
<LOCID>1</LOCID>
</item>
</LOCATIONID>
- <OILID>
- <item>
<OILID>BP260</OILID>
</item>
BP260
</OILID>
</ns0:Lspm_Request_SampledueGrid_MT></i>
I tested using view source code and removing the extra ]<?xml version="1.0" encoding="UTF-8" ?> in IR and it is working fine.
Now my problem is how to rectify this error can anyone help me out please??
thanks,
Nisheeta

hi,
I tried to post the XML in the http page without the header and now it it showing a new error
Result:
<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><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: Name or password is incorrect (repeat logon)</SAP:AdditionalText></SAP:Error>
http://cgnsap27:8000/sap/xi/adapter_plain?namespace=http%3A//satyam.com/xi/LSPM&interface=Lspm_SampledueGrid_Syn_MI&service=SATYAM_LSPM_BS&party=&agency=&scheme=&QOS=BE&sap-user=shailesh&sap-password=shailesh&sap-client=100&sap-language=EN
wat does this mean??
nisheeta

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.

RFC to SOAP - Mapping Error

Similar Messages

Maybe you are looking for