XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault

Hi Experts,
I am trying to create a scenario SOAP to SOAP through AAE. There is no mapping involved.
Sender is a 3rd Party application and receiver is SAP BusinessObjects [BI].
Following error is coming when posting the message from SOAPUI or through integration engine.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: String index out of range: 0
I have done following workaround.
1) I tried the message flow through AAE, but same error in the channel
2) I checked creating a one to one mapping with soap fault message. Still the same error.
3)  "XMBWS.NoSOAPIgnoreStatusCode = true" in module tab -> Module configuration
When I tried this mentioned option, the message is passing through the channel but the passing blank empty payload.
I have checked following links.
http://forums.sdn.sap.com/thread.jspa?threadID=156305
http://forums.sdn.sap.com/thread.jspa?threadID=2111959
http://forums.sdn.sap.com/thread.jspa?threadID=1675917&tstart=0
Any pointers on this subject will be very much helpful
Thanks
Ray..

Hello,
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: String index out of range: 0
When I tried this mentioned option, the message is passing through the channel but the passing blank empty payload.
Probably because the return is blank. If this is expected, can you just use Java Mapping to parse the blank response?
Hope this helps,
Mark

Similar Messages

  • Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

    Hi All,
        We have a scenario of FTP-->PI---> Webservice.  While triggering the data in the FTP, it is failing in the PI with the below error
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
    Can you please help?

    Hi Raja- It seems to be a data quality issue.
    Check for the value @ 1447 position in the xml message that you are trying to send to web service..
    may be a date filed/decimal value which is not in expected format.

  • XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation

    Hi,
    I am doing a SOAP - PI - SOAP scenario.
    When I tested my scenario, I am getting this error in wsnavigator:
      Web service returned error. Fault code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" Fault String: "Server Error".
    When I checked in SXMB_MONI, I get this error in the response message:
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation</SAP:AdditionalText>
    I searched thru the forums but I am not finding this similar issue.
    "no such operation" issues posted here usually have an operation name after.
    I would appreciate your help.
    Thanks,
    mae

    HI
    WSDL is having some problem
    When you imported this wsdl how many messages does it show. Check weather it is having SETCOMPANYFIELDVALUE request and response. you can check the messages carried in a wsdl using the messages tab in external definition.
    Thanks

  • C4C Integration issue XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault

    Hi All,
    Scenario: ECC to C4C
    I am getting below error while pushing message to C4C using SOAP channel with Http Protocol.
    SOAP channel has been configured with SSL Authentication.
    Regards,
    Mani

    Hi Manikandan,
    Use TCPGW tool to see the response from C4C, it is very useful for trouble shooting this kind of errors.
    Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
    Regards,
    Praveen.

  • ADAPTER.SOAP_EXCEPTION : soap fault: No such operation

    Hi Experts,
    I have done File to Webservice scenario. When I am trying to execute the scenario I am getting the following error.
    <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="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: No such operation 'InventoryRequest'</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    My receiver SOAP adapter is showing inactive in communication channel monitoring. But I check one of the forum people are saying it is showing like that only until we execute the scenario. Is it correct.
    I have checked the webservice for "InventoryRequest" soapAction but in my webservice all soapActions are just empty.As follows
    <operation name="InventoryStatus">
    <wsdlsoap:operation soapAction="" />
    <input name="InventoryRequest">
    Is it problem with weservice or my configuration. Please suggest me
    Regards
    Sowmya

    Hi
    In configurator if I check the "Do Not Use Soap Envelope" I am gettin "Internal Error 500"
    If i dont check that check box I am getting the following error
    soap fault: No such operation 'InventoryRequest'
    But I didn't specify anything in soapAction.
    Could you please tell me how to resolve this issue
    I have chec the url from browser it is wroking..
    Thanks & Regards
    Sowmya

  • Receiver SOAP Adapter Problem-soap fault: Server did not recognize the valu

    I have a scenario for service orders using async call : IDOC-XI-SOAP.
    I used the XML Spy tool to test the Service order's web services and it works fine. I imported the same WSDL file in XI. When I send a SOAP message from XI, I get a following error in the adapter engine.
    <i>MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: AddUpdateCostObjectLevel1.</i>
    Can someone please help me...
    Thanks in advance!
    Mrudula

    This problem is resolved by me by passing the "http://company's URL/AddUpdateCostObjectLevel1" in the SOAP action.
    Thanks to all for your input.
    Mrudula

  • PARSING ADAPTER.SOAP_EXCEPTION

    Hi,
    I am Integrating Sap(RFC) with Webservice(Soap) using XI.
    I uploaded the FM and Wsdl file.
    For Wsdl I created Message Interface having Inbound Asychronous.
    I have done mapping,Interface mapping and Activated.
    For ID Part I am Using Two Business System , 1 for Sender and 1 for Receiver.
    I created Sender Communication channel and Receiver communication Channel,
    SenderAgreement,Receiver Determination,Interface Determination,Receiver Agreement.
    Then Activated.
    I Executed the Scenario It is throwing Error in RWB as
    PARSING>>>>>>>ADAPTER.SOAP_EXCEPTION .
    Wat it means.
    I am Going The Scenario for Webservice Receiver for the First Time.
    Points will be awarded for the answer.

    Hi
    Look into this Blog
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    Also these threads might help u
    SOAP Adapter Exception
    SOAP Adapter Exception
    SOAP adapter exception
    SOAP receiver exception problem
    Issue with SOAP Adapter calling a Web Service
    error in connecting to sender soap adapter
    http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
    **********Reward points if usefullll***********

  • Error "soap fault: No operation available for request" in proxy to soap Scenario

    Hi Experts,
    Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
      Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
    Thank you very much if any one provided the solution
    Regards,
    Yugandhar 

    Hi Yugandhar,
    Check the below thread,
    Connecting from SAP PI To Salesforce
    Regards
    RK N.

  • Handling Soap Fault Response.

    Hi All,
    I have a Proxy to SOAP scenario. 
    While testing from SoapUI --
    I am getting response for the valid input and for the invalid input the response is below.
    In the scenario through SAP PI , the valid input given from the HTTP client is getting a valid response and the scenario is running fine.
    But while checking the negative test, giving the invalid input, it is ending in a System error in PI.
    We have to handle this and send the error back to the source system.
    FAULT RESPONSE IN SoapUI :
    <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>
          <soap:Fault>
             <faultcode>soap:Client</faultcode>
             <faultstring>System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (6, 45). ---> System.InvalidOperationException: Instance validation error: 'AD' is not a valid value for Currency.
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
       at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
       at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       --- End of inner exception stack trace ---
       at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
       --- End of inner exception stack trace ---
       at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
       at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring>
             <detail/>
          </soap:Fault>
       </soap:Body>
    </soap:Envelope>
    *System error message in SAP PI* :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Inbound Message --> <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code area="MESSAGE">GENERAL</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server was unable to read request. ---&gt; System.InvalidOperationException: There is an error in XML document (1, 328). ---&gt; System.InvalidOperationException: Instance validation error: 'US' is not a valid value for Currency.
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
       at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
       at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       --- End of inner exception stack trace ---
       at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
       --- End of inner exception stack trace ---
       at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
       at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</SAP:AdditionalText><SAP:Stack/><SAP:Retry>M</SAP:Retry></SAP:Error>
    I want to capture the text in Fault string in the Fault response and send it back to the Source system.
    I have referred many blogs but i am unable to do it.
    Will java mapping work as this is a response from the Target Webservice and NOT an errorin PI.

    Hello.
    If your scenario is ECC -> Proxy -> PI -> SOAP -> WS -> SOAP -> PI -> Proxy -> ECC.
    In ESR create a Fault Message Type, and added to your Service Interface (Outboun/Inbound), use a XSLT mapping to take anyway format response, rebuid your proxy ABAP and see your "message fault" on exception tab.
    this works for me.
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema">
         <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
         <xsl:template match="/">
              <ns0:FMT_ResponseAuth>                              
                        <standard>
                             <faultText>
                                  <xsl:value-of select="//detail"/>
                             </faultText>                         
                        </standard>
              </ns0:FMT_ResponseAuth>
         </xsl:template>
    I hope this help you.
    Edited by: KrlosRios on Nov 2, 2011 5:59 PM

  • How to catch a SOAP fault

    Hi All,
    I have a ISU to web service, PROXY to SOAP sync interface. I am getting following as response.
    How can I get this into Fault message mapping?
    I have followed these blogs:
    Fault Message Types - A Demo (Part 1)
    Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Validation constraint violation: data type mismatch in element 'extraOverhead'</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks,
    Aravind

    Hi,
    Can you please elaborate exactly what you are trying to achieve.....are you trying to display this error message to the user of client proxy...If so, You can catch the exceptions in client proxy using the two standard exception classes.
    CATCH cx_ai_system_fault .
    CATCH cx_ai_application_fault .
    and in the catch block you can receive the error message and display it. The code will look like this
      DATA :  sys_fault TYPE REF TO cx_ai_system_fault,
                 text      TYPE string.
      CREATE OBJECT sys_fault.
      CALL METHOD sys_fault->get_text
        RECEIVING
          result = text.
      WRITE  : /10 'System Fault ', 30 text.
    Regards,
    Priyanka

  • Mapping SOAP Fault during synchronous SOAP call

    We are building a mediated service scenario where PI is brokering a synchronous SOAP call, without changing any of the information being sent or received (the mappings use the same source and target data types with no transformations).  When the service is successfully executed everything works as expected, but when the target service returns a SOAP fault, PI appears to be wrapping the fault in a separate fault before returning it to the client.  Why is this happening?  Is there a way to simply return the SOAP fault to the client without adding the additional wrapper?
    Here is the fault received from the target service when called directly:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Header/>
       <soapenv:Body>
          <soapenv:Fault>
             <faultcode>Missing_Required_Data</faultcode>
             <faultstring>**Required data is invalid : Dealer Country**</faultstring>
          </soapenv:Fault>
       </soapenv:Body>
    </soapenv:Envelope>
    Here is the fault received from the mediated PI service call:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: **Required data is invalid : Dealer Country**
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)
         at sun.reflect.GeneratedMethodAccessor948.invoke(Unknown Source)
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    Why aren't they the same?

    are diferents coz the first is a fault message and the second is a exception message.
    to send back the fault message define a fault message for both structure and map them in a new message mapping. later in the operation mapping or interface mapping  (depends of the pi version) under fault message or fault mappinng (i dont remember) tab assisg the fault message mapping.
    thats all you need.

  • Error message : soap fault: java.lang.NumberFormatException

    Hello,
    I have Idoc to SOAP scenario. We I send Idoc, I get following error,
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.NumberFormatException Message being parsed:
    To be on safer side, I have populated all the fields with values. I have tested the same scenarion using SOAP UI tool with payload from XI & it works fine.
    This is very annoying. Can anybody help?
    Regards,
    Sunil

    Prateek,
    Here is my xml which goes to web service via SOAp adopter,
       470 {/ns0:company_code} 
       Constant {/ns0:userid} 
       Constant {/ns0:password} 
       1 {/ns0:acklm} 
       20090821 {/ns0:badat} 
       1020104878 {/ns0:banfn} 
       A {/ns0:banst} 
       NB {/ns0:bsart} 
       20090821 {/ns0:erdat} 
       Constant {/ns0:temp1} 
       Constant {/ns0:temp2} 
       Constant {/ns0:temp3} 
       Sunil.Joyous com {/ns0:email} 
       146474 {/ns0:ernam} 
       Sunil Joyous {/ns0:name} 
       {/ns0:zossatb}
       TEST OSAT {/ns0:afnam} 
       1 {/ns0:anln1} 
       1 {/ns0:anln2} 
       1 {/ns0:aufnr} 
       1020104878 {/ns0:banfn} 
       1 {/ns0:bednr} 
       00010 {/ns0:bnfpo} 
       NB {/ns0:bsart} 
       1.000 {/ns0:bsmng} 
       1.000 {/ns0:bumng} 
       1 {/ns0:catalog_info} 
       1 {/ns0:ebakz} 
       T02 {/ns0:ekgrp} 
       IZ {/ns0:ekorg} 
       IZ {/ns0:gsber} 
       5300642603 {/ns0:infnr} 
       1 {/ns0:knttp} 
       1 {/ns0:kostl} 
       20090812 {/ns0:lfdat} 
       1 {/ns0:lifnr} 
       X {/ns0:loekz} 
       BOX CARDBOARD TELESCOPIC PART {/ns0:maktx} 
       00441010 {/ns0:matkl} 
       000000000002647430 {/ns0:matnr} 
       ST {/ns0:meins} 
       10.000 {/ns0:menge} 
       1 {/ns0:mfrpn} 
       1 {/ns0:peinh} 
       10.000 {/ns0:preis} 
       0 {/ns0:pstyp} 
       X {/ns0:repos} 
       1 {/ns0:saknr} 
       1 {/ns0:statu} 
       470 {/ns0:temp1} 
       PACKING {/ns0:temp2} 
       20090821 {/ns0:temp3} 
       BOX CARDBOARD TELESCOPIC PART {/ns0:txt01} 
       TRY {/ns0:waers} 
       1 {/ns0:wempf} 
       X {/ns0:wepos} 
       IZ {/ns0:werks} 
       1 {/ns0:zdegsta} 
       TEST TEST {/ns0:zsastxt} 
       F442617301 ,4085212101 ,JL/QSC-70108949 ,OUT ,7064 58 049 , , , , , , , , , , {/ns0:ztanim} 
       {/ns0:zossatd}
       1020104878 {/ns0:banfn} 
       00010 {/ns0:bnfpo} 
       NB {/ns0:bsart} 
       470 {/ns0:temp1} 
       Constant {/ns0:temp2} 
       Constant {/ns0:temp3} 
       PO TEXT {/ns0:zmetin1} 
       1 {/ns0:zmetin10} 
       1 {/ns0:zmetin2} 
       1 {/ns0:zmetin3} 
       1 {/ns0:zmetin4} 
       1 {/ns0:zmetin5} 
       Constant {/ns0:zmetin6} 
       Constant {/ns0:zmetin7} 
       Constant {/ns0:zmetin8} 
       Constant {/ns0:zmetin9} 
       {/ns0:zossatt}
    Out of these following fields are of decimal type,
    BSMNG, BUMNG, MENGE, PEINH, PREIS
    Rest all are of string type.
    Edited by: Sunil Joyous on Aug 21, 2009 2:01 PM
    Edited by: Sunil Joyous on Aug 21, 2009 2:02 PM
    Edited by: Sunil Joyous on Aug 21, 2009 2:02 PM

  • Receiver soap : Error ADAPTER.SOAP_EXCEPTION

    Hi all,
    My Scenario is IDOC -> XI -> WEBSERVICE using BPM & SOAP adaptor.
    when i send idoc from R/3 it is going Xi
    From Xi to web service using WSDL Request message .it is not reach to web service(connection is ok but wsdl request massage is not going properly) .
    sxmb-moni   :error is
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <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="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    <SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText> : this service is not related to my service (It is showing wrong service name)
    Pleas tell me where error is happened

    this service is not related to my service (It is showing wrong service name)
    This is the reason, you somehow call the wrong web service. But are you talking about BI or XI here?
    Best regards
    Dirk

  • ADAPTER.SOAP_EXCEPTION Error while posting data on webservice.

    Hi.
    I have IDOC-> SOAP -> IDOC Synchronous Scenario.
    I have uploaded WSDL of the webservice for mapping.
    Data is not posting on Webservice.
    it is giving me Following error.
    - <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="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    When i checked Call Adapter Outboundbinding..
    <SAP:OutboundBindingAttributes>
    - <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Attribute>
      <SAP:Name>verifyWsuTimestampMessageAge_SecurityProfileWSSEVerifyEncryptionBodyThenSignatureBodyResponse</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applyEncryptionKeyStore</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applyEncryptionKeyStoreAlias_SecurityProfileWSSEApplyEncryptionBody</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>WSSEProfileApply</SAP:Name>
      <SAP:Value>SecurityProfileWSSEApplySignatureBody</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applyEncryptionEncryptionSignatureAlias</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    I found this entry..
    Is there any problem in outbound binding.
    Kindly guide me for same.
    Regards,
    Siya

    Thanks Stefan.
    Yes, sender agreement is there and it is also there in CPA Cache.
    CPAObject: (Binding) keys: ObjectId=02cb8f5717cc35e582f072b26138a0f8 values: Direction=I
    ActionNamespace=http://test.com/xi/POC ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=os_test AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=b38bcd00e47111d7afacde420a1145a5 FromService=temp AdapterType=SOAP MappingId=null Attributes=<?xml version="1.0" encoding ...
    http://sapxis:50000/XIAxisAdapter/MessageServlet page also shows the status OK for required components and Warning for optional components.
    Am I missing something?
    Thanks,
    Beena.

  • ADAPTER.SOAP_EXCEPTION

    Hi,
    i got the following error when calling webservice. i've experienced webservice in using XI, but i do not know this situation.  please help me!!
    receiver soap adapter i've set as below;
    connection parameter : http://60.7.103.210:8011/RuleInvokerEJBwar/RuleInvokerWS
    soap action  : executeRulesFI01
    ===========================================================
    <?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="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>soap fault: Unable to find a matching Operation for this remote invocation <ns1:ruleInvokerVOFI01s xmlns:ns1="http://www.cc.com/RuleInvokerWS/javaclass"> <ns2:RuleInvokerVOFI01 xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> <ns2:approvalService xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:approvalService> <ns2:budgetExceedYn xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">N</ns2:budgetExceedYn> <ns2:categoryCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">E3</ns2:categoryCode> <ns2:categoryDetailCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">01</ns2:categoryDetailCode> <ns2:deptAttrCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:deptAttrCode> <ns2:deptPjtAttrCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">02</ns2:deptPjtAttrCode> <ns2:deptPjtCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:deptPjtCode> <ns2:pjtAttrCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo"> </ns2:pjtAttrCode> <ns2:pmEmpNo xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">00000000</ns2:pmEmpNo> <ns2:reporterEmpNo xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">51</ns2:reporterEmpNo> <ns2:reporterJikgubCode xmlns:ns2="java:com.sds.approval.biz.invoker.ejb.vo">A</ns2:reporterJikgubCode> </ns2:RuleInvokerVOFI01> </ns1:ruleInvokerVOFI01s>. Please check your operation name.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    wsdl  information..
    =========================================================
      <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions xmlns:tns="http://www.cc.com/RuleInvokerWS/javaclass" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.cc.com/RuleInvokerWS/javaclass">
    - <types xmlns:tns="http://www.cc.com/RuleInvokerWS/javaclass" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/">
    - <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:com.sds.approval.biz.invoker.ejb.vo" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:com.sds.approval.biz.invoker.ejb.vo">
    - <xsd:complexType name="ArrayOfRuleInvokerVOCO01">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOCO01" name="RuleInvokerVOCO01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOFI01">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOFI01" name="RuleInvokerVOFI01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOFI02">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOFI02" name="RuleInvokerVOFI02" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOITO01">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOITO01" name="RuleInvokerVOITO01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOMM01">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOMM01" name="RuleInvokerVOMM01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOMM02">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOMM02" name="RuleInvokerVOMM02" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOPS01">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOPS01" name="RuleInvokerVOPS01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOPS02">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOPS02" name="RuleInvokerVOPS02" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfRuleInvokerVOSD01">
    - <xsd:sequence>
      <xsd:element type="stns:RuleInvokerVOSD01" name="RuleInvokerVOSD01" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOCO01">
    + <xsd:sequence>
      <xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="assignAccountYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="budgetExceedYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="budgetUseCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="execPreBsneStepAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOFI01">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="budgetExceedYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryDetailCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reporterJikgubCode" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOFI02">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="costItemCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="execPreBsneStepAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="forwardYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="monthAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="standardDeptYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="unusualDeptYn" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOITO01">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryDetailCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="clientDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOMM01">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="assoOrgYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="inoutYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="purchaseDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="requestEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOMM02">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="amt" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="purchaseDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reposterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="requestCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="requestEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOPS01">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="architManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="architcentBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="bsnePrsntEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="ctrlExceedAmt" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="execBndPrftRate" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="execPmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="matrExceedAmt" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="notCtrlExceedAmt" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="orderBndPrftRate" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="orderDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="orderModProgressYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pdctManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pdctinndivBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="postPmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="saleDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="serviceLineCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="vrbYn" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOPS02">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="budget" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="budgetExceedYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="costDeptAttrYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="costDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="execDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="ipjtAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="mgrPlanLinkYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="owrspDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="vaCodeYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="vfCodeYn" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RuleInvokerVOSD01">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="afterActivityEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="approvalService" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="architManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="architcentBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="bsneAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="bsneDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="bsnePrsntEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="categoryCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="clientInoutAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="deptPjtCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="gukpanExportAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="manRequestAttrCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="newSjtYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pdctManInvestYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="pdctinndivBelongDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="proposalPmEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="reporterEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="saleDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="serviceLineCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="vrbYn" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
      </xsd:schema>
    - <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:com.sds.approval.biz.dao" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:com.sds.approval.biz.dao">
    - <xsd:complexType name="ApprovalUserInfo">
    - <xsd:sequence>
      <xsd:element type="xsd:string" name="apprEmpDeptCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpDeptName" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpEmailAddr" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpHname" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpJikchakCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpJikchakName" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpJikwiCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpJikwiName" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprEmpResNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprItemTypeCode" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprItemTypeName" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprOrgEmpNo" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprRepYn" minOccurs="1" nillable="true" maxOccurs="1" />
      <xsd:element type="xsd:int" name="apprSeq" minOccurs="1" maxOccurs="1" />
      <xsd:element type="xsd:string" name="apprService" minOccurs="1" nillable="true" maxOccurs="1" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ArrayOfApprovalUserInfo">
    - <xsd:sequence>
      <xsd:element type="stns:ApprovalUserInfo" name="ApprovalUserInfo" minOccurs="0" nillable="true" maxOccurs="unbounded" />
      </xsd:sequence>
      </xsd:complexType>
      </xsd:schema>
      </types>
    - <message name="executeRulesCO01">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOCO01" name="ruleInvokerVOCO01s" />
      </message>
    - <message name="executeRulesCO01Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesFI01">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOFI01" name="ruleInvokerVOFI01s" />
      </message>
    - <message name="executeRulesFI01Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesFI02">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOFI02" name="ruleInvokerVOFI02s" />
      </message>
    - <message name="executeRulesFI02Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesITO01">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOITO01" name="ruleInvokerVOITO01s" />
      </message>
    - <message name="executeRulesITO01Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesMM01">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOMM01" name="ruleInvokerVOMM01s" />
      </message>
    - <message name="executeRulesMM01Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesMM02">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOMM02" name="ruleInvokerVOMM02s" />
      </message>
    - <message name="executeRulesMM02Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesPS01">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOPS01" name="ruleInvokerVOPS01s" />
      </message>
    - <message name="executeRulesPS01Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesPS02">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOPS02" name="ruleInvokerVOPS02s" />
      </message>
    - <message name="executeRulesPS02Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <message name="executeRulesSD01">
      <part xmlns:partns="java:com.sds.approval.biz.invoker.ejb.vo" type="partns:ArrayOfRuleInvokerVOSD01" name="ruleInvokerVOSD01s" />
      </message>
    - <message name="executeRulesSD01Response">
      <part xmlns:partns="java:com.sds.approval.biz.dao" type="partns:ArrayOfApprovalUserInfo" name="result" />
      </message>
    - <portType name="RuleInvokerWSPort">
    - <operation name="executeRulesCO01">
      <input message="tns:executeRulesCO01" />
      <output message="tns:executeRulesCO01Response" />
      </operation>
    - <operation name="executeRulesFI01">
      <input message="tns:executeRulesFI01" />
      <output message="tns:executeRulesFI01Response" />
      </operation>
    - <operation name="executeRulesFI02">
      <input message="tns:executeRulesFI02" />
      <output message="tns:executeRulesFI02Response" />
      </operation>
    - <operation name="executeRulesITO01">
      <input message="tns:executeRulesITO01" />
      <output message="tns:executeRulesITO01Response" />
      </operation>
    - <operation name="executeRulesMM01">
      <input message="tns:executeRulesMM01" />
      <output message="tns:executeRulesMM01Response" />
      </operation>
    - <operation name="executeRulesMM02">
      <input message="tns:executeRulesMM02" />
      <output message="tns:executeRulesMM02Response" />
      </operation>
    - <operation name="executeRulesPS01">
      <input message="tns:executeRulesPS01" />
      <output message="tns:executeRulesPS01Response" />
      </operation>
    - <operation name="executeRulesPS02">
      <input message="tns:executeRulesPS02" />
      <output message="tns:executeRulesPS02Response" />
      </operation>
    - <operation name="executeRulesSD01">
      <input message="tns:executeRulesSD01" />
      <output message="tns:executeRulesSD01Response" />
      </operation>
      </portType>
    - <binding type="tns:RuleInvokerWSPort" name="RuleInvokerWSPort">
      <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="executeRulesCO01">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesFI01">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesFI02">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesITO01">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesMM01">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesMM02">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesPS01">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesPS02">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
    - <operation name="executeRulesSD01">
      <soap:operation style="rpc" soapAction="" />
    - <input>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </input>
    - <output>
      <soap:body namespace="http://www.cc.com/RuleInvokerWS/javaclass" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />
      </output>
      </operation>
      </binding>
    - <service name="RuleInvokerWS">
    - <port name="RuleInvokerWSPort" binding="tns:RuleInvokerWSPort">
      <soap:address location="http://60.7.103.210:8011/RuleInvokerEJBwar/RuleInvokerWS" />
      </port>
      </service>
      </definitions>

    Hi Ogawa,
    First of all check the  URL in your receiver SOAP adapter. The error comes from the web service server. It says that the request message is wrong.
    U have to fill field SOAPAction in the receiver soap adapter
    U may find the related information here
    http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
    Please check this
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    There are multiple soap actions listed there.
    Regards,
    Prateek

