Error in Receiver SOAP adapter - but ok in sxmb_moni

[Former Member]

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

[Former Member]

HI Ranjan,

Is it solved?

regards,

sukarna

[Former Member]

Hi,

Nops it's not solved and thats why replying back to the answers suggested.

Do u have any solution to my problem. Your help will be appreciated.

Thanks & Regards

Prabhat

[Former Member]

Hi Ranjan,

can you tell me what that "parts" u r using?

regards,

sukarna

[Senthilprakash1]

Hi Guys,

I am replying to this thread as we are also facing the same issue with windchill integration with SAP PI.

we have narrowed down on the problem.

the problem is with the SOAP action which is generated.

if you look proper the SOAP ACTION contains "!" exclamation without quotes, which is not understood by PI and does not point to the complete soap action.

so if windchill can provide the soap action with out ! in it. then the server will be able to connect to the method without any issues.

BUT question all, what else option we have to make the SOAP action with ! to be processed proper in SAP PI without asking the business client to regenerate the WSDL with SOAP ACTION which does not contain ! exclamation in it?

suggestions would be greatly appreciated.

[Senthilprakash1]

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.

[Former Member]

Hi ,

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

It's an urgent one.

Thanks & Regards

Prabhat

[Former Member]

first call the same webservice using some external tool like xml spy or eclipse wtp

Later verify if the content of the request is according to webservice definition. Decimal places and length of fields.

/wg

[Former Member]

Hi ,

I called the webservices using wsnavigator and connectivity was ok but every time in adapter monitoring I get the error message that " task not found for action ******** which is not clear to me as why exactly it is happening.

can u suggest some solution to my problem.

regards

prabhat

[Former Member]

It looks like typo in integration directory. Please double check it maybe ask your colleague to do that. It might be an operation or something like that.

/wg

[Former Member]

Hi,

Could u please elaborate and specify the exact problem.

your help will be appreciated.

Thanks & Regards

Prabhat

[Former Member]

plese verify your settings in integration directory communication channel settings. You might have made a small mistake. That's the most frequent problem for webservices and XI.

/wg

[Former Member]

Hi,

As I have shared the adapter monitoring messsage status details can you please specify accurately as what exatcly i have missed out in my SOAP receiver adapter as i have already specified the URL and soap action.

regards

prabhat

[Former Member]

before that please tell me if you have verified the setting in integration directory letter by letter. Especially name of action also take into account size of letters.

Wg

[Former Member]

Hi,

Yes I have used the same one which is there in .wsdl file.

Thanks & Regards

Prabhat

[Former Member]

was the information posted in target system?

/wg

[Former Member]

Hi,

Conncetivity was successful but the information is not reaching to the webservices and if ypu check my adapter monitor message details it shows " task not found for action********' so i am not getting the root cause of the problem and therefore not able to resolve it.

therefore i seek a solution to this problem.

thanks & regards

prabhat

[Former Member]

Hi Ranjan,

if my understanding is correct,

you are trying to tringger a custom defined actoin in the webservice.

custom defined actions can't be triggered directly by XI adapter. i faced this problem some time ago, i didn't get answer for this.

i heard that we have to use java mapping at adapter level to trigger action.

Regards,

sukarna.

[Former Member]

Hi,

I am trigerring IDOC from SAP and I need to send it to Webservices.

idoc is MATMAS05.

CAN U SUGGEST SOME SOLUTION TO MY SPECIFIC PROBELM.

Regards

Prabhat

[Former Member]

Hi Ranjan,

get the WSDL from the Webservice, import it,

import the idoc

and map it.

configure the receiver HTTP adapter....

determination-------

-

---

did the action "parts" came from the WSDL which you imported?

Regards,

sukarna

[Former Member]

Hi Ranjan,

send this error to the team which is taking care of your webservices... i think they can solve this.

regards,

sukarna.

[Former Member]

how about 'default soap action'?

/wg

[Former Member]

Hi,

Can anybody provide the concrete solution to my problem?

Thanks & Regards

Prabhat

[Former Member]

Hi All,

any soultion you have got to my problem.the adapter message monitoring is showing the message as shown below:

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

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

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

2008-02-22 13:36:33 Success Message successfully put into the queue.

2008-02-22 13:36:33 Success The message was successfully retrieved from the receive queue.

2008-02-22 13:36:33 Success The message status set to DLNG.

2008-02-22 13:36:33 Success Delivering to channel: ZCC_Material_SOAP

