XML schema in MDM Console

Hi! I have created a new XML and XSD for catalog item load. This is for batch processing of imports. I understand that I have to assign the format and XSD to the port relevant for this load. Before I can do that, I have to add the new XSD via Console > Admin > XML Schemas. The XSD is located on my C: Drive. After I have added the XSD schema, I noticed that the File Name colume is showing 'C:\product.xsd'. This is different from the other XSD that already existed in the system. For example, MDMSupplierListTransmission has filename MDMSupplierListTransmission without Namespace.xsd. My questions are:
1. I assume that the xsd MDMSupplierListTransmission is located on the server? If so, where can I find them?
2. For the XSD that I have added, is there a way for me to have it load onto the server (assuming 1 is correct)?
Appreciate your enlightenment on this.
Cheers!
SF

Hi SF,
If you have generated an XSD File from your system and then uploaded from the system to your MDM console.
It should work fine without nay problem.
Thats the standard way to do it,if you dont have an already existing XSD and have to create one..
Once the XSD file is loaded in console and its correct ,then your XML file must be allowed to import using it.
Hope It Helped
Thanks & Regards
Simona Pinto

Similar Messages

How to change XML Schema in MDM Console?

Hi Experts,
My scenario: SRM send products to MDM Catalog using PI.
I need to change the XML Schema (XSD) for processing some new fields that don't exist in Catalog. So I created a copy of the XSD file in my station and made the necessary changes.
In XML Schema (MDM Console), I changed the FileName for getting the XSD I created.
But when I tested SRM Shopping Cart again, this couldn't access the products in Catalog anymore.
1) After my chage the FileName shows the name with "c:\Documents and Settings\...". Does it work?? Is this the cause of the error?
2) Do you know why my change affect the Shopping Cart access to the products in the Catalog?
3) Now I don't know how to undo my change in FileName. I can't do it because in the FileName MDM Console it doesn't allow to write it. It allows only to choose a file in some place, my station for example.
Could anyone help me?
Thanks!
Rose

Hi Kanstantsin,
I was analysing what you explain, but it was not exactly this problema. But what you wrote, help me to understand better the MDM and lets me know more about schemas .
Thank you very much for your help.
Hi Vinary,
It was exactly this. I had edited the name. I changed it and now it is working.
Thank you very much for your help!
Rose

Problems importing an XML Schema

Hello,
I am trying to import an XML schema using the MDM Console.
In the Console Hierarchy tree I right-click on the MDM repository into
which I want to import the XML schema and choose Import
Repository Schema from the context menu and finally I choose a simple XML file.
Then an message appears: "MDS Version mismaths. Upgrade the source repository to the latest version and import the original schema again"
I use the SAP MDM Console for Windows, version 5.5 SP4. There is another way to import an schema in my repository? This Console version really doesn't support it?
Thank you.
Could I import my Schema of my repository using MDM Import manager?

Hi Marta,
MDM Console will not update the schema.If you select an xml schema in the import manager and try to specify an xml file with different structure,Then it will give you error and will not allow you to import.
You define xml schema into MDM console so that u can import data into MDM repository from the xml file or files having same structure as defined into xml schema table of repository.
The XML Schema drop-down list in Import manager includes an entry for each XML schema you define in the MDM Console. For each XML Schema defined in the console, you can select multiple XML source files, each having the same structure.
Hope it will help you.Let me know the result and further queries if any.
<b>
Please remark if it helped you.</b>
Thanks,<b>
Shiv Prashant Dixit</b>

Using xml schema problem (SAP MDM 7.1 Syndicator)

Good day !
I try to syndicate directory which correspond to some xml-schema and I have a problem.
I want to syndicate data from hierarchy table which have one field which have a type like lookup <Flat> (multivalued).
In XML-schema element "DEF_PRODUCT" and "DEF_PRODUCT_CODE" - attribute presents hierarchy table.
"CREDIT_PRODUCT" and childs presents linked flat table.
According idea and business rules I must get the result like this: each "DEF_PRODUCT" have N-"CREDIT_PRODUCT". One - to- many.
But when I set up all map completely and look to xml result file I start to be disappointed.
XML result file approximately must be like this:
<DEF_PRODUCT>
    <CREDIT_PRODUCT/>
    <CREDIT_PRODUCT/>
    <CREDIT_PRODUCT/>
