WebSevice Problem in IDOC2Webservice

[Former Member]

Dear Friends,

I'm doing IDOC to Webservices scenario, where in IDOC is generated in CRM server and posted to PI then the fileds of IDOC has to be mapped to webservices.

I have got the webservice that is generated from a .net server, when I'm consuming the webservice, it was not showing all the required fields that are to be mapped with an IDOC fields in mapping.

These fields can be visible in xmlspy.

Have any one worked on this scenario please help me out.

I feel there if problem with some name spaces in the imported wsdl.

Please dont provide any links.

If you want furthur information I will provide.

Thanks in advance

Praveen

[Former Member]

Solved!!!!

This is due to .xsd's that come along with the WSDL files where .xsd's will have definition of the descriptions specified in WSDL.

Regards

Praveen

[Former Member]

check.

Symptom

In the Integration Builder of SAP NetWeaver 2004 and SAP NetWeaver 2004s ,

problems occur during the import of xsd and wsdl files as external

definitions if the target namespace contains more than 60 characters. The

system does not issue any error message, however, the list of the

recognized messages remains empty.

More Terms

Namespace, repository namespace, XML Namespace, Integration Repository,

External Definition

Cause and Prerequisites

In SAP NetWeaver 2004 and SAP NetWeaver 2004s, repository namespaces cannot

contain more than 60 characters. When the system reads xsd and wsdl files

as external definitions, it automatically uses the respective target

namespace as the repository namespace of the external messages extracted

from that namespace. If this target namespace has more than 60 characters,

the system does not extract any message.

Solution

For a wsdl file, you simply need to edit the target namespace manually (

attribute "targetNamespace" of the wsdl:definitions element) and reduce the

number of characters to less than 60. For the structure of the extracted

messages (exception: import assuming rpc style binding, see below), this

target namespace does not have any importance.

For a xsd file, refer to the first case. Import the xsd file, navigate to

the tab with the generated wsdl file, copy this to an editor and shorten

the target namespace. Then, import the edited wsdl file as an external

definition.

There is no length limit for the xml namespace name for definitions of

message mappings. If you want to generate a proxy from the external

message, the xml namespace must not be longer than 250 characters.

In SAP NetWeaver 2004 as of SP16 and AP NetWeaver 2004s as of SP07, you can

extract messages from wsdl files with rpc style binding. In this case, the

system uses the target namespace of the wsdl definition as the xml

namespace for the messages. If the target namespace is too long, first

import the file with the selection for using the rpc style, copy the

generated file into an editor and shorten the target namespace. Then,

re-import the file but use the selection "from all contained message

definitions".

[Former Member]

Hi ,

U r target namespace is more than 60 characters in thewebservice, Edit it to below targetnespace in wsdl file. There is no problem in editing the namespace.

Then when importing the file u can see all the methods and fields.

Regards,

Jayasimha JAngam