2008-02-22 13:36:33 Success MP: Entering module processor

2008-02-22 13:36:33 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

2008-02-22 13:36:33 Success SOAP: request message entering the adapter with user J2EE_GUEST

2008-02-22 13:36:33 Success SOAP: completed the processing

2008-02-22 13:36:33 Success SOAP: continuing to response message ccc3d6f0-e142-11dc-ac9f-001a4b0658c1

2008-02-22 13:36:33 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-22 13:36:33 Success SOAP: sending a delivery error ack ...

2008-02-22 13:36:33 Success SOAP: sent a delivery error ack

2008-02-22 13:36:33 Success Acknowledgement creation triggered for type: SystemErrorAck

2008-02-22 13:36:33 Success Acknowledgement creation triggered for type: AckNotSupported

2008-02-22 13:36:33 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-22 13:36:33 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-22 13:36:33 Success Acknowledgement sent successfully for type: SystemErrorAck

2008-02-22 13:36:33 Success Acknowledgement sent successfully for type: AckNotSupported

2008-02-22 13:36:33 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: 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-22 13:36:33 Success The message status set to WAIT.

2008-02-22 13:36:33 Success The asynchronous message was successfully scheduled to be delivered at Fri Feb 22 13:41:33 CET 2008.

2008-02-22 13:41:33 Success The message status set to TBDL.

2008-02-22 13:41:33 Success Retrying to deliver message to the application. Retry: 1

2008-02-22 13:41:33 Success The message was successfully retrieved from the receive queue.

2008-02-22 13:41:33 Success The message status set to DLNG.

2008-02-22 13:41:33 Success Delivering to channel: ZCC_Material_SOAP

2008-02-22 13:41:33 Success MP: Entering module processor

2008-02-22 13:41:33 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

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

Thanks & Regards

Prabhat

[prateek]

Tracing with TCPGateway would be a really helpful option. We found the solution to one of our problem in same way

/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

Regards,

Prateek

[Former Member]

Hi Prateek,

connectivity was checked using wsnavigator and it was o.k.

my question is very specific that when audit log of the message shows

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

so can anybody answer why it is refering to no task found for action and what I should do to resolve the issue.

I hope I have clarified my question.

Has anybody faced this type of problem earlier.

your correct solution will be awarded.

Thanks & Regards

Prabhat

[prateek]

TCPGateway not only checks the connection but also find out wht data is expected at the receiver and and what is missing.

The case may be that the SOAP action u r triggering have no corresponding implementation at the receiver Webservice

Regards,

Prateek

[Former Member]

Hi Prateek,

it showed the error HTTP/1.0 500 Internal Server Error in tcpgateway

can you suggest what coulkd be the reason.

thanks & regards

prabhat

[Former Member]

Hi,

it showed the error HTTP/1.0 500 Internal Server Error in tcpgateway

can you suggest what coulkd be the reason.

thanks & regards

prabhat

[stefan_grube]

Hi Prabhat,

The web service reports an application error. The provided data are not correct.

There is nothing wrong with the SOAP adapter.

Check the data in the message.

Regards

Stefan

[Former Member]

Hi Stefan,

As mentioend by you is this only problem related to data or any message format also?

apart from this is there any other possibility also please let me know so that I can check it from my side.

I will check it tommorrow morning and then confirm it to you.

Thanks & Regards

Prabhat

[Former Member]

Hi ,

I checked it using the correct test data and it is still showing the same error: HTTP/1.0 500 Internal Server Error and No task found for action "parts", object type "ext.testsystem.SAP", and object identifer "@beingapp02-vm01.testsystem.local".

can anybody suggest the correct solution.

This thread has been open for a long time now and I didnt get any solution so far;

regards

prabhat

[Former Member]

Hi,

Can anybody provide the correct solution for the IDOC_SAP XI _ Webservices scenario

error: showing the same error: HTTP/1.0 500 Internal Server Error and No task found for action "parts", object type "ext.testsystem.SAP", and object identifer "@beingapp02-vm01.testsystem.local".

thanks & regrads

[henrique_pinto]

> This thread has been open for a long time now and I didnt get any solution so far;

This is not SAP standard support.

This is a place for dicussing and sharing experiences between fellow colleagues.

If you want an SLA from your software provider, open an OSS message.

Regards,

Henrique.

[Former Member]

Hi,