</DEF_PRODUCT>
but in result I have all <CREDIT_PRODUCT> in one node and child attributes.
I attach 3 pics which explain my situation.
xml-schema :[http://xmages.net/storage/10/1/0/6/3/upload/42ca6ca8.jpg]
field mapping: [http://xmages.net/storage/10/1/0/6/a/upload/bbbc09f2.jpg]
example: [http://xmages.net/storage/10/1/0/c/c/upload/817b0e23.jpg]
Anybody can help me?
About software : SAP MDM 7.1 (7.1.04.139)
P.S: My problem can be resolved succesfully if I will use 1 <main> table and 1 <qualified flat> table.
       But in my case I must use hierarchy - structure because it most usable for business - users

>
Christian Heuer wrote:
> Hi,
>
> now I understood and you really have got a point here. But the question is whether you need key mapping then on the remote key level with a tuple anymore. If yes, you won
>
> Best regards
> Christian
If SAP MDM will present many opportunities to me I will be very glad.
I repeat I must get output xml which have the pair like "RemoteKey"="RemoteSystem" in tuple subnode.
In tuple, after your advices.
Ideally, Syndicator must present to each user ability to choose pair "RemoteKey" = "RemoteSystem" in each subnode like <LookUp> table in root (look at my example pic).
Imagine you have one root table and N-linked <lookup> tables.
Tree like this :
<main tbl>
<subtbl1/>
<subtbl2/>
<subtbl3>
     <childtbl1/>
     <childtbl2/>
</subtbl3>
</main tbl>
It's dangerous to deprive SAP MDM user to select pair "RemoteKey" = "RemoteSystem" from ROOT to ALL and LAST LEAF in abstract hierarchy. How do you think ?
Now, I haven't abilities to solve my problem using standard resources. Really ?

Problem with XML import MDM 7.1 - Can't generate Xml Schema

Hi All,
When I try to open an XML file using Import manager, I'm getting some errors, as detailed below. I mention that I'm using MDM 7.1.
The first error I received was the following:
"Can't open C:/Program files/SAP MDM 7.1/Import Manager/XSD.exe". I copied the file xsd.exe in the Import Manager folder, as suggest here:
Re: Import Manager Error.
Afterwards, I received a new error:
"Can't generate Xml Schema for: C:/Program files/SAP MDM 7.1/Import Manager/filename.xml"
If anyone has faced the same problem - and solved it -, could you please help me find the reason for this behaviour?
Regards,
Laura

Hi Laura,
The error message "Can't generate Xml Schema" might be related to DTD. the XML file has a directive for loading DTD.
MDM doesnot support DTDs.
Remove the DTD line and make sure there is only one root element in the XML file and try again.
Hope this helps,
Bes t Regards,
Silpa Chillakuru

Switching ON validate xml(Schema Validation) in BPEL Console for AIAtesting

While we were testing Oracle O2B pip, we have recently switched on schema validation by turning it on to 'Strict' so that we can Validate
XML in BPEL Console. Earlier when we were testing we had turned the schema validation as 'None' on BPEL console, and hence everything was working fine and
no errors we popping out while creating sales order in Siebel CRM. But the moment we put validate xml to ' Strict' it starts throwing validation errors.
So can you please help us to know whether it is right to test the Oracle O2B pip by putting validate xml to 'Strict'? If it is fair to test it by switching
ON Validate XML(putting validate xml to 'Strict') then we are getting below error.
We are creating a new sales order in Siebel CRM and when we check in BPEL console it was faulted at UpdateSalesOrderSiebelCommsProvABCSImpl (v. 1.0) .When we checked the BPEL flow it is throwing error at InvokeUpdateUpsert.
Error is According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.a: Invalid content was found starting with element 'xsdLocal1:Process_spcInstance_spcId'. One of '{"http://siebel.com/asi":Process_spcInstance_spcId}' is expected.
Steps for Switching on Validation ?
1)     Login to BPEL Console
2)     Go To Configuration section
3)     Schema Validation changes
a.     ON: populate validateXML with value strict
b.     OFF: populate validateXML with value none
Really appreciate if you can help..

