Repository XSD in MDM 7.1

Hi All,
I need to genarate XSD for my one of repository in MDM 7.1.Did all the Configuration Required as explained in Blog and the Video.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c065c565-60a4-2c10-8d95-af250ca89478
http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/d0694d7d-ead4-2c10-8e89-c3312fb63581
But however while creating the Project and Folder in Netweaver Developer Studio I am not able to see MDM WIZARD in NWDS.
my NWDS Version : Version: 7.0.16
Do I need to download 7.1 version of NWDS?
Could anybody help me on this .
Thanks,
Madhu

Now I could able to download CE7.2 and installed plugins Required ,Now I am getting MDM Connection Wizard ,But however I am Getting Error while connecting to MDM Server like  Problem while creating physical connection to MDM server  zzz.com
Please let me know on this.
Thanks,
Madhu
Edited by: Madhusudhan Honnappa on Sep 7, 2010 9:25 PM

Similar Messages

  • Generic Vendor XSD in MDM syndicator

    Hi All,
    I downloaded Generic Vendor XSD file from XI Content and trying to use in MDM syndication.
    But,When I select Generic Vendor XSD in syndication,root element is not coming and ok button is in disable mode.
    please look into my xsd file here...
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/BICONTENT" targetNamespace="http://sap.com/xi/BICONTENT">
         <xsd:simpleType name="PartnerLocalId">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c2fdd4507b2a11dcbf3a0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="60" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="TextShort">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c2fb63517b2a11dcb5250013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="20" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="LanguageCode">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3001e407b2a11dc87310013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="2" />
                   <xsd:minLength value="2" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="MarketTradePartner">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3028f407b2a11dcc4cb0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="36" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="TransportZone">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c30500407b2a11dc8be70013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="10" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GroupID">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3074a307b2a11dca5530013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="32" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GenericVendorId">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c309bb307b2a11dc9d150013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="60" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="CountryKey">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c30c05207b2a11dc9e9d0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="3" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="SourceSystemName">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c31331137b2a11dc830f0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="60" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="TextLong">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c31331107b2a11dc82d80013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="40" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GeoSourceID">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c315a2127b2a11dccda20013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="4" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="TextMedium">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c31cce007b2a11dc9d7e0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="40" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GeoPrcisionLocation">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c31f17f07b2a11dc9fbb0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:integer">
                   <xsd:totalDigits value="4" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="Street60">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c32188f07b2a11dcb5cf0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="60" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="PostalCode">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c323f9f07b2a11dcae280013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="10" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="Region">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c32643e07b2a11dcc0c80013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="3" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="TimeZone">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c328b4e07b2a11dcc11a0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="6" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="CompanyCode">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c328b4e37b2a11dcabfd0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="4" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="City">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c32b25e27b2a11dccc770013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="40" />
                   <xsd:minLength value="1" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="BackEndType">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c32d6fd27b2a11dc993f0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="4" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="NationCode">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c32fe0d17b2a11dc895c0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="3" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GeoLatitude">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3322ac07b2a11dca37e0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:decimal">
                   <xsd:totalDigits value="27" />
                   <xsd:fractionDigits value="12" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GeoAltitude">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3349bc07b2a11dc9f6e0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:decimal">
                   <xsd:totalDigits value="20" />
                   <xsd:fractionDigits value="3" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="Gender">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3370cc07b2a11dcbc340013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="1" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="TelNumber">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3370cc37b2a11dcac2e0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="30" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="BusinessPartner">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c33956b27b2a11dc85200013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="10" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="PartnerSourceSystemID">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c33bc7b27b2a11dc896f0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="2" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="LegalForm">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c33e38b17b2a11dcb0bb0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="2" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="OrgUnit">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c34082a07b2a11dc83200013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:integer">
                   <xsd:totalDigits value="8" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="FaxNumber">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c342f3a07b2a11dc8c6d0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="30" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="LocalVendor">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3453d907b2a11dccc3f0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="10" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GeoPostalCode">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3453d937b2a11dc921f0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="10" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="HouseNumber">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c347ae927b2a11dcb78d0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="10" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="TaxJurisCode">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c34a1f927b2a11dc84640013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="15" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GeoLongitude">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c34c69807b2a11dca0070013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:decimal">
                   <xsd:totalDigits value="27" />
                   <xsd:fractionDigits value="12" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="GlobalUltimateDuns">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c34eda807b2a11dc9ff90013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:integer">
                   <xsd:totalDigits value="9" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="DunsNumber">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c3514b807b2a11dcc48a0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:integer">
                   <xsd:totalDigits value="9" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="ClientObjectType">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c35395737b2a11dcb5ea0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="32" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="DeletionFlag">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c35395707b2a11dca4df0013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:length value="1" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="ApoLocno">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c35606727b2a11dc8ff40013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="20" />
                   <xsd:minLength value="1" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="CountryCode">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c35850627b2a11dccde30013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="3" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="SourceInfoObject">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c35ac1617b2a11dca0230013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="30" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:simpleType name="EmailAddress">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   c35d32607b2a11dc80c90013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:restriction base="xsd:string">
                   <xsd:maxLength value="60" />
                   <xsd:minLength value="0" />
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:complexType name="GenericVendor">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   5d21eea07b2a11dcc8b80013725d3a37
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="GenericVendorID" type="GenericVendorId" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a1cd2d00f46611d9ad8dd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="APOLocation" type="ApoLocno" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a1cd2d01f46611d993e0d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="BusinessPartner" type="BusinessPartner" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             cb1ab990f46911d9ca58d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="GroupID" type="GroupID" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             cb1ab991f46911d9c008d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="CompanyCode" type="CompanyCode" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             e16b4f70f46911d9ac0cd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Country" type="CountryKey" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4b41e260f46a11d980b3d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="DunsNumber" type="DunsNumber" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4b41e261f46a11d9b6acd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="BackEndType" type="BackEndType" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4b41e262f46a11d99c2fd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="LocalPartnerID" type="PartnerLocalId" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9ec56e70f46a11d9a572d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="SourceSystemID" type="PartnerSourceSystemID" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9ec56e71f46a11d9bbbbd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="SourceSystemName" type="SourceSystemName" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             33efe2a0fe9d11d9b2ebc5a20a12cf18
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="SourceInfoObject" type="SourceInfoObject" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             cc2ca950f46a11d9c5edd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="ClientSystemObjectType" type="ClientObjectType">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             33efe2a1fe9d11d9c169c5a20a12cf18
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="MarketTradePartner" type="MarketTradePartner" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             f0780b10f46a11d9b9f7d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="PostalCode" type="PostalCode" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             41ac4ff0f46b11d990dad7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Region" type="Region" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a1cce870f47211d981d6d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="LocalVendorID" type="LocalVendor" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a1cce871f47211d9a2e1d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="GlobalUltimateDunsID" type="GlobalUltimateDuns" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             e110fc30f9d411d9959fc42c0a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="CountryCode" type="CountryCode" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             870a26c0f9d511d992b7c42c0a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Altitude" type="GeoAltitude" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             496718d0f47311d9851dd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="City" type="City" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             496718d1f47311d998b1d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="EmailAddress" type="EmailAddress" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             496718d2f47311d999e9d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="FaxNumber" type="FaxNumber" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             496718d3f47311d99a31d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Gender" type="Gender" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             26ecd820f47411d98ffdd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="HouseNumber" type="HouseNumber" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             26ecd821f47411d9c6e6d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="LanguageCode" type="LanguageCode" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             26ecd822f47411d9ba96d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Latitude" type="GeoLatitude" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             26ecd823f47411d9b1aad7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="LegalForm" type="LegalForm" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             26ecd824f47411d9ac3dd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Longitude" type="GeoLongitude" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             17aa7d70f91c11d9b9a8c3c70a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Nation" type="NationCode" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             26ecd825f47411d9c6d5d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="OrganizationalUnit" type="OrgUnit" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             505fe380f47611d9ce02d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="GeoPostalCode" type="GeoPostalCode" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             505fe381f47611d99a89d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="PrecisionLocation" type="GeoPrcisionLocation" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             505fe382f47611d9c360d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="GeoSourceID" type="GeoSourceID" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             628b1d30f47711d9a05bd7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="Street60" type="Street60" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             c835b9b0f47711d98906d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="TaxJurisdictionCode" type="TaxJurisCode" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             c835b9b1f47711d9c9c3d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="TelNumber" type="TelNumber" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9af28c20f47811d9a820d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="TimeZone" type="TimeZone" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9af28c21f47811d9a064d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="TransportZone" type="TransportZone" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9af28c22f47811d98414d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="DeletionFlag" type="DeletionFlag" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             870a26c1f9d511d98cd2c42c0a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="TextShort" type="TextShort" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             cce01270f47811d9b0c9d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="TextMedium" type="TextMedium" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             cce01271f47811d9b274d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
                   <xsd:element name="TextLong" type="TextLong" minOccurs="0">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             fc8667e0f47811d9b851d7990a12cf0d
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

    Hi JJ,
    most propably the cause for your issur is the namespace definition within the XSD:
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/BICONTENT" targetNamespace="http://sap.com/xi/BICONTENT">
    Solution:
    1. Add the namespace information to the URI field when adding the XSD to your repository in MDM Console
    OR
    2. Remove the namespace information within the XSD as it is not really mandatory.
    This should help.
    BR Michael

  • Can any body help me to create a meaningful repository in SAP MDM

    Hi ,
    I am new to this area . I have read the RKT material provided for MDM 5.5 SP4 and have the software installed with me . I know how to create repositories but what I am looking at is some help where someone can provide me with some repository structure and corresponding excel files so that I can exactly replicate the scenario in my server and learn to import the data . I am looking for a scenario which involves some hierarchies/taxonomies and lookup tables . The excel files for such a repository structure would certainly help .
    Can someone help me out with this ?
    Thanks
    Ravikumar

    Ravi,
    If you allow, this is what I would suggest -
    1) First focus on the concepts. Understand how MDM goes beyond the traditional database concepts of master child relationship and uses concepts of Hierarchy Table, Taxonomy/Attributes tables, Qualified Lookups etc. RKT material exercises are good enough for quick ramp-up on these concepts. Once you have got the concepts, you will be able to easily create a XLS file yourself. Also the fun is not in importing an XLS file that has been created specifically for import into MDM. Any logical data structure in xls should be importable into MDM by using the functionality of MDM Import Manager
    2) In the RKT material you should find an exercise called Case Study. I am emailing a Spreadsheet that created to use with this exercise. It is basically a Products Main Table, with Manufacturers coming from a Hierarchy Look table and Categories and Attributes table to store product classifications.
    Let me know if this was helpful.
    Vinay

  • Region wise Repository for SRM MDM

    Hi,
    We are in Migration of CCM to MDM.
    In CCM we have so many catalogs.
    So we are creating 3 repostoteries in MDM based up on the region.
    Can any pls let me know the how the supplier data can be replicated to MDM ?
    we dont have XI.
    Please let me know is there any jobs to replicate.
    Regards
    Venkatesh P

    Hi Venkat.
    Supplier can be replicated from SRM to MDM through ROS_SUPPLIER_SEND_TO_CATALOG report.
    Also through MDMGX report you can configure the supplier table information fields to send to MDM.
    If you are looking for replicating records from CCM to MDM, if you can export the records in XML then you can import it to MDM through MDM Import Manager.
    Best Regards
    Bala

  • Creating Repository in SAP MDM

    Hi,
    I am getting the below error when I am trying to create a respository in SAP MDM.
    "Error Initializing database engine.".
    Regards,
    Venkatesh

    hi,
    follow the link:
    Installing MDME 5.5
    Database error - MDM server installation
    hope this will help you.
    Regards,
    srinivas

  • SRM MDM 3.0 BMECAT Repository Schema

    Hello at all,
    I have currently run the SRM-MDM 3.0 with the standard respository delivered as archive on the install CD. I still have created some data with the data manager and it runs all very well.
    Now I want to import a catalog based on BMECat 1.2 standard. I Have the complex catalog data XML from the vendor Bechtle and the images folder for the articles.
    When running the Import Manager there are many fields and tables in the source xml that do not excist in the destination hierachy (repository).
    My question is how do I create a repository based on the BMECat 1.2 standard to import the vendor catalog xml ?
    What I still tryed was. Creating a new repository. It's empty except of the standard table like Admin, Images, Products etc.
    Than go to Transport -> Import Repository Schema -> choose the vendor XML
    That doesn' work. I get the Error Message: "There are problems with the transport (XML) which prevent it from being processed"
    I have learned that an XML schema data is described with the ending .xsd but when I try to import the databrowser looks for .xml endings.
    Could someone please advice what's I have done wrong?
    Thanks a lot.
    Rico

    Hi Rico,
    I am not aware of BMEcat standard but in MDM terms you can take the backup of repository in two forms:
    1. Archive/UnArchive -> If you want to move the repository from one MDM server to another i.e. from dev to QA then you can Archive the repository which creates the .a2a file and place the file in the Archives folder of MDM Server installation directory which can then be copied and moved to Archives folder of target MDM server and you can UnArchive it on that MDM server.
    Archive = Repository Schema + Data
    2. Export / Import Repository Schema -> With this method you can export the schema of the repository and create the new repository on some other MDM Server using Create Repository from Schema command. When you perform the export repository schema command, it will ask for the file name and path. You can then copy this schema file and place in the file system of another server.
    Export / Import Repository schema = Repository Schema only
    Regards,
    Jitesh Talreja

  • SAP MDM-GDS repository structure

    Hi,
    Does anybody have any input or knowledge of SAP's direction regarding repository structures for MDM and GDS now that they've begun integrating the functions into the MDM solution the offer?
    At present, whilst the GDS Console is basically just accessing data in an MDM repository, it can't be your core MDM product data repository, but rather it has to be a separate one, set up specifically for GDS and nothing else, and thus it needs to be populated separately.  I am wondering if this is a long term vision, or just a result of the way the package has been developed and that further integration will be forthcoming.
    Any ideas?
    Steve

    Hello lis716
    I'm not recomend working with SAP MDM database directly moreover modify some data at Database level because database structure is close information. (i had expiriens to mass upload users and their roles directly in MDM database, after that operation repository hasn't been started - repair returned a lot of errors and i was very happy when repository has been started)
    You can lost important data because database structure may be modify in any time. 
    SAP MDM provide API for different development platforms as is .NET, ABAP, JAVA, COM.
    My suggestion you should use API in your application for connect to data.
    Additional information about API you can find here:
    https://websmp209.sap-ag.de/installmdm71
    Regards
    Kanstantsin Chernichenka

  • Create MDM repository from repository schema.

    Hi,
    I have exported MDM repository from one MDM console schema and saved it. Now I am trying to create a Repository from a different MDM console using this Schema. I am getting the Error "ERROR LOADING FILE".
    The versions of these MDM are different. Is this causing the failure? How can I overcome it?
    regards,
    MRao

    Hi Mahesh,
    This is an Un-usual error, which even I am facing. In my case there is no version mis-match.  I am trying to take the Export the Schema from a rep in 1 MDM server and then importing into another rep in another server.
    Hence it might not be a version issue.
    However, check the following things in your case.
    1. Check the Original repository for error and repair them if found any. Upload your repository with Updated indices. Export the schema out and save it on your desktop.
    2. Try creating a new repository using Import Schema on the same MDM server and check if its still showing you an error.
    3. Try importing the schema on an Existing repository on the same MDM server.
    4. Try Importing the schema and create a new repository on a different MDMserver.
    Please check it in a test environment and no need to press the OK button while Import schema. We just need to see if the Import schema windows opens.
    If in any case, you do not find the error, then probably we can understand the clear reason of the Error.
    If error still persists, then would advice you to raise an SAP ticket for the same.
    Hope this info helps.
    Thanks and Regards
    Nitin jain

  • MDM 5.5.65.71(Not able to load the repository)

    Hi All,
    We are getting the strange problem in MDM patch 5.5.65.71.
    We have recently upgraded to 5.5.65.71 from 5.5.64.79 and we are getting problem one of our repository while we try to load it.
    The repository is not getting loaded saying that unique constraint violated and duplicates are there for one of the field.
    We have removed the unique constraint in the console level and loaded the repository to check whether any duplicates existing or not. But no duplicates existing in that repository.
    We have again kept unique constraint in the console level and tried  to load the repository but we were not able to do it as it is
    saying unique constraint violation eventhough there were no records which violates unique constraint on our repository.
    Has anyone faced this problem?
    Please share your views on how to get rid of this issue?
    Thanks,
    Narendra

    Hi,
    I would suggest, if you have backup archive file of the repository, then please try by deleting and again archiving repository. it may solve problem. It is suggested to check and verify and take backup of the repository before upgrading MDM server.
    please revert if you don't have backup of the repository.
    Regards,
    Shiv

  • Import and Syndication maps - change in XSD

    HI All,
    Can any one let me know are these are correct if it is then are there any work around solutions?
    We created manually Import and syndication maps.. fine..After few days we changed data type/deleted the filed/added new fields.... In all these above incidents do we need to recreate import and syndication maps????
    There is no other work around for this ??
    2) Even if there is no change in Repository structure but change in import or syndication XSD do we need to recreate all import and syndication maps???
    Your inputs are really helpful.
    Thanks
    Rajeev

    HI Rajeev,
    So for any change in the MDM repository Import maps and syndication maps are not needed to recreate from scrach right?
    For minor changes like field add there is no need.For changes involving deletion of mapped fields,changing types of already mapped fields,deleting mapped tables,one should first unmap the current map and then carry out structural changes.Later one can remap them again,this is to avoid maps from getting corrupt.
    If there is any change in the XSD then there is a possibility to recreate the map from scrach??
    Yes
    Do Update XML schema option avaliable only in MDM 7.1?? not in 5.5?
    Yes
    A good description and usage is given by Aamir here Update of XML syndication map when XSD is changed
    One more thing want to clear : I created a scheme and assigned the XSD.. Now when I created the port I am unable to assing the schema like I do for import map??? then what is the use of XSD schema for outbbound??
    Seems you are not using in the way it is supposed to.the exact usage and defining what feature is available with which port is mentioned in pg no 356 of Console guide.
    What is the usual method of import XSD and Outbound XSD?? Do Source and Target systems provide XSDs to MDM or MDM provides to Source and Target Systems?
    For Standard contents SAP provides ready made xsds.
    It is important to note that xsds are only to make MDM and other system understand the xml so they should be same.
    To do this you can use Altova tool to create xsds based on your xml,also PI can help you do the same.
    You can create xsd with PI for other idoc type too.
    Hope this helps.
    Thanks,
    Ravi

  • XSD for the inbound/outbound file

    MDMers,
    We have customized Material repository supplied with business content of MDM. We have added a few tables/fields and deleted few.
    How do we create XSD from the repository which can be used in Import process and syndication process?
    Thanking you in advance,
    Dan.

    Hi Dan,
    Agreed you have customized your repository by adding and deleting certain fields.
    But the point is from where are you importing your source file.Because the XSD that you use in importinga nd syndicating must match with the input and output XML file.It need not be the Schema of your MDM rep.
    Eg: If you are importing an XML matmas file from ECC having material master record data you will have to upload and use the matmas XSD in MDM console similarly...
    If you are exporting your master data to an ECC system you will need the same matmas XSD in syndicator as well.As while syndicating your Source XSD will be your repository structure any ways it sthe destination xsd which is decided based on wats your target system.
    If are jsut trying and doing an R n D with the tool then you can use the xomlite to create your xsd of the MDM repository forimporting mdm data and syndicating MDM data.
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Creating repository DEBMAS

    Hi experts!
    Unloaded structure IDOC DEBMAS.
    How this structure to load into a repository?

    Please Help me
    I come back to the theme.
    I shall describe the actions step-by-step.
    1. we60 -
    Basic type - DEBMDM06 -> Documentation - XMLSchema - Downloand
    <?xml version="1.0" encoding="utf-8" ?>
    - <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0">
    - <xsd:element name="DEBMDM06">
    - <xsd:annotation>
      <xsd:documentation>MDM: Mass Processing DEBMAS (Customer Master + Addresses)</xsd:documentation>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="IDOC">
    - <xsd:complexType>
    - <xsd:sequence>..........
    2.MDM Console - Create Repository from Schema -> "XMLSchema" -> Error
    PROBLEM  CREATING  from SCHEMA X Cannot read schema file.

  • Error Message in MDM Server Log

    Hi Experts,
    Can anybody tell me what could be the problems if we have the following scenario ?
    For an example: Our MDM Server is based on 5.5 SP06, MDM Server name is DFM and our repository name is MDMQ110.
    1) Checking the Reports from this Repository MDMQ110 from MDM Console, no errors and no warning. This repository can be loaded successfully and completed.
    2) Server Log has an error in message:
    Error: Service 'DFM', Schema 'MDMQ110_m000', ERROR CODE = 0,
    SELECT LENGTH(Data) FROM A2i_Misc_Blobs WHERE Id=1000
    Thanks very much for your help in advance
    Regards,
    WD

    Hi Kanstantsin,
    Thanks for your reply. I have done the stop and repair but It did not help any. By repair, there are no errors and warnings that have been fixed which I can see in the repository reports.
    The Assertion Log has come up first with the messages like:
    6426            2010/01/12 09:07:08.500               Error: Data_2 accelerator does not exist in A2i_CM_Accelerator_Status
    6426            2010/01/12 09:07:08.683               Error: Data_53 accelerator does not exist in A2i_CM_Accelerator_Status
    4884 2010/01/12 09:43:30.335   Error: KeyWord_2_F4_Leng_USA accelerator does not exist in A2i_CM_Accelerator_Status
    As soon as I run into MDM, the Server Log has come up the same messages:
    It looks like not only happened to this repository. As I can see if I load any other repository, there are the same messages in Server Log but only the repository name in the message is different.

  • MDM lookup parameters from File Sender Channel

    Hi SDNers,
    In my current assignment I am required to make an SAP MDM lookup in a JAVA Mapping to fetch certain details to further process the message.
    Currently the MDM server details along with user id and password are maintained in a properties file.
    During Migration from Development to Quality or from Quality to Production Environment this properties file needs to be changed and the mapping needs to be reimported individually in each environment.
    I want to avoid this cumbursome task of changing the properties file and re importing the Java Map on each environment.
    Is there any way to mention the following 3 parameters in the Sender Channel itself (in my case it is FIle Channel)
    Server IP Address, User ID, Password? so that the Java Map at runtime can access these parameters from the channel, as each environment will have different channel.
    I don't know if I can use ASMA or Additional Parameters for achieving this.
    Regards,
    Gautam Purohit

    Hi Michal,
    Can you please elaborate this?
    I need to give parameters like;
    mdm.repository.host=Development_Server
    mdm.repository.name=Development_Rep
    for all three environments.
    How can I achieve this using Value Mapping?
    Regards,
    Gautam Purohit

  • Import multiple info records for 1 material item in repository

    Hi Guys,
    I have got sort of a puzzle I can not solve at the moment, maybe some one can help me to solve it. The situation in our system landscape is as follows:
    Systems:
    SRM 5.0 (Classic implementation scenario)
    ECC 6.0
    SRM-MDM 2.0
    PI 2005
    Material master is maintained in R/3 and the materials are replicated to SRM. From SRM we replicate all materials to the catalog repository in SRM-MDM.
    As the material master in R/3 is vendor independent, the materials replicated to SRM also have no vendor attached. For the first initial material replication from SRM to the catalog SRM-MDM this also means that the products in the main table of the repository, u2018catalog positionsu2019, will not have a vendor or vendor number attached (i.e. no reference to a source of supply).
    To assign a source of supply in the repository to a product (record) we will use info records which are replicated from R/3 to SRM-MDM. The mapping for this in the Import Manager can only be based on the product number. As this is the only unique value available which can map a info record to a already existing (but vendor less) ptoduct item in the catalog.
    As long as every item in the repository has only one unique info record, meaning one source of supply with a specific price, there is no issue in the above scenario. Based on the product-id, the info record data will be matched with the material item in the catalog.
    The issue for me arises when multiple info records exists for the same material. The info records can heave different vendors and different prices. All possible vendors should be available in the catalog for the same material (at least this is the requirement ).
    At this point the product-id will no longer be an unique value. Importing the info records will cause problems, as only one material record is available in the repository for the specific product-id (remember that when doing a initial replication of the material master to the catalog, no vendor data is replicated).
    Does anyone had this issue before, and knows a solution? Is it for example possible during the import of the info records in the Import manager, to duplicate material records in the destination data, based on the number of info records available in the source data for the same product-id. Or is there an other solution that I am missing?
    Your help would be appreciated!
    Regards,
    Skander

    Hi Shai & Ravi,
    Thanks for your answers. The MDM version which we are using is 5.5 - currently on SP6
    @ Shai: you are right; the standard SRM-MDM 2.0 catalog repository has a qualified lookup table u2018priceu2019, in which itu2019s possible to store the info record data. The standard fields in this sub-table are: Purchase Org, Amount, Currency Lower B, PIR-ID, price based quantity and Price based quantity UoM.
    I added some extra fields (non qualified), to accompany the remaining info record data (product no. u2013 vendor id  u2013 product category)  which is exported/imported, via the standard extraction program in R/3: Tcode MECCM
    I tried the solution Ravi proposed. This scenario works fine when, for example you want to maintain multiple info records for one specific material record in the main table (all info records related to the same source of supply, i.e. vendor). But as I described, the info records we import for one product can have different vendors. 
    The source of supply (vendor) in the shopping cart of SRM is determined via the u2018supplieru2019 field in the main repository table (which is in itself a flat lookup table ). What happens now is that all related info records are added to the u2018price informationu2019 field of the specific product record in the main table. Thus info records which have different suppliers are attached to a record in the main table which will have one specific supplier in the u2018supplieru2019 field. So from my point of view this will not work.
    I am still stuck with the situation that the material master import will only import one record for every distinct product, which can have multiple info records. The info records can/will have different vendors. As the supplier field in the main table determines the source of supply in the shopping cartu2026. Iu2019am seeking for a solution which will duplicate the material records in the main table, based on the amount of imported info records for that specific material record, that have distinct vendors.
    Shai, if you have some useful info on how you accomplished this requirement on a previous version of SRM-MDM, it would be greatly appreciated if you can share it..
    Thx.
    Skander