My point is that this forum is considered to be full of XI expert and somebody might have encountered the problem of the same category therefore if any help can be provided it will be of great help.

I hope you may understand this and also to make you clear my intention is not to put any SLA but since the problem is critical and aslo generic so there is no harm in asking SAP XI expert to reply on it fastly;

Have u ever faced this problem of webservices? I expect the discussion on the topics rather than discussion on these trivial issues;

if you may provide me the solution to my problem i will be greatful to you;

Thanks & Regards

Prabhat

[Former Member]

Prabhat,

have you thought about Setafn's answer?? That this is an application error? Of course there is everything ok in the sxmb_moni, because your scenario is async. So when the error occurs, it can be seen only on adapter engine.

Ok, tell me, what are these terms: PARTS, "ext.testsystem.SAP", and object identifer "@beingapp02-vm01.testsystem.local"?? Are they SOAP request data?

How did you construct your SOAP request - did u use WSDL for this?

Peter

[Former Member]

Hi Peter,

Thanks for the response.

q1; have you thought about Setafn's answer??

Answer: yest i did the test with correct test data.

q2: How did you construct your SOAP request - did u use WSDL for this?

Answer: yes I used wsdl for the IDOC _SAP XI _ SOAP Receiver scenario; wsdl is having two messages request and response but i have done the mapping with request and as per the advice of Webservices suppliers i have ignored the response.

q3: Ok, tell me, what are these terms: PARTS, "ext.testsystem.SAP", and object identifer "@beingapp02-vm01.testsystem.local"?? Are they SOAP request data?

answer: it is shwoing error that : No task found for action "parts", object type "ext.testsystem.SAP", and object identifer "@beingapp02-vm01.testsystem.local".

for your information the soap action is:

urn:ie-soap-rpc:ext.testsystem.SAP!createUpdatePart

Hope it clears your question; In case of any doubt please let me know;

waiting for your support; your help will be appreciated;

thanks & regards

prabhat

[Former Member]

Prabhat,

can you post your SOAP request?

Also, I'm not sure about the SOAP action, if the exclamation mark is allowed there. Where do you have this infromation about soap action from? Do you have it from WSDL?

Peter

[Former Member]

Prabhat, one more thing:

q1.. you could have tried with the correct data, but maybe the web service works not correctly! and it threw an excetpion. But you say, you have tried it from other web service tool, right?

Peter

[Former Member]

Hi Peter,

Thanks for your prompt response; SOAP action i got it from wsdl file;

i am pasting the wsdl file for your help: i used the "testsystem" in place of actual system name

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

<?xml version='1.0'?>

<definitions

name='IESoap'

targetNamespace='http://www.ptc.com/infoengine/soap/rpc/message/'

xmlns:wc='http://www.ptc.com/infoengine/soap/rpc/message/'

xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'

xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/'

xmlns:xsd='http://www.w3.org/2001/XMLSchema'

xmlns:stk='http://schemas.microsoft.com/soap-toolkit/wsdl-extension'

xmlns:mime='http://schemas.xmlsoap.org/wsdl/mime/'

xmlns='http://schemas.xmlsoap.org/wsdl/'>

<types>

<schema version='1.0'

xmlns='http://www.w3.org/2001/XMLSchema'

targetNamespace='http://www.ptc.com/infoengine/soap/rpc/message/'

xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>

<complexType name='ext.bekaert.integration.sapPart'>

<all>

<element minOccurs='0' name='baannumber' type='xsd:string'/>

<element minOccurs='0' name='classcode' type='xsd:string'/>

<element minOccurs='0' name='decortenumber' type='xsd:string'/>

<element minOccurs='0' name='machinetype' type='xsd:string'/>

<element minOccurs='0' name='materialgroup' type='xsd:string'/>

<element minOccurs='0' name='name' type='xsd:string'/>

<element minOccurs='0' name='number' type='xsd:string'/>

<element minOccurs='0' name='state' type='xsd:string'/>

</all>

</complexType>

<complexType name='ArrayOfext.bekaert.integration.sapPart'>

<complexContent>

<restriction base='soapenc:Array'>

<sequence>

<element name='item' minOccurs='0' maxOccurs='unbounded' type='wc:ext.bekaert.integration.sapPart'/>

</sequence>

<attribute ref='soapenc:arrayType' wsdl:arrayType='wc:ext.bekaert.integration.sapPart[]'/>

</restriction>

</complexContent>

</complexType>

