on 11-20-2013 7:15 PM
Hi Experts,
We have one idoc to SOAP scenario.We are calling third party web service and placing the file at their local tool.The local tool will validate the XSD and process the file if XSD is correct.
Now the issue is whenever we are sending the file to third party,they are not receiving the messageheader feild ( first feild in xsd) ,hence file is not getting processed at their end.
If I check PI receiver channel or adapter engine, the output file is having header and correct.
So seems something is happening while calling webservice.
I would really appreciate your inputs on it.
We are not using any specific setting in SOAP channel.
The SOAP action is the web method which we are calling in this case.
The error at third party side is
Error=Invalid Message
Received
XML in message does not match schema at line 1 character 41
The element 'schedule' has incomplete content. List of possible elements
expected: 'messageHeader'.
Schema Validation Failed: XML in message does not match schema at line 1
character 41.
The element 'schedule' has incomplete content. List of possible elements
expected: 'messageHeader'.
Regards,
Varinder Singh
Hi All,
It was the issue with reciever web service.
They have refernce from two namespaces and that was missing in the file,sent by PI.
After web service update,it is working fine.
Thanks for your support.
Regards,
Vikram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Please try executing your request externally by using SOAPUI. After doing this, compare the request generated by SOAPUI to the request that XI is sending. There are some webservices (at least in some of my projects) that are strict with namespace prefixes and would not accept the ns0 generated by PI message mapping.
Hope this helps,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Thanks for the reply.
This is the first time i am working with SOAP.
One doubt here, If we execute the request using SOAP UI and it goes through and gets posted successfully.
How can we compare it with XI request and where can we see the payload that is going through web service.
Also, we need to find where and which field is gettng missed when we are sending the same request via XI..
Thanks,
Vikram
Hi Mark,
I did not find any data in RAW tab.Its just having response data.
But when i import the WSDL from third party to SOAPUI, I found that the field where we are getting the error is named as 'tms:messageHeader' but in our PI XSD, it is maintained as 'messageHeader'.
Can this be the reason?
is there any automatic validation that happens at web service side?
Also, he is able to post the same file manually. So, I am still not sure why it is not getting posted via webservice.
Regards,
Vikram
Hi Vikram,
Try XMLAnonymizerBean to add tms to messageheader
http://help.sap.com/saphelp_nwpi711/helpdata/en/45/d169186a29570ae10000000a114a6b/frameset.htm
Refer http://scn.sap.com/thread/3202784
Regards,
Pranav
Hi Vikram,
You said you call a SOAP service? Why is then a file placed somewhere? Can you please explain in more detail? Did you get a WSDL from the called SOAP service which you used in PI?
Best Regards
Harald
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harald,
We are using the XSD in PI which is being used by the third party tool.
Now, for connecting to that tool, we are going via web service.
With SOAP channel we are going for one particular web method and trying to post the file.
We are not using the WSDL from SOAP service but the XSD being used in PI is similar to SOAP service WSL.
Regards,
Vikram
Vikram,
Can you provide the xml sent from SOAP and the xml received at third party web service.
Regards,
Pranav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.