cancel
Showing results for 
Search instead for 
Did you mean: 

MS Project Server & SAP WSDL-Compatibility

0 Kudos

Hello everyone,

I recently encountered a quite interesting problem when trying to consume a Microsoft Project Server 2007 Webservice with ABAP (Netweaver 700 EP16).

Project Server does offer a variety of 19 differently complex web services. Consuming services and calling methods that use simple data types does work just fine.

But digging deeper to the real interesting methods, there is the method ReadProjectList, offered by the "Project"-web service. It uses the complex data type ProjectDataSet, which would fill about 14 pages if you printed out the corresponding WSDL-part. The problem is, when you create the ABAP-proxyclass, ABAP does not create the correct data structures which you need to call the web service properly in a program. It seems that the ProjectDataSet gets just overjumped.

In the warnings-tab, there is a suitable warning: "<any>,<anyAttribute> are not supported"

There is a SAP note that contains the helpful document Proxy_WSDL_XSD_Restrictions.xls, which says "Ignored with warning" for "any" and just a "planned" for a later release.

So there seems to exist a incompatibility issue, which I would like to solve before 2013.

You can download the Project-wsdl-document here: http://studentisches.com/Project_SDN.xml

Now the question: Does anyone have experience in solving this problem? Is editing of the WSDL a good solution? How does the edited WSDL have to look like to get the complex data type ProjectDataSet properly generated in the proxyclass?

Thank you for reading! Your thoughts are enourmously appreciated.

View Entire Topic
0 Kudos

Manually editing a WSDL-File to fix the automatic creation of the Consumer proxy does work technically, but is complicated to develop, because testing of the wsdl does take a while (regenerating and activating the consumer proxy) and it's basically trial and error while not getting any useful information from abap except of warnings ("does not support XML schema tag any, anytype, etc.").

Furthermore, every embedded wsdl-file with the unsupported Tags has to be edited manually. It is definitely no long-term-solution, so a short/midterm support for the appropriate xml schema and wsdl-tags would be welcome.