<complexType name='ArrayOfstring'>

<complexContent>

<restriction base='soapenc:Array'>

<sequence>

<element name='item' minOccurs='0' maxOccurs='unbounded' type='xsd:string'/>

</sequence>

<attribute ref='soapenc:arrayType' wsdl:arrayType='xsd:string[]'/>

</restriction>

</complexContent>

</complexType>

</schema>

</types>

<message name='IEResponse'>

<part name='Collection' type='xsd:string'/> </message>

<message name='createUpdatePartRequest'>

<part name='parts' type='wc:ArrayOfext.bekaert.integration.sapPart'/>

</message>

<portType name='IEService'>

<operation name='createUpdatePart'>

<documentation>this is comment</documentation>

<input message='wc:createUpdatePartRequest'/>

<output message='wc:IEResponse'/>

</operation>

</portType>

<binding name='SoapBinding' type='wc:IEService'>

<stk:binding preferredEncoding=''/>

<soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>

<operation name='createUpdatePart'>

<soap:operation soapAction='urn:ie-soap-rpc:ext.bekaert.SAP!createUpdatePart'/>

<input>

<soap:body use='encoded' namespace='http://www.ptc.com/infoengine/soap/rpc/message/'

encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' />

</input>

<output>

<soap:body use='encoded' namespace='http://www.ptc.com/infoengine/soap/rpc/message/'

encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' />

</output>

</operation>

</binding>

<service name='IESoapServlet'>

<port name='IESoapPort' binding='wc:SoapBinding'>

<soap:address location='http://beingapp02-vm01.bekaertcorp.local/Windchill/servlet/RPC'/>

</port>

</service>

</definitions>

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

request you to please help me on this as i am getting error

thanks & regards

prabhat

[Former Member]

Hi Peter,

I pasted the ;wsdl file for your help;

regarding your query for q1: webservice is working correctly and i testing it with wsnavigator tool and also logged on to webservices also;

please help me;

thanks & regards

prabhat

[Former Member]

Ok, wsdl looks ok. Can you please post your SOAP request which you try in the wsnavigator tool? And also a soap request from XI please..

Peter

Edited by: Peter Jarunek on Feb 25, 2008 1:28 PM

[Former Member]

Hi Pter,

Thanks for the prompt reply;

the soap reuest message with wsnavigator is : and it is showing http return code 200

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

POST /Windchill/servlet/RPC HTTP/1.1

Host: beingapp02-vm01.bekaertcorp.local:80

Content-Type: text/xml; charset=UTF-8

Connection: close

Authorization: <value is hidden>

Content-Length: 1225

SOAPAction: "urn:ie-soap-rpc:ext.bekaert.SAP!createUpdatePart"

<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'><ns1:createUpdatePart xmlns:ns1='http://www.ptc.com/infoengine/soap/rpc/message/'><parts ns2:arrayType='tns:ext.bekaert.integration.sapPart[1]' xmlns:tns='http://www.ptc.com/infoengine/soap/rpc/message/' xmlns:ns2='http://schemas.xmlsoap.org/soap/encoding/'><item xsi:type='tns:ext.bekaert.integration.sapPart'><baannumber xsi:type='xs:string'></baannumber><classcode xsi:type='xs:string'></classcode><decortenumber xsi:type='xs:string'></decortenumber><machinetype xsi:type='xs:string'></machinetype><materialgroup xsi:type='xs:string'>test</materialgroup><name xsi:type='xs:string'>test1</name><number xsi:type='xs:string'>test234</number><state xsi:type='xs:string'>test</state></item></parts></ns1:createUpdatePart></SOAP-ENV:Body></SOAP-ENV:Envelope>

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

if you need any information please let me know

Thanks & Regards

Prabhat

[Former Member]

Hi Peter,

Request message from SAP XI IS AS SHOWN BELOW/

<?xml version="1.0" encoding="UTF-8"?>

<ns0:parts xmlns:ns0="http://www.ptc.com/infoengine/soap/rpc/message/"><item><materialgroup>1000480</materialgroup><name>Test Material for RF 12</name><number>000000000000210015</number><state>10</state></item></ns0:parts>

THANKS & REGARDS

PRABHAT

[Former Member]

Prabhat,

use the SAME DATA in your wsnavigator request as you use in XI

.....<item><materialgroup>1000480</materialgroup><name>Test Material for RF 12</name><number>000000000000210015</number><state>10</state></item>....

