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

Similar Messages

  • Regarding MDM Import and Syndication Server

    Hi,
    I have earlier worked in MDM Import Server.
    Today, I successfully did MDM Syndication by
    MDM Syndicator.
    Now, the point is I need to do Import and Syndication
    by MDM Import Server and MDM Syndication Server.
    The MDM Version is 5.5.
    Now, the point is under my installed directory:
    F:\MDM SERVER\Server
    in mds.ini file:
    I need to give the following path:
    Distribution Root Dir=F:\MDMSER~1\Server\Distributions\
    I think other than these I don't have to do any configuration
    in mdis.ini or mdss.ini.
    Also, I have already inbound and outbound ports made and linked
    to inbound and outbound maps.
    Is there any more configuration needed?
    Regards
    Neha Singh

    Hi Neha,
    There are many configuration needed to complete the Automatic import and syndication using MDIS and MDSS.
    Please go through the link below for the same:
    Master Data Management Import Server and Master Data Management Syndication Server - Webinar Powerpoint
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
    This will give you the complete steps to perform the same.
    Hope it helps.
    Thanks and Regards
    Nitin Jain

  • Import and Syndication

    Hi all
    Can anyone tell me what the issues (if any) might be is we run and import process and syndication process simultaneously, provided of course that the  data selection  for syndication is not the data being imported

    It has been our experience that one process will hold up the other.  For example, we have been doing many imports and syndications as part of our set up and have done fairly large imports as well. During these imports, my syndicator will show at the bottom "please wait while the server performs an operation on behalf of 'USER' on 'MACHINE'". Once that process is completed, it will perform the next process in the queue.  Hope this helps.
    Don

  • How do i update & test import maps and syndication maps?

    HI,
    Can anyone guide me/ let me know the steps - how do i update & test import maps & syndication maps during upgrade in development system>
    Regards,
    Harmony

    Hello Harmony
    Different service packs SAP MDM 7.1 supprot the same Syndication and Import map format.
    For Import map is updating you can use Import manager
    For syndication map is updating - Syndicator
    If your syndication and import map have been saved into repository just archive repository from your source landscape and unarchive it in destination.
    If your syndication and import map haven't been saved  in repository.
    Exporting your maps to xml(syndication maps from syndicator and import maps from Import Manager) before migration and importing it to new repository.
    According updating(modification) repository structure:
    For Import map is updating you can use Import manager
    For syndication map is updating - Syndicator
    Another way(very exotic) - make changes in exported xml maps.
    That's all
    Regards
    Kanstantsin Chernichenka

  • Scheduling Imports and Syndication

    Hello Experts,
    Is it possible to schedule Importing?
    If so can we do it Thrice a day in a stipulated time?
    weekly?
    monthly?
    I am sure that syndication can be scheduled by placing it in Work flow(on record import, update, delete)
    And by making the outbound port hourly, daily, weekly.
    Can we schedule Syndication Monthly?
    Kind Regards
    Eva

    Hi Eva,
    How can we include an Import proces in MDM wf!!!
    In Data Manager, Once you have done with your design of mdm workflow, set workflow property Trigger Action = Record Import and set Autolaunch = immediate. But as you are looking for Scheduling import, I am not sure as i have not tried it so I would suggest just check and try with Autolaunch =  Threshold and  set Max Records = 1000 & Max Time = 3 days if it gives you desired result.
    In import Manager, import map for which you want to set it. Go to configuration options--> set the property Checkout/Workflow = Workflow name from the drop down which you created in data manager and then save the map.  So whenever record import for this map it will go through this mdm workflow.
    PI/XI is also a good approach to control the import timing.
    As you are looking for Import Scheduling thrice a day.
    I feel that as soon as files comes to your ready folder port, files get imported to MDM if your Import Server is running. So in this case you can create another folder say initial backup import where you should contain import files and with the help of scripting language/scheduler, you should move files from this folder to ready folder after every three days.
    Can we schedule Syndication Monthly?
    You can make use of JAVA APIs and run a batch job to schedule it monthly.
    Please refer these below threads for more details:
    1. Java API : Syndication
    2. Call a Java API via Unix Script
    Regards,
    Mandeep Saini

  • Setup interval on Import and Syndication server in 7.1

    Hello Experts:
    I am upgrading MDM from 5.5 to 7.1; I am having issues with Import Server picking up files from Ready folder, and Syndication Server creating the files on Ready Folder. 
    1. I checked Console, and both ports, Inbound and Outbound, are setup as Automatic.
    2. I restarted both servers
    The files are still on the ready folder for Import Server, and Syndication is not creating the file.
    1. Do you know what else can I check to make this process automatic?
    2. Do you know where, in 7.1, can I check the interval? I used to check it on the mdis.ini file, but I cannot find it in 7.1.
    Thank you for your help,
    Claudia Hardeman

    Hi claudia,
    check the below points:
    1) Manually you can import and symdicate those files through import manager and syndicate manager its works fine, then PI not picked those files from ready folder, check the communication channel of receiver and sender systems.
    2) files having some special characters (like ", ' etc.) MDM is not supported to special characters.
    3)check the MDM server running and repository loaded or not.
    Regards,
    Bhupal.

  • Syndication Map Change Track

    Hi Experts,
    Somebody have changed the map in MDM Syndicator and created huge problem in PI.
    can we track the User Name who last changed the map?
    Thanks,
    Sekhar

    Hi Sekhar,
    I can understand your pain. But unfortunately it is not possible with Standard MDM Components. Using Database management tool Give a try and check the MDM repository database tables and see if you can get something there. I am not very positive about it.
    - Shiv

  • Itunes 11 hangs when importing and try to change Screen

    Hi
    When I try to import cd's into itunes it impors no drama untill I try to change to browse my music library.
    When I try to change screens to browse by Artist while the cd is importing itunes just hangs and I have to force quit to exit.
    Any clues or suggestions.
    Cheers
    Tony

    I've tried:
    reinstalling iTunes (many times)
    creating a new library
    reimporting my files in small batches
    turning off organize library/copy files into iTunes library
    uninstalling Quicktime (and then reinstalling Quicktime)
    turning off start-up items
    Any thoughts? Thanks.

  • Update of XML syndication map when XSD is changed

    All,
    So we recently upgraded to MDM 7.1 SP 06 and found a new feature which we were waiting for quiet some time. Thought i'll share with the community as well.
    Update of XML syndication map when XSD is changed in Console
    In earlier SP's of MDM, if we had to update an XML syndication map, we had to upload the new XSD in Console, go to syndicator and basically re-create the whole map. there was no way for syndicator to preserve the old mapping.
    Well with this new feature, the old mapping is preserved, we only need to re-map the new fields.
    The process is as below:
    1. Upload the new XSD in Console.
    2. Go to syndicator and open the syndication map which you want to update(File->Open).
    3. Click File -> Update XML Schema. (this is the new option)
    4. It will give a pop-up, select the new schema you have uploaded in console and hit OK.
    5. You will get a prompt saying that syndication map is being changed, hit OK.
    6. Now you will see the new XSD in syndicator, the older fields are still mapped, you only need to map the new fields.
    It a nice feature which will definitely save lot of time. Thanks SAP
    Regards
    Aamir

    If this post answered your question or helped, please mark it as such.
    This works.
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
      <mx:Script>
        <![CDATA[
          import mx.events.DataGridEvent;
          import mx.collections.ArrayCollection;
          [Bindable] private var ac:ArrayCollection = new ArrayCollection([
            {bgColor: "0xFF0000", num: 100, name: "Test1"},
            {bgColor: "0xFF0000", num: 200, name: "Test2"},
            {bgColor: "0xFF0000", num: 300, name: "Test3"},
          private function changeBK(evt:DataGridEvent):void{
            var row:uint = evt.rowIndex;
            var data:Object = ac.getItemAt(row);
            data.bgColor = "0x00FF00";
        ]]>
      </mx:Script>
      <mx:DataGrid id="dg" dataProvider="{ac}" itemEditEnd="changeBK(event);"
        editable="true">
        <mx:columns>
          <mx:DataGridColumn dataField="num">
            <mx:itemRenderer>
              <mx:Component>
                <mx:TextArea backgroundColor="{data.bgColor}" text="{data.num}"/>
              </mx:Component>
            </mx:itemRenderer>
          </mx:DataGridColumn>
          <mx:DataGridColumn dataField="name"/>
        </mx:columns>   
      </mx:DataGrid>
    </mx:Application>

  • Redo the syndication map if the Repository schema changes?

    Hi ,
    We have changed the repository structure after creating the syndication map which is based on the repository schema.Now when I load the syndication map with the updated schema ,i am not seeing the newly added fields on the destination items,so we loaded the destination properties with new schema again but the map of all the fields are no more available which leaves us to redo the map again.Is there anyway that the destination is updated with new fields without redoing the map again.
    Thanks

    Hi Aravind,
    unfortunately there is no way to solve this issue but rebuilding the map. The reason is the way syndciation maps are stored in MDM 5.5. This is subject to change (and improve a lot!) in MDM 7.1. But in 5.5 you'll have to rebuild the syndication map completely if you change the repository schema, respectively the XSD file you use as a basis for XML distribution.
    Best regards
    Michael

  • Steps to configure Import Server and Syndication server

    Hi,
       Can some one help me to work on Import Server and Syndication server. I know there are few forums availabe on this topic but they are not very basic. I need to know the basic step(From installation to automatic transfer of data.) to work on Import <b>Serve</b>r and Syndication <b>Server</b>.
    Regards,
    Ron
    Message was edited by:
            Ron

    Hi Ron,
    The MDM Import Server is a background process (service), which separates the core processing of master data imports from the front-end processing. MDM Import Server allows you to load master data records periodically from various
    client systems to various MDM Servers and repositories based on the port concept.
    Once the data is delivered by SAP XI on a specific port, it will automatically get picked within a configurable time interval and queued up for import processing.
    MDM Import Server creates log files of the entire load process, which are stored
    in the port folder Log and can be displayed in MDM Console.
    If an error occurs in the automated import, the MDM Import Server stops and
    drops the XML in the Exception folder of the port. You can import the XML
    interactively using the MDM Import Manager and correct the error (for example
    complete the import map).
    Hope this might help....
    thanks
    Alexander
    P.S. Kindly reward the points, if found helpful.

  • Is it possible to import and display/plot (Google Earth) KML files as overlays in Mac OS 10.9 Maps application?

    Is it possible to import and display/plot (Google Earth) KVM files as overlays in Mac OS 10.9 Maps application?
    Here is the particular application: (note I haven't gotten the code to compile yet -- seems to be several differently named environment variables in Mac unix than in Linux that are making the compile blow up -- but that's another issue) there is a freeware application that can do radio path loss prediction and plot path loss contours on a map. It has an option to output the data as KML files which can be imported into Google Earth, in order to display the path loss contours on Google Earth maps. I guess you could liken it to displaying overlays of GIS-like data in Google Earth. I would like to know if there is a mechanism to facilitate importing KML data files to overlay (preferably in a translucent fasion so that you could see the underlying map) onto Mac OS 10.9 Maps?

    varjak paw wrote:
    They're also known to patent things they never release. So while it indicates that they're investigating such things, a patent application is no guarantee that anything will ever come of it, much less be immanent. And that application was filed in 2012 and is really for something rather different.
    Regards.
    As I stated, "possibly."
    While the commerce side of it has little to do with the KML files, per se, the API for the layer data should allow for any type of overlay.
    Also, the patent was filed Dec 19, 2013. There was a related patent filed in 2012. Not sure what it is about.

  • I've been using samsung for a long time and I just changed into an iPhone 5s and the most important thing I need is my calendar appointments , but in the notification center it doesn't show my events for tomorrow , will there be an updated or this soon?

    I've been using samsung for a long time and I just changed into an iPhone 5s and the most important thing I need is my calendar appointments , but in the notification center it doesn't show my events for tomorrow and it doesn't even show more than 1 event  , will there be an updated or this soon? Or should I just shift back to samsung?????

    Go to settings/notification centre and make sure today vie and calendar day view are both on

  • Autotype support for xsd import and xsd include statement

    Hi,
    I am using Weblogic 7.0.1. While using autotype for a Schema, I get the error unable to resolve element ref: "qb:WireCenterCLLI. This element exists in an xsd imported in the main XSD which in turn includes a few XSD's. I saw few posts which indicated there were issues with autotype recognising xsd:import and xsd:include statements. Were these issues fixed? If so, what SP were they fixed in?
    My XSD:
    <?xml version = "1.0" encoding = "UTF-8"?>
    <xsd:schema xmlns = "http://www.qwest.com/XMLSchema"
    targetNamespace = "http://www.qwest.com/XMLSchema"
    xmlns:qb = "http://www.qwest.com/XMLSchema/BIM"
    xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
    elementFormDefault = "qualified">
    <xsd:import namespace = "http://www.qwest.com/XMLSchema/BIM" schemaLocation = "/u/skarani/sia_code/xsd/ProjectSpecific/SIA/BIM/AddressValidationInclude_v01_00.xsd"/>
    <xsd:include schemaLocation = "/u/skarani/sia_code/xsd/ProjectSpecific/SIA/Common/AddressValidationCommon_v01_00.xsd"/>
    <xsd:include schemaLocation = "/u/skarani/sia_code/xsd/ProjectSpecific/SIA/Common/RequestMessage_v02_01.xsd"/>
    <xsd:element name = "AddressValidationByServiceIdRequest">
    <xsd:complexType>
    <xsd:complexContent>
    <xsd:extension base = "WebServiceRequestT">
    <xsd:sequence>
    <xsd:element name = "InputData" type = "AddressValidationByServiceIdInputDataT">
    </xsd:element>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    </xsd:element>
    <xsd:complexType name = "AddressValidationByServiceIdInputDataT">
    <xsd:sequence>
    <xsd:element ref = "qb:WireCenterCLLI" minOccurs = "0"/>
    <xsd:element ref = "qb:WireCenterPrimaryNPANXX" minOccurs = "0"/>
    <xsd:element ref = "AdministrativeArea" minOccurs = "0"/>
    <xsd:element ref = "qb:PostalCode" minOccurs = "0"/>
    <xsd:element ref = "qb:BTN"/>
    <xsd:element name = "ParsedAddressFlag" type = "xsd:boolean" minOccurs = "0">
    </xsd:element>
    <xsd:element ref = "qb:CCNA" minOccurs = "0"/>
    <xsd:element name = "CompanyCode" type = "xsd:string" minOccurs = "0">
    </xsd:element>
    <xsd:element ref = "AssignedHouseNumberFlag" minOccurs = "0"/>
    <xsd:element ref = "GSGRqmtFlag" minOccurs = "0"/>
    <xsd:element ref = "TNStatus" minOccurs = "0"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Thanks
    Shekhar

    Hmmmm.... No answers!!!
    Has anyone had success using autotype with an xsd having include and import statements???
    Thanks
    Shekhar

  • Syndication mapping when changing XML schema

    I have used a ARTMAS04 XML schema and done mapping in the syndicator and saved the map. Then we are doing changes i SAP R/3 and need to add some extentions in the IDOC and therefor also the XML schema. I then add my new schema with the extentions into the the syndicator, and try to open the mapping. Then the mapping is done using the old schema. This means that if I do a change in an XML schema, I need to to map everything from scratch. Does anyone have a solution to this problem?
    Regards John-Kjell

    Hi John,
    The maps saves not only the mappings but also the destination properties for that particular scenario.
    Hence as soon as you change the destination properties i.e your XML schema, and try to open your old map which is using different XML schema your changes will be lost and you will end up with using old XML schema only.
    As far as i know, to handle this situation you have to do all the mappings again.
    Hope this helps.
    Regards,
    Pooja

Maybe you are looking for