XSD says no message exists while usage in MM

[Former Member]

Hi,

I am facing a very strange issue

its a IDOC to Soap scenario.

I am using XSD for MM and I have URL and location seperately

When I try to use XSD in MM, it says no message exists,

when I use the same in SPY , I could able to transfer the test data succesfully

but in XI, MM, it says no message exists, when I try to drag the external definition as input to MM

I have other 23 WSDL, for which I was succesfully able to post the data using XSD.

What could be the reason?

why is XI not able to understand the XSD? (that too.... after I have already posted data succesfully using SPY? implies no wrong in XSD)

has anyone faced same kinda issues earlier?

plz help

[prateek · Accepted solution]

For this xsd, open the external definition. Can u see any message name under "Messages" tab there. If nothing is present then it means that ur XSD is not proper (May be a missing root element)

Regards,

Prateek

[Former Member · Accepted solution]

Hi Prateek,

I have tried more than 50 times

I dont see any message under "Messages" tab any time.

how do I check if the root element exists or not?

when I send test data from XML SPY, it updates the data and I could see it

If there was no root element, it wouldnt have happend. am I correct?

if its issue with root element, how do I trace it?

thanks

[prateek · Accepted solution]

If there was no root element, it wouldnt have happend. am I correct?

I think not always.

I couldnt think of any solution except u pasting ur xsd here.

Regards,

Prateek

[Former Member · Accepted solution]

Here is the XSD :

<?xml version="1.0" encoding="ISO-8859-1"?>

<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:l="http://www.abcd.com/application/ws/location" xmlns:att="http://www.abcd.com/application/ws/entityAttribute" xmlns:cr="http://www.abcd.com/application/ws/confirmedRequest" xmlns:p="http://www.abcd.com/application/ws/part" xmlns:crl="http://www.abcd.com/application/ws/confirmedRequestLine" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.abcd.com/application/ws/confirmedRequestLine">

<import namespace="http://www.abcd.com/application/ws/part" schemaLocation="http://206.13.59.162:8080/Branch62/services/ConfirmedRequestLine?xsd=xsd1" />

<import namespace="http://www.abcd.com/application/ws/location" schemaLocation="http://206.13.59.162:8080/Branch62/services/ConfirmedRequestLine?xsd=xsd4" />

<import namespace="http://www.abcd.com/application/ws/confirmedRequest" schemaLocation="http://206.13.59.162:8080/Branch62/services/ConfirmedRequestLine?xsd=xsd7" />

<import namespace="http://www.abcd.com/application/ws/entityAttribute" schemaLocation="http://206.13.59.162:8080/Branch62/services/ConfirmedRequestLine?xsd=xsd3" />

<element name="ConfirmedRequestLines" type="crl:ConfirmedRequestLines" />

<complexType name="ConfirmedRequestLines">

<sequence>

<element maxOccurs="unbounded" minOccurs="0" name="Location" type="crl:Location" />

</sequence>

</complexType>

<complexType name="Location">

<sequence>

<element maxOccurs="unbounded" minOccurs="0" name="Part" type="crl:Part" />

</sequence>

<attribute name="name" type="l:nameString" use="required" />

</complexType>

<complexType name="Part">

<sequence>

<element maxOccurs="unbounded" minOccurs="0" name="ConfirmedRequestLine" type="crl:ConfirmedRequestLine" />

</sequence>

<attribute name="name" type="p:nameString" use="required" />

</complexType>

<complexType name="ConfirmedRequestLine">

<sequence>

<element minOccurs="0" name="CustomAttributes" type="crl:CustomAttributes" />

</sequence>

<attribute name="confirmedRequest" type="cr:nameString" use="required" />

<attribute name="line" type="integer" use="required" />

<attribute name="requestDate" type="date" use="required" />

<attribute name="dueDate" type="date" use="required" />

<attribute name="quantityOrdered" type="integer" use="required" />

<attribute name="quantityReceived" type="integer" use="required" />

<attribute name="requestStatus" type="crl:requestStatus" use="required" />

<attribute name="supplierLoaction" type="l:nameString" />

<attribute name="proposedRequest" type="double" />

</complexType>

<complexType name="CustomAttributes">

<sequence>

<element maxOccurs="8" minOccurs="0" ref="att:CustomAttribute" />

</sequence>

</complexType>

<simpleType name="requestStatus">

<restriction base="string">

<enumeration value="Open" />

<enumeration value="Closed" />

<enumeration value="Partial" />

</restriction>

</simpleType>

</schema>

Nikhil.

[prateek · Accepted solution]

I used it. In my case, under the Message tab, i can see "ConfirmedRequestLines". I think u r not importing the proper xsd. Its working for me.

Regards,

Prateek

[Former Member · Accepted solution]

I have changed my client URL to abcd.com in the entire XSD and posted here

If I import the same xsd that I have posted to you, I can able to see Message under messages tab.

But when I replace the www.abcd.com with the actual URL, it do not shows up any messages again.

does it hint anything to u?

where is the exact problem with?

please help

thanks and regards,

venkat.

[henrique_pinto · Accepted solution]

nikhil,

Integration Repository has a known issue of only accepting up to 40 chars namespaces in imported documents. Any namespace greater than that will be ignored.

I think that's your case. Please review your namespaces to match that limitation.

Regards,

Henrique.

[Former Member · Accepted solution]

Hi Henrique,

I think that's your case. Please review your namespaces to match that limitation.

Does this mean I can cut down the length of namespace?

doesnt it matter anything while execution?

please reply

thanks n regards,

nikhil.

[Former Member · Accepted solution]

Thanks Prateek and Henrique,

the problem was because of length of NS

the NS cant be more than 60 characters

Nikhil.

[henrique_pinto · Accepted solution]

Hi nikhil,

thank you for correcting me: the maximum length is 60 chars indeed.

And for the namespace, you can just reduce the length (cutting some sub-divisions that you have).

Regards,

Henrique.