Exactly the same! Use no test123 or enything else.. use exactly there numbers for materialgrou etc.

What's the WS response?

Peter

Edited by: Peter Jarunek on Feb 25, 2008 1:53 PM

[Former Member]

Hi Peter,

The request message in wsnavigator is :

POST /Windchill/servlet/RPC HTTP/1.1

Host: beingapp02-vm01.bekaertcorp.local:80

Content-Type: text/xml; charset=UTF-8

Connection: close

Authorization: <value is hidden>

Content-Length: 1255

SOAPAction: "urn:ie-soap-rpc:ext.bekaert.SAP!createUpdatePart"

<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'><ns1:createUpdatePart xmlns:ns1='http://www.ptc.com/infoengine/soap/rpc/message/'><parts ns2:arrayType='tns:ext.bekaert.integration.sapPart[1]' xmlns:tns='http://www.ptc.com/infoengine/soap/rpc/message/' xmlns:ns2='http://schemas.xmlsoap.org/soap/encoding/'><item xsi:type='tns:ext.bekaert.integration.sapPart'><baannumber xsi:type='xs:string'></baannumber><classcode xsi:type='xs:string'></classcode><decortenumber xsi:type='xs:string'></decortenumber><machinetype xsi:type='xs:string'></machinetype><materialgroup xsi:type='xs:string'>1000480</materialgroup><name xsi:type='xs:string'>Test Material for RF 12</name><number xsi:type='xs:string'>000000000000210015</number><state xsi:type='xs:string'>10</state></item></parts></ns1:createUpdatePart></SOAP-ENV:Body></SOAP-ENV:Envelope>

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

The response messag in wsnavigator is:

HTTP/1.1 200 OK

Date: Mon, 25 Feb 2008 12:33:23 GMT

Server: Apache/2.0.59 (Win32) mod_jk/1.2.18

Content-Length: 3350

Vary: Accept-Encoding,User-Agent

Connection: close

Content-Type: text/xml;charset=utf-8

<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wc="http://www.ptc.com/infoengine/soap/rpc/message/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Header/><SOAP-ENV:Body><wc:createUpdatePartResponse><Collection xsi:type="xsd:string">

<wc:COLLECTION xmlns:wc="http://www.ptc.com/infoengine/1.0">

<wt.part.WTPart NAME="OUTPUT" TYPE="Unknown" STATUS="0">

<wc:INSTANCE>

<obid>VR:wt.part.WTPart:91741077:357415453-1158844631275-23687203-19-210-207-195@beingapp02-vm01.bekaertcorp.local</obid>

<class>wt.part.WTPart</class>

<name>test1</name>

<state.state>INWORK</state.state>

<versionInfo.identifier.versionLevel>1</versionInfo.identifier.versionLevel>

<masterReference>OR:wt.part.WTPartMaster:91741075:357415453-1158844631275-23687203-19-210-207-195@beingapp02-vm01.bekaertcorp.local</masterReference>

<oneOffVersionInfo.identifier.oneOffVersionId></oneOffVersionInfo.identifier.oneOffVersionId>

<folderingInfo.cabinet>OR:wt.folder.Cabinet:71694:357415453-1158844631275-23687203-19-210-207-195@beingapp02-vm01.bekaertcorp.local</folderingInfo.cabinet>

<lock.note></lock.note>

<iterationInfo.modifier>uid=erp,ou=people,cn=windchill_8.0,cn=application services,o=bekaertcorp:Ldap.bekaertcorp.local@Ldap.bekaertcorp.local</iterationInfo.modifier>

<ownership.owner></ownership.owner>

<partType>component</partType>

<teamId></teamId>

<lock.date></lock.date>

<thePersistInfo.createStamp>2008-02-25 13:33:24 CET</thePersistInfo.createStamp>

<iterationInfo.branchId>91,741,077</iterationInfo.branchId>

<iterationInfo.latest>true</iterationInfo.latest>

<checkoutInfo.state>c/i</checkoutInfo.state>

<versionInfo.identifier.versionId>A</versionInfo.identifier.versionId>

<domainRef>OR:wt.admin.AdministrativeDomain:71645:357415453-1158844631275-23687203-19-210-207-195@beingapp02-vm01.bekaertcorp.local</domainRef>

<lifeCycleAtGate>false</lifeCycleAtGate>

<thePersistInfo.modifyStamp>2008-02-25 13:33:24 CET</thePersistInfo.modifyStamp>

