on 09-26-2014 1:53 PM
Hello David
There is a issue in your External WSDL structure which does not match with PI standards.
You need to check the structure of WSDL in Service Interface. All the fields should be of category "Complex Type, Element or Attribute". If any of the field's category is different then you have to change it manually.
Thanks
Dheeraj Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
When I try to generate de Service Consumer (Proxy) with the wizard of the TCODE SE80, when the process finish appears the following error: "message part refers a type, not an element".
It's possible the data of WSDL it's incorrect?
Could be incorrect, but also take into account that not all XSD schemas are supported by abap proxies. You might have to re-encode your WSDL just to have it generated in se80.
For example in PI 7.1:
Supported XML Schema and WSDL (SAP NW PI 7.1) Excel List
But since you are directly generating it using SE80, this note will help
SAP Note 944029 - XML Schema Supported by ABAP Proxy (Thanks )
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can generate proxy for external defintion, but make sure that service interface should have this external definition, and check external definition xsd well formed or not. then please cross check the type of the field once again.
Regards
Srinivas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
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.