Maybe you are looking for

  • I can sign in to AppleSupport on my iMac, but today I cannot sign in via iPad

    I have been using both iMac and iPad to access Apple Support... but today I couldn't sign in with either. I finally changed password and now I can sign in using my iMac, but when I try to sign in with iPad, I get message "we do not recognize an accou

  • Delivery date should be equal to basline date

    Hi, I have created PO on 2nd and delivery taken place on 5th , IR is taken place on 7th.  Right now i want my baseline date in inoice is should be 5th as delivery date.  please help me in this.

  • Add user to multiple mailman lists at once

    I have multiple mailman lists at my organization that employees need to be added to (when hired) or removed from (when terminated). Is there a terminal command or some other way to add and/or remove one or more addresses to multiple Mailman list at o

  • HP Deskjet 3545 shows "Incompatible cartridge " on the FIRST itself

     I got a Printer - Hp Deskjet 3545 here in Chennai to be used in my home, nearby Erode. I chose hp since, they have got good reputation and they promised onsite issue identification and solution. But on the first day, after carrying it home, installi

  • My iWeb Blog entries are not showing on MobileMe. Help!

    When I click on the link from the Blog Summaries to one one my Blog Entries I get a 'Not Found' page - all published to MobileMe with the latest iWeb. These llinks have always worked before. The problem has been apparent for two days now. What can or