hi
Indeed, the "Validate XML" menu option only shows "Validate XML: 0 errors, 0 warnings.".
But, if you look at the "Design" tab for your schema, the "invoices" element node contains an "xsd:invoice" sequence shown in red. If you change "xsd:invoice" to "invoice" this becomes white and the node can be expanded.
One other thing, registering an XML Schema in JDeveloper like the one you posted, isn't possible without an "oracle.xml.parser.schema.XSDException" (without further details).
regards
Jan Vervecken

Unable to find root element in XML Schema when Syndicating (SAP MDM)

Hi experts,
We are having a problem with our Syndication.
We have created an XML Schema using XML Spy. We need a namespace, and this is 70 characters long (in other words, far shorter than maximum at 255 characters).
<xs:schema xmlns:ns="http://schemas.xxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" xmlns:xs="http://www.xxxxx.org/2001/XMLSchema" targetNamespace="http://schemas.xxxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" elementFormDefault="unqualified" attributeFormDefault="unqualified">
When opening the xml schema file in Syndicator, the root field is disabled.
If we remove namespace in heading of xml schema, the root field is enabled, and the root element is correct.
How can we make use of the XML schema when we need namespace?
We have tried to add namespace annotation ns: to all type definitions:
<xs:element name="ServiceCategory" type="ns:ServiceCategoryType">
This did not help.
Please advice.
KR,
Thomas
Edited by: Thomas on Mar 2, 2011 2:12 PM

>>We need a namespace, and this is 70 characters long
If you want namespace to appear in XML and your XSD has it too. please add the namespace under "URI" attribute in XML schema in Console.
You need to import the XSD in Console first, specify namespace under URI and then use this to build syndication map.
Thanks
Aamir

Need to add a new field to the Schema for MDM Syndicator

We are running MDM 5.5 SP6.
We have a requirement to add a new field and syndicate the new field to the our Procurement System.
I was able to add the new field to the repository and schema in SAP MDM Console. However, when I went into the Syndicator to map the new field (which I do see) to the new Schema field, I don't see the new field to map in the Schema.
How can I change the existing syndication jobs (11 of them) to use the new Schema? Or do I have to recreate all of them?
Thank you in advance!!!

Hi Janynne,
I hope you have modify the Syndication XSD(add new field) and then load it in XML Schema table of MDM Console, right ?
If you have done it, now open MDM Syndicator>Go to File>Open, select the required Remote system and Available map.
Now your existing map will be loaded which has not the required added field, Now again, go to file-->Export.
Give file name and save this syndication map on your Desktop. Once you have done this.
Go to File>New>Select respective remote system and Type as XML Schema if you have loaded this XSD in Console else select Type as XML Schema file and select the modified XSD (added new field XSD) from Desktop. Once it is loaded, import the existing syndication map(which you have exported as said above) which should have all the fields mapped, now in target side you will have here new added field too, map it with required source field in Item Mapping and then go to file>Save as>select the required Remote system and give new map name. Use this map for exporting files for future reference.
Also, if your are using Port Concept, you need to change the Properties Map and XML Schema in Port of MDM Console.
Regards,
Mandeep Saini

Updated xml schema not reflected in Import Manager and Syndicator

Hi all,
We have a perfectly running MDM scenario using custom XML schema for import and syndication. I have now updated the schema by adding a couple of fields to the schema and uploaded the new schema to MDM using Console - Admin - XML Schemas, and we have added the same fields in the repository. However, when I open Import Manager or Syndicator the xml schema is not updated, it is still showing the old version without the new fields. The fields added to the repository show up just fine.
I have searched around the forum and it suggests I actually have to re-create manually all mappings with the new schema?! I cannot believe this is really necessary and would mean massive amounts of work.
I have tried to export old maps and create new map with new schema. Then the new fields show up, but when I import the previously exported map the old schema returns and the new fields disappear.
Any help with this seemingly very odd behavior is very much appreciated!
Thanks,
Kenneth

Hi Kenneth, Aamir
the statement
> Uploading the XML schema in Console is mainly a placeholder, it not not synced with Import Manager or Syndicator schema at runtime.
is not completely true. You have to differentiate the MDM version and the tools:
MDM 7.1 Import Manager: uses the actual XSD of MDM Console
MDM 7.1 Syndicator: stores the XSD as part of the map and disregards the one in MDM Console
MDM 5.5 Import Manager: stores the XSD as part of the map and disregards the one in MDM Console
MDM 5.5 Syndicator: stores the XSD as part of the map and disregards the one in MDM Console
Best regards
Michael