Maybe you are looking for

  • ODBC 8.1.7 Error when calling a stored procedure that owned by an other user

    I am testing my application VB for certified to use the Client 8 with ODBC Driver 8.1.7.0 , because today this application have been working with Client 7 and ODBC driver 7.3 version 2.5. But i have some surprises: Set qy = con.CreateQuery("", "{CALL

  • New iMac, have several questions

    Community, First of all I'm not sure if this is the right community to post to. My questions seem to span several forum categories. If there is a better general forum for my questions, please let me know. I just got a new iMac, (21.5 inch late 2013),

  • Comments in OLAP Query

    I have tried unsuccessfully to use the traditional comment indicators (--, // or /../) in the MII OLAP Query Template.  Can any one offer any insight ?  We are running xMII 11.5 Thanks Edited by: Gary Wilson on Mar 18, 2010 4:17 PM

  • Published website but still having a problem-HELP?

    Hello all- I just got done publishing my site to .Mac and yes I am using a domain I purchased. When I go to visit my site on the web all of the hyperlinks are connected to their corresponding pages correctly and my domain name is still in the URL, ex

  • Simulating Acccounting Document before billing is created ( VF01 )

    Hi All,   We are on ECC6.00 . As it is a standard feature that SD billing is created and then the billing details are submitted to create accounting document .  If the system fails to create the the FI document, the billing docuemt still exists in th