cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

"Source File does not match XML Schema"

Former Member

on ‎02-05-2007 8:12 PM

0 Kudos

Using MDM 5.5 SP4 Patch 2 (Build 5.5.34.26) on a 32-bit system (WinServer 2003, Enterprise Edition SP1.

This source file and schema have been verified by SAP Tech Support and again using Altova XML Spy. The schema was loaded into MDM through the console and the source file was successfully mapped against it and the data manually imported into MDM. The customer record was then cleansed using the Data Manager and the import map was used to create an inbound port. However, when the Import Server goes to import the file using the map, the following error is dropped into the log: "Source File does not match XML Schema". Has anyone else seen this error?

Thanks, Don

IMPORT LOG ENTRY:

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="MDM_Log.xsl"?>
<MDM_Log version="1.0" path="H:PROGRA~1SAPMDM~1.5IMPORT~1TempMDIS_TASK@@U@070203@182435.xml"

>
	<Open ts-long="18:24:35 GMT, Saturday, February 03, 2007" ts="2007/02/03 18:24:35.108 GMT" pid="8640" host="bp1tulap452" compile-type="RELEASE_32">
		<Trace ts="2007/02/03 18:24:35.249 GMT" tid="7216" entry-no="3">[BP US FUELS CUSTOMER MASTER] Import Task Started. Chunk size[50000], No. parallel chunks[1]</Trace>
		<Trace ts="2007/02/03 18:24:43.890 GMT" tid="5980" entry-no="11">xSaxParser: Starting.</Trace>
		<Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="19">xSaxParser: Ending.</Trace>
		<Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="20">Source file does not conform to XML Schema!<LINE-FEED/></Trace>
		<Trace ts="2007/02/03 18:24:45.312 GMT" tid="7216" entry-no="29">[RESPOSITORY]Import Task Finished. Chunk size[50000], No. parallel chunks[1]</Trace>
	</Open>
</MDM_Log>

SOURCE FILE:


  <?xml version="1.0" encoding="UTF-8" ?> 
- <ns1:CustomerCreateResp xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
- <CUSTOMER>
- <item>
  <CUSTOMERNO>0090154474</CUSTOMERNO> 
  <MDMCUSTOMER>2463</MDMCUSTOMER> 
  <CREATE_DATE>22/01/2007,11:43:49</CREATE_DATE> 
- <RETURN>
  <TYPE /> 
  <MESSAGE /> 
  </RETURN>
- <PT_CONTPART_RETURN>
- <item>
  <MDM_CONTACT>0000000001</MDM_CONTACT> 
  <CONTACT>0001111119</CONTACT> 
  </item>
- <item>
  <MDM_CONTACT>0000000004</MDM_CONTACT> 
  <CONTACT>0002222229</CONTACT> 
  </item>
  </PT_CONTPART_RETURN>
- <PARTNERS>
- <item>
  <CUSTOMERNO>0090154474</CUSTOMERNO> 
  <PARTNER_FUNCTION>RE</PARTNER_FUNCTION> 
  <PARTNER_NUMBER>0001333329</PARTNER_NUMBER> 
  <DEFAULT_PARTNER>X</DEFAULT_PARTNER> 
  </item>
- <item>
  <CUSTOMERNO>0090154474</CUSTOMERNO> 
  <PARTNER_FUNCTION>WE</PARTNER_FUNCTION> 
  <PARTNER_NUMBER>0001555559</PARTNER_NUMBER> 
  <DEFAULT_PARTNER /> 
  </item>
  </PARTNERS>
  </item>
  </CUSTOMER>
  </ns1:CustomerCreateResp>

SCHEMA:

   <?xml version="1.0" encoding="UTF-8" ?> 
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" targetNamespace="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" elementFormDefault="unqualified">
  <xsd:element name="CustomerCreateResp" type="CustomerCreateResp" /> 
- <xsd:complexType name="CustomerCreateResp">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">682cc2d0aa6e11db9b800015c5888624</xsd:appinfo> 
  </xsd:annotation>
- <xsd:sequence>
- <xsd:element name="CUSTOMER">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">f68988f0a02e11db94bb00166f98336c</xsd:appinfo> 
  </xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" maxOccurs="unbounded">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b20a75811dba9d400166f983d94</xsd:appinfo> 
  </xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b21a75811db9c4800166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="MDMCUSTOMER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b22a75811dbcbac00166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="CREATE_DATE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b23a75811dbcc0300166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="RETURN" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b24a75811db8d5500166f983d94</xsd:appinfo> 
  </xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="TYPE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b25a75811db876d00166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="MESSAGE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b26a75811db85c400166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
- <xsd:element name="PT_CONTPART_RETURN" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b27a75811db8ca900166f983d94</xsd:appinfo> 
  </xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b28a75811dbaae100166f983d94</xsd:appinfo> 
  </xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="MDM_CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b29a75811dbaade00166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2aa75811dbc24c00166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
- <xsd:element name="PARTNERS" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ba75811dbb74500166f983d94</xsd:appinfo> 
  </xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ca75811db9f6500166f983d94</xsd:appinfo> 
  </xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2da75811db9bd800166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="PARTNER_FUNCTION" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ea75811dbb84100166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="PARTNER_NUMBER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2fa75811db852800166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
- <xsd:element name="DEFAULT_PARTNER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
  <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b30a75811db968400166f983d94</xsd:appinfo> 
  </xsd:annotation>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
  </xsd:sequence>
  </xsd:complexType>
  </xsd:schema>

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
‎02-05-2007 10:07 PM
0 Kudos

You have to define the namespace in the URI field of XML Schmea in Console.

In MDM Console,

Admin -> XML Schemas -> Create XML Schema

You have to specify the namespace urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100 in the URI property.

Please update this post if fixed your problem.

Show replies
Show replies
Former Member
‎02-05-2007 10:35 PM
0 Kudos

Adhappen,

Thanks, but that was the first thing we did when we created the schema in MDM. It was declared there and then mapped to using the Import Manager.

Don

Ask a Question