Problem with "Add new xml schema"

Hi,
When i add a new xml schema to my repository, the Console stop responding.
It happens for all repository. Have any clue why?
I am using MDM SP05 5.5.42.48
Thanks in advance for you help
Best regards,
Arun prabhu S

Hi Arun,
Kindly visit the following links:
[http://help.sap.com/saphelp_mdm550/helpdata/en/42/e9cfa1d2e23ee6e10000000a1553f7/frameset.htm]
[http://help.sap.com/saphelp_mdm550/helpdata/en/fe/8aa2bbdb0d41a0a6b37194ea614f11/frameset.htm]
[http://help.sap.com/saphelp_mdm550/helpdata/en/7a/d536f2aae04747b1f48afbff4834b1/frameset.htm]
Hope it will suffice to hint you.
With warm regards,
Krutarth

Port and XML Schema

I wanted to configure the Port and XML schema for a repository.
I followed the following steps.
I have XML Schema file in my local disk. Then I created Port in the console.
However I am not able to see any folder structure getting created on unix server. The port was saved successfuly.
I can not see the Ready folder for this particular folder.
Can you please help me?

Hi SudhaViz,
Firstly create a remote system and associate that with the port.
You can find the port in the following path of that particular remote system.
C:\Program Files\SAP MDM 7.1\Server\Distributions\HostName_DB\Repository Name\Inbound\Remote_System\Port\Ready,
C being the drive where you have installed MDM Server
Thank you,
Minaz

Location of XML schema file (XSD)

Hi! Previously a XML schema was imported into the Console Manager and used for the import of data into the repository. Now we have made some changes and I would like to change the XML schema file. However, I would like to get a copy of the previously import schema (XSD) file from the system. Does anyone know where this file can possibly be held? Any way for us to extract this file to update?
Cheers!
SF

Hi SF,
the XSD is actually stored in MDM's database. One option to export is using the transport schema mechanism in MDM console - asuming that you're on MDM 7.1. If so, right-click on your repository in MDM console and choose Transport -> Export Repository Schema in the context menu. Doing this you'll get a huge XML file describing your repository. Open this XML in a suitable editor (e.g. IE, Wordpad, XML Spy, and so on) and check the file contents. Somewhere inside you'll find a section for XML Schemas and your XSD.
If you are on 5.5, the only option is accessing the DB directly...
Best regards
Michael

Exporting XML schema

Hello All,
When i am trying to export xml schema of repository in console it is giving Unhandeld exception.
Can any one have any idea about it?
Thanks
Ankit

Hi Ankit,
Exception in Exporting XMl schema can occur due to the following reasons
1) If there are any Fatal error that cannot be repaired by MDM.
Check to see if there are any Fatal errors which cannot be repaired and see the log.If there is some field or lookup table error which you cannot fix then try deleting and recreating it and then recheck the rep.
2)The second possibilities could be the format is not saved as XML while exporting.Check it.
Hope it helps
Thanks & Regards
Simona
Edited by: Simona Pinto on Feb 27, 2008 10:50 PM

How to enhance the fields into xml schema?

Hi Expert,
We are at SRM-MDM Catalog 3.0 SP02, we enhanced two fields in the contract data which were transfered from the SRM via xml. But when the MDM import manage do the mapping between the xml file and MDM catalog items automatically, it will bring a exception with the mapping error. The error message is "Logon Error: Source file dose not conform to XML schema. Element <field name> not found in the xml schema."
How could I add these fields to xml schema?
The problem is resolved.
Edited by: Wendrin Duan on Nov 5, 2009 5:01 AM

Hi
Did changing the Name of the Schema in the console to be the same as the Name of the Schema file solve the problem.
I take it you used the output file with the custime fields to create the Schema file so as to have a consistent structure.
REegards,
Iggy

"Source File does not match XML Schema"

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@[email protected]"
>
     <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>

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.

XML schema in MDM Console

Similar Messages

Maybe you are looking for