<iterationInfo.identifier.iterationId>1</iterationInfo.identifier.iterationId>

<iterationInfo.state>ctrld</iterationInfo.state>

<source>buy</source>

<view>Design</view>

<locker.id></locker.id>

<number>TEST234</number>

<iterationInfo.creator>uid=erp,ou=people,cn=windchill_8.0,cn=application services,o=bekaertcorp:Ldap.bekaertcorp.local@Ldap.bekaertcorp.local</iterationInfo.creator>

<state.lifeCycleId>OR:wt.lifecycle.LifeCycleTemplate:1684:357415453-1158844631275-23687203-19-210-207-195@beingapp02-vm01.bekaertcorp.local</state.lifeCycleId>

</wc:INSTANCE>

</wt.part.WTPart>

</wc:COLLECTION>

</Collection></wc:createUpdatePartResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

please let me know if you need any more help from my side

thanks & regards

prabhat

[Former Member]

Hi Peter,

Have you got any clue for the problem

Thanks & Regards

Prabhat

[Former Member]

Prabhat,

you used the same data, but the request is different!

What about the missing root node <ns1:createUpdatePart> in the XI's message??

How come this is not there??? Strange behaviour, cos' normally this "corrupted" message shouldn't have been understood by WS!

Do you have an explanation, why the rrot node is not in the XI request?

Peter

[Former Member]

Hi Peter,

I imported the .wsdl file as an external definition and therefore used the message tpe createupdatePartRequest from that; I didnt create any meesage type which seems to be correct because i have used the ;wsdl message type;

can you suggest what i should check and do for resolution of this problem

thanks & regards

prabhat

[Former Member]

Good news, I've found the solution

When you create the external definition, there is a combobox Messages (next to Category). Select the "Using RPC Style". This "changes" your message structures. Create again message mapping etc. Use the new message request type. It shoud work now.

Peter

[henrique_pinto]

Please note this:

http://help.sap.com/saphelp_nw70/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm

> The WSDL document in rpc-style format must also not use any

> soapenc:Array types; these are often used in SOAP code in

> documents with this format. soapenc:Array uses the tag <xsd:any>,

> which the Integration Builder editors or proxy generation either

> ignore or do not support.

The generated message may also not be fully undestood by the application.

But it's worth a try.

Regards,

Henrique.

[Former Member]

Hi Peter,

that problem related to task no found is not there now but when I triggered the messgae it showed me

SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: INSTANCE parameter missing.

could you please comment what parameter might be missing communication as I already mentioned soap URL and soap action

Thanks & Regards

Prabhat

[Former Member]

Prabhat,

go to:

http://<sap_xi_host>:<sap_xi_port>/MessagingSystem

find the latest message and click the Eye icon.. Then click button "Display message bytes"...

Post the content

Peter

[Former Member]

Henrique,

r u sure with the link?

Peter

[henrique_pinto]

Prabhat,

the instance which it talks about is the index in the namespace of parts node (tns:ext.bekaert.integration.sapPart[1] in the proper request message).

As I've commented, IR doesn't support RPC-style WSDL with soap-enc:arrays, and hence the application won't be able to understand the message XI generates.

I don't see any room for a solution here unless changing the application definition... I'm sorry.

Regards,

Henrique.

[Former Member]

Hi Peter,

follwing is the meesage details in messga monitoring in "Display message bytes"...

--SAP_DCE3B2AB48C07FF1B785001A4B061F90_END

content-id: <soap-DCE3B2AB48C07EF1B785001A4B061F90@sap.com>

Content-Type: text/xml; charset=utf-8

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:SAP='http://sap.com/xi/XI/Message/30' xmlns:wsse='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'><SAP:Main versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-main-92ABE13F5C59AB7FE10000000A1551F7'><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>asynchronous</SAP:ProcessingMode><SAP:MessageId>dce3b2ab-1f8d-6ff1-b785-001a4b061f90</SAP:MessageId><SAP:TimeSent>2008-02-25T15:02:22Z</SAP:TimeSent><SAP:Sender><SAP:Party agency='http://sap.com/xi/XI' scheme='XIParty'></SAP:Party><SAP:Service>ZBS_SAPERP_DEV</SAP:Service></SAP:Sender><SAP:Receiver><SAP:Party agency='http://sap.com/xi/XI' scheme='XIParty'></SAP:Party><SAP:Service>ZBSV_PDM010</SAP:Service></SAP:Receiver><SAP:Interface namespace='urn://bekaert.com/XI/Material_Master_V010'>ZMI_OB_A_MATMAS05_Material</SAP:Interface></SAP:Main><SAP:ReliableMessaging SOAP:mustUnderstand='1' SystemErrorAckRequested='true' ApplicationAckRequested='true' ApplicationErrorAckRequested='true'><SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService></SAP:ReliableMessaging><SAP:DynamicConfiguration SOAP:mustUnderstand='1'><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='SNDPOR'>SAPBDV</SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='RCVPOR'>LS/ALEISR</SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='RCVPRN'>LS_ALEISR</SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='MESTYP'>MATMAS</SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='SNDPRT'>LS</SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='CIMTYP'></SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='RCVPRT'>LS</SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='SNDPRN'>LS/ALEMPP</SAP:Record><SAP:Record namespace='http://sap.com/xi/XI/System/IDoc' name='IDOCTYP'>MATMAS05</SAP:Record></SAP:DynamicConfiguration><SAP:Diagnostic SOAP:mustUnderstand='1'><SAP:TraceLevel>Information</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:HopList SOAP:mustUnderstand='1'><SAP:Hop timeStamp='2008-02-25T15:02:22Z' wasRead='false'><SAP:Engine type='IS'></SAP:Engine><SAP:Adapter namespace='http://sap.com/xi/XI/System'>IDOC</SAP:Adapter><SAP:MessageId>dce3b2a9-bf11-39f1-b785-001a4b061f90</SAP:MessageId><SAP:Info>MATMAS.0000000001383325:20080225160220</SAP:Info></SAP:Hop><SAP:Hop timeStamp='2008-02-25T15:02:22Z' wasRead='false'><SAP:Engine type='IS'>is.66.emhbssap05</SAP:Engine><SAP:Adapter namespace='http://sap.com/xi/XI/System'>XI</SAP:Adapter><SAP:MessageId>dce3b2ab-1f8d-6ff1-b785-001a4b061f90</SAP:MessageId><SAP:Branch><SAP:MessageId>dce3b2ab-1f8d-6ef1-b785-001a4b061f90</SAP:MessageId><SAP:Service>Integration_Server_Development</SAP:Service></SAP:Branch><SAP:Branch><SAP:MessageId>dce3b2ab-1f8d-6ff1-b785-001a4b061f90</SAP:MessageId><SAP:Service>ZBSV_PDM010</SAP:Service></SAP:Branch><SAP:Info>3.0</SAP:Info></SAP:Hop><SAP:Hop timeStamp='2008-02-25T15:02:24Z' wasRead='false'><SAP:Engine type='AE'>af.isd.emhbssap05\sapdbisd</SAP:Engine><SAP:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</SAP:Adapter><SAP:MessageId>dce3b2ab-1f8d-6ff1-b785-001a4b061f90</SAP:MessageId></SAP:Hop></SAP:HopList></SOAP:Header><SOAP:Body><sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'><sap:Payload xlink:type='simple' xlink:href='cid:payload-DCE3B2A9BF113BF1B785001A4B061F90@sap.com'><sap:Name>MainDocument</sap:Name><sap:Description></sap:Description><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest></SOAP:Body></SOAP:Envelope>

--SAP_DCE3B2AB48C07FF1B785001A4B061F90_END

content-id: payload-DCE3B2A9BF113BF1B785001A4B061F90@sap.com

content-type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns0:createUpdatePart xmlns:ns0="http://www.ptc.com/infoengine/soap/rpc/message/"><parts><item><materialgroup>00441024</materialgroup><name>PALET+DEKSEL 650X2430 (416.112.43071)</name><number>000000000002506280</number><state>10</state></item></parts></ns0:createUpdatePart>

SAP_DCE3B2AB48C07FF1B785001A4B061F90_END

thanks & regards

prabhat

[Former Member]

Prabhat,

Henrique is right. XI does not support SOAP calls in a format you need. So you have only one option now - ask the Web Service developer to re-create the web service and ask him NOT TO USE ARRAYs as parameters. Sorry.

Peter

[Former Member]

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

[Former Member]

Hi ,

I checked with test data in wsnavigator and it was working fine. Any other suggestion to resolve the issues.

Regards

Prabhat

[Former Member]

Hi,

Has anybody got the solution to the problem.

Thanks & Regards

Prabhat

[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