Skip to Content
avatar image
Former Member

Error in Receiver SOAP adapter - but ok in sxmb_moni

HI,

i am trying to call a Web Services which takes only input. so it is a asynchronous call.

I configured SAP R/3(IDOC)-XI-WS.

My sxmb_moni is ok in XI. But when i check Adapter monitoring it is throwing the following error... any help please..

**********************************************************************************************************************************************

2008-02-21 11:13:05 Success Message successfully received by messaging system. Profile: XI URL: http://EMHBSSAP05.bekaertcorp.local:56600/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

2008-02-21 11:13:05 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2008-02-21 11:13:05 Success Message successfully put into the queue.

2008-02-21 11:13:05 Success The message was successfully retrieved from the receive queue.

2008-02-21 11:13:05 Success The message status set to DLNG.

2008-02-21 11:13:05 Success Delivering to channel: ZCC_Material_SOAP

2008-02-21 11:13:05 Success MP: Entering module processor

2008-02-21 11:13:05 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

2008-02-21 11:13:06 Success SOAP: request message entering the adapter with user J2EE_GUEST

2008-02-21 11:13:06 Error 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: No task found for action "parts", object type "ext.bekaert.SAP", and object identifer "@beingapp02-vm01.bekaertcorp.local".

2008-02-21 11:13:06 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No task found for action "parts", object type "ext.bekaert.SAP", and object identifer "@beingapp02-vm01.bekaertcorp.local".

2008-02-21 11:13:06 Success SOAP: completed the processing

2008-02-21 11:13:06 Success SOAP: continuing to response message 983cc370-e065-11dc-975c-001a4b0658c1

2008-02-21 11:13:06 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No task found for action "parts", object type "ext.bekaert.SAP", and object identifer "@beingapp02-vm01.bekaertcorp.local".

2008-02-21 11:13:06 Success SOAP: sending a delivery error ack ...

2008-02-21 11:13:06 Success SOAP: sent a delivery error ack

2008-02-21 11:13:06 Success Acknowledgement creation triggered for type: SystemErrorAck

2008-02-21 11:13:06 Success Acknowledgement creation triggered for type: AckNotSupported

2008-02-21 11:13:06 Success Acknowledgement sent successfully for type: AckNotSupported

2008-02-21 11:13:06 Success Acknowledgement sent successfully for type: SystemErrorAck

************************************************************************************************************************************************

Can anybody help on this. This is urgent. Correct solution will be awarded.

I have done the : http://xihost:port/wsnavigator

It is showing the successful conncetivity.

Can anybody help me to find out the solution to the problem

Thanks & Regards

Prabhat

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Feb 21, 2008 at 10:54 AM

    Hi,

    From my point of view the Web Service is not able to parse the information you provide.

    From the Audit log, i think there is an Operation called "PARTS" in the Web service,

    It requires an Object type and Object key. Somehow the values passed by you are validated at the web service, it does not find its value and throws an exception.

    Hence no issue with communication, here but with data. Check your data and send the message again.

    Reward points if useful

    Regards

    Abhishek

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      Because you have one IDOC - XI -SOAP scenario, you will not get error back to SXMB_MONI. IDOC is async and if the message successfully transfered from ABAP to J2EE stack, the message will be marked as FINAL (Success) in ABAP.

      The technical connection between SOAP Adapter and the WebService seems to work as well. What you get is one SOAP Fault. It seems the SOAP request message does not work on the Server side. You could download the XI message payload and send it with external SOAP Test tool like SOAP UI to test whether it works or not. Apart from that, you should also consider you scenario new, since IDOC is asycn and the WebService you try to invoke seems to be a req/rep (Sync), what would you do with the response and how does exception handeling looks like ? However you could use Asych/Sync ability within XI to cover this issue.

      regards,

      Hai

  • avatar image
    Former Member
    Feb 21, 2008 at 08:58 PM

    Hi ,

    Any suggestion on my problem. correct solution will be rewarded with full points.

    It's an urgent one.

    Thanks & Regards

    Prabhat

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 21, 2008 at 09:28 PM

    HI Ranjan,

    Is it solved?

    regards,

    sukarna

    Add comment
    10|10000 characters needed characters exceeded

    • GUys Got the answer,

      above was happening to us because - we imported the WSDL provided by them as Category: wsdl and Messages "From All Available Message Definition"

      but when we changed to Messages to "Using RPC Style" in External definition (IR). the problem got solved.

      and in Receiver SOAP channel, check "Use Encoded Headers".

      Please note we are using PI 7.31 sp4

      thanks.