cancel
Showing results for 
Search instead for 
Did you mean: 

com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException

Former Member
0 Kudos

Hi All,

I am getting this exception when calling the adaptive webservice based on a wsdl.

"com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML is not valid. Node <PrimaryAccountPOBox> child of <Account> not described in Schema"

But i do have the node <PrimaryAccountPOBox> as child of <Account> node in wsdl schema.Is there anything else that we need to look into it.

This is the part of the wsdl corresponding to the problem.

<xsd:complexType name="Account">

<xsd:sequence>

<xsd:element name="PartyTypeCode" maxOccurs="1" minOccurs="1" type="xsdLocal1:string30"/>

<xsd:element name="PartyUId" maxOccurs="1" minOccurs="1" type="xsdLocal1:string30"/>

<xsd:element name="PayerGlobalId" maxOccurs="1" minOccurs="0" type="xsdLocal1:string100"/>

<xsd:element name="PayingLocation" maxOccurs="1" minOccurs="0" type="xsd:string"/>

<xsd:element name="PricingMasterAccountId" maxOccurs="1" minOccurs="0" type="xsd:string"/>

<xsd:element name="PricingMasterGlobalId" maxOccurs="1" minOccurs="0" type="xsdLocal1:string100"/>

<xsd:element name="PrimaryAccountPOBox" maxOccurs="1" minOccurs="0" type="xsdLocal1:string40"/>

<xsd:element name="PrimaryAccountCity" maxOccurs="1" minOccurs="0" type="xsdLocal1:string50"/>

<xsd:element name="PrimaryAccountCountry" maxOccurs="1" minOccurs="0" type="xsdLocal1:string30"/>

<xsd:element name="PrimaryAccountPostalCode" maxOccurs="1" minOccurs="0" type="xsdLocal1:string30"/>

<xsd:element name="PrimaryAccountState" maxOccurs="1" minOccurs="0" type="xsdLocal1:string10"/>

<xsd:element name="PrimaryAccountStreetAddress" maxOccurs="1" minOccurs="0" type="xsdLocal1:string200"/>

<xsd:element name="ListOfAccount_AccountBillFrom" maxOccurs="1" minOccurs="0" type="xsdLocal1:ListOfAccount_AccountBillFrom"/>

</xsd:sequence>

</xsd:complexType>

Any suggestions greatly appreciated...

Accepted Solutions (1)

Accepted Solutions (1)

chintan_virani
Active Contributor
0 Kudos

Aravind,

Looks like that the WebService signature is changed in the backend. Redeploy the WebService or else create a new model from the WebService and check if you get same error.

Chintan

Answers (0)