Update MDM Import Map

Hello...
I am a PI consultant who inherited MDM recently.
MDM 5.5, SP06
My issue is that I have an existing map that works fine, but the source schema is changing to add a few new fields.  I need to map the new fields to my existing catalog repository.
I had to import the revised schema under a unique name (v2 suffix).  Then I assumed I could just change the source schema in my existing map, but that does not look possible.  What is the best way to make such a change?  I am hoping to at least copy the current mapping as nothing is changing there...just adding a few new mappings.
Thanks!
Keith
Edited by: Keith Wendel on Jun 4, 2009 10:30 AM

HI Keith
Are you talking of syndication maps?
In import maps we never put the schema. Just connect to the source file and open your old map. on top of this you can do the mappings for the delta fields and save the map with a new name.
thanks
Ravi

Similar Messages

  • 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

  • Map including spliting operation dosen't work in MDM Import Server

    Hi All,
    I met a problem with MDM Import Server when using a map file with spliting operation in it, although I can use it in MDM import manager to load data successfully. The error in log file is like this:
    Record Matching...
    Importing Lookup...
    One or more attribute values are invalid.
    One or more attribute values are invalid.
    One or more attribute values are invalid.
    One or more attribute values are invalid.
    Import Failed!
    The spliting in my map is: I split field "Category" into category1 and category2 with space " ". e.g. value "Trousers M" is splitted into "Trousers" and "M"  . Then I map category1 to category and category2 to size.
    I tried to delete this spliting and just map "Category" to "Category" then it works well for Import Server.
    Is it the bug of MDM import server? can anyone give me a explaination?
    Thanks! Bin

    Under Configuration Options of the Import Manager,
    check the values for
    <b>Default Batch Handling</b>
    AutoMap Unmapped Values = Yes
    Unmapped value Handling = Add/Ignore/Fail.
    Set the values according to your needs.
    Make sure that the data source is updatable as well.

  • Value Exceptions - Import Map Update

    Hello MDM Gurus,
    We have the requirement to update the existing import map by unmapping two of the fields that we no longer required.
    When we try unmapping the required fields and save as another map name, export, reimporting it and overwriting the existing map with the same name. But the problem is we are loosing all value mappings. we are facing issue getting loads of value exceptions as all value mappings are gone.
    Please we need experts advices to resolve this since we no longer need that two fields getting imported in to the repository.
    We need a solution to unmap that two fields and keep all existing value mappings.
    Save Update not works for filed mappings, it only works for value mappings.
    Thank you very much in advance for the suggestions and inputs.
    Example :
    Field1 and Field2 Unmapped, We saved the Map by Save -> we are loosing all value exceptions ( As it stores only present config)
    Field1 and Field2 Unmapped, We saved the Map by Save Update -> When reimport the map again, we are seeing this field1 and field2 still mapped.
    Field1 and Field2 Unmapped, We saved the map by Save As -> Still it does like First Scenario.
    Please Advice.

    Hi Smartsoft,
    Just try this below procedure and revert with result.
    1. Open the existing map.
    2. Remove all the fields from matching field under Match Records tab.
    3. Now unmap these two not required fields under Map Field/Value tab.
    4. Afterwards, set again all the matching fields like earlier under Match records tab. Now make sure that under your Import Status tab Action Item: Ready to Import. Once it is done.
    5. Now try with Save As option as a new map in order you have had existing correct map as a reference for future.
    If it work properly then you can overwrite this new map name with existing map. Kindly revert.
    Regards,
    Mandeep Saini

  • R/3 u2013 XI u2013 MDM integration scenario - Standard import Maps problem

    Hi Data Masters,
    We are working on R/3 u2013 XI u2013 MDM integration scenario for Vendor Object. We have extracted main table Data using u201CMDM_CLNT_EXTRu201D program. Now while importing the data in MDM we want to use u201CStandard business content i.e. Standard Import Maps (Name u2013 cremdm - 03 u201D but this maps are not mapping all the fields. So do we need to extend this maps..??
    OK. Second, To create own maps we are facing following problems,
    1)     In source section many fields are reflecting twice means in two segments i.e. LFA1 and ADRMAS like Name, City, Street, country etcu2026 whereas in Target section we have one field for the same so how to maps this fields.
    2)     In source, There are few fields like ADRNR which have values but in target we donot have any fields to map for the same, so how to handle thisu2026
    Helpful answers will be rewarded,
    Cheers
    RC

    closed

  • What is meant by criteria of Updateability in MDM Import manager

    Hi,
    What is meant by criteria of Updateability in MDM Import manager? i read some information, but i could understand, it says original data source be  updateble. what is meant by Original data source.?
    what is the use of option "Read-only"  in Import manager logon screen.
    Thanks

    Hello Ankam,
    You can check the Read-only option to prevent MDM from updating your data source.
    Kindly see the below information on "DATA SOURCE UPDATES"
    DATA SOURCE UPDATES
    Some MDM Import Manager operations require that the original data source be updateable, thereby allowing new fields and/or entire new tables u2013 and the corresponding data values for each record u2013 to be automatically added to the data source before further processing.
    Other operations simply create virtual fields in the MDM Import Manageru2019s workspace, although if the data source happens to be updateable, some of these operations instead add the new fields to the original data source as well.
    NOTE ►► Updating the data source when possible allows you to
    perform additional operations on the new fields as if they were part of
    the original source data, and also use them as record matching fields.
    NOTE ►► Fields that are added only if the data source is updateable
    can be deleted automatically by the MDM Import Manager when you
    exit or switch data sources based on the setting of the Delete Created
    Fields on Exit configuration option.
    Updateable Data Sources
    Whether or not a data source is updateable depends upon the following:
    u2022 Source type. The source Type must permit the MDM Import Manager to update its schema and insert the additional fields of data; some supported types are updateable and some are not.
    u2022 Media. The media on which the data source resides must itself be updateable. If the media on which the data source resides is readonly, such as a CD-ROM, the data source cannot be updated.
    u2022 Permissions. You must have the proper file system permissions to update the file, or the proper DBMS permissions to update the schema of the database.
    u2022 Read-only option. You cannot have checked the Read-Only option, which prevents MDM from updating the data source even if the other conditions would otherwise permit it.
    NOTE ►► The Read-Only option is: (1) enabled for source types that
    can be updated (Access, Oracle, SQL Server, and XML); (2) disabled
    and unchecked for those that use Access as an updateable staging
    area (Delimited Text and Fixed Text); and (3) disabled and checked for
    those that cannot be updated (Excel and ODBC).
    NOTE ►► When the data source is SQL Server, the table names in
    the database must not contain spaces; otherwise any operation that
    would update the data source will fail.
    Hope this helps.
    Regards,
    Vikas

  • Qualified Updated Selections not Saved in Import Map

    Hello,
    I create a new Import Map and Set the Qualified Update setting on a qualified table.  When I reopen the map, the Qualified Update option is saved but not the selections for the qualified update.  The defaults are saved:  all fields are selected as matching qualifers.  Create = blank, Existing = blank.
    I have tried to recreate a new map and get the same results.  Any ideas?
    thanks
    Tammi

    Hi Tammi,
    could you pls elaborate on  the exact issue a bit more?
    Reg,'
    Bis

  • MDM Import Manager - remove multiple values from a multi valued fiedl

    Hi,
    We have this multi-valued field and we would like to clean the values from it.
    How can we do this using MDM Import Manager?
    Example:
    Article A
    Field XPTO has values Z, T and P.
    We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?
    Thanks and regards,
    Maria

    *We have this multi-valued field and we would like to clean the values from it.
    How can we do this using MDM Import Manager?
    Example:
    Article A
    Field XPTO has values Z, T and P.
    We want this field XPTO with no values. How can we do a mass actualization to clean the field for some articles?*
    Hi Maria,
    There can be multiple ways to achieve this -
    1.After doing field mapping for XPTO you can set conversion filter for each of the values.
    2.Value map with NULL.
    3.Trigger a Workflow on import/record add,run assignment and make that field NULL.
    4.Run mass update for conditional assignment based on that value of XPTO.
    There can be more ways,whichever suits you best you can go ahead with that.
    Hope it helped
    Regards,
    Ravi

  • Source Data for Import Map

    I inherited some MDM work from a consultant who rolled off our SRM project.  He did not leave any source input files to use when making changes to maps, and I read in the SAP MDM Guides that you should always revert back to your original source file when making map changes so you don't lose any mappings (if the newer source file does not contain every segment that the original did, etc).
    Am I off base?  Is there a safe way to make map changes without having the original source file?
    Thank you in advance,
    Keith

    Hi Keith,
    You are absolutely right. This is a common problem which is being faced while subsequent loads into MDM. The problem is that generally the Map is created in Import manager and then if more values come in for value mapping or more fields are mapped due to a new business requirement, then the map sometimes throws a problem of Map being out of date.
    The solution that we came out for this was a creation of Value mapping template ( you can also include the field mapping). This would have the complete list of fields and values in one map. Also if some new value is getting added, then firstly add in the template and then Map it in the original Map.
    Now in your case, you can either go and create a Template or else, use the SAVE UPDATE option present in Import Manager everytime you face an exception via MDIS. SAVE UPDATE will help you update the additional mapping onto the original map and then if a similar file comes in again, it will processed successfully via MDIS.
    You can refer to my Article on this:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
    Hope it helps.
    Thanks and Regards
    Nitin Jain

  • Creation of Import Map for Business Partners

    Hello Guru's,
    Can anyone guide me how to create import maps for Business Partners please , we use Text files.
    Thanks in advance
    Regards
    Srihari

    Hi srihari ,
    Kindly refer to the below links for some further help in this area:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_mdm/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31303335373733%7d
    /people/satyajit.chakraborty/blog/2009/01/15/central-mdm-business-partner-creation-scenario-with-galaxy-bpm--part-i
    /people/satyajit.chakraborty/blog/2009/01/16/central-mdm-business-partner-creation-scenario-with-galaxy-bpm--part-ii
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Import map issue one record at a time

    Hello Experts,
    I built an import map to run it manually with import manager, but when I click on Ready to Import, the import manager is doing one record at a time.  I have to go back to the match tab and refresh in order to import the rest. 
    Any idea where to setup a setting to import all records at once?
    Thank you very much for your help,
    Claudia Hardeman

    Hi Claudia,
    Please check if your matching criteria results in fewer records,what is the matching criteria you are setting?
    Do you see a total of 300 under "Create" Match Action?
    No of records to be imported is governed by Match action which tell the MDS which are distinct records,Match Action tells MDS what is to be done with this number of records which have this Match type.
    Please check if you have "SKIP" as match action,if yes use a appropriate action for match type.
    Do a "Save Update" of the map.
    Please revert with results.
    Thanks,
    Ravi

  • Identifing duplicate master data records using the MDM Import Manager

    hi all
    I read the Topis "How to identify duplicate master data records using the MDM Import Manager</b>"
    i tried to create import maps and to set rules. but when i import them it creates the new vendor records for each rule with rest of the fields blank.
    when i import vendor data all the three fields i.e Match rate , match type and match group are blank.
    My Question is :
    I am getting vendor data from SAP R/3.
    In which source (in lookup xml file or data xml file) do i have to include these above three fields and how all the rules will be reflected in repository?

    Hi Sheetal
      Here we go when do you Import any data (vendor master) please follow the following steps;
    1. First of all apply the map to the source data
    2. In the Match Record tab there are 3 possiblities
       a.[Remote Key] : Checks the current source rec with
         repository along with all the fields - This is
         default
       b.Remove [Remote key] - by double click the same; and
         choose any single fields like Vendor Number or
         name - Then the current record will be matched
         with the repository based on the field.
       c.Instead of single field you can choose combination
         also.
    3. Based on the Match results, match class will be set
       automatically;
       a. None
       b. Single
       c. Multiple
    4. Then Match Type
        a.Exact-All the individual value matches are Equal.
        b.Partial-At least one value match is Equal and at least one Undefined; no value matches are Not Equal.
        c.Conflict-At least one value match is Equal and at least one value match is Not Equal.
    5. then chek the Import status and Execute the import.
    Hope this helps you.
    cheers
    Alexander
    Note: Pls dont forget reward points.

  • MDM Import Manager Batch

    Hi everyone,
    We are using the MDM Import Manager Batch to import data automatically. Can we write in our ImportBatch.ini the file name with * at the end : CREMDM.CREMDM04*.xml
    because the file name comes with time stamp (CREMDM.CREMDM0420061129-103959-602.xml)
    [Source]
    Type=XML Schema
    XML Schema=CREMDM04
    File name= \...\... CREMDM.CREMDM04*.xml
    DSN=
    DBMS Server=
    Database=
    User=admin
    In advance thanks,
    Aklilu

    Hi Aklilu,
    the names of the XML files don't matter. MDIS tries to process everthing that is put into the ready folder. The ready folder is processed in a "first comes, first served" way. So there's no need to change the names. Is the time stamp in the file name really a problem? If yes, why?
    > We are trying to parameter the mdis.ini and until now it does not work.
    Could you specify this? In addition, I've got a few hints:
    MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.
    Here's a sample for the MDIS.ini:
    [GLOBAL]
    Version=5540
    Server=WDFD00146633A
    Interval=30
    Automap Unmapped Value=True
    Unmapped Value Handling=Add
    Always Use Unmapped Value Handling=False
    VXR_MAX=25000
    Verbose=0xFFFF
    -- Verbose OFF:     0x0000
    -- Verbose ON:      0xFFFF
    -- FI  Verbose:     0x0001
    -- XML Verbose:     0x0002
    -- MAP Verbose:     0x0004
    -- THRD Verbose:    0x0008
    -- PARSER Verbose:  0x0010
    -- STRUCTX Verbose: 0x0020
    -- VALUEX Verbose:  0x0040
    -- IMPORTX Verbose: 0x0080
    String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
    Log Dir=Logs
    SLD Registration=False
    [SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
    Login=Admin
    Password=
    Chunk Size=50000
    No. Of Chunks Proccessed In Parallel=5
    Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.
    Kind regards
    Michael

  • How to save the setting in MDM import manager?

    How to save the setting in MDM import manager? After I configure all things in MDM import manager, I try to save the setting, let's say, saved map name is " Test002", and then I export this map into desktop. After that, I logon Import manager again, and import this map file, system show me the same thing that I have to configure it again, because nothing was changed, what I configured before, were all disappeared.

    Hi Alfred ,
    are You not saving this map in Import Manager ? Import Manager itslef saves the map and remember it . Exporting map is only for backup .
    Pls make changes and save the map . Exit and relogin . then see the map . It should be there . Pls let us know the result .
    - An

  • Differences between various source files in mdm import manager

    Hi,
    Can anyone tell me the differences between the source files(access,xml,xml schema,excel) available in mdm import manager?
    Thanks and regards,
    Rithesh
    Edited by: rithesh_shet on Mar 30, 2010 1:04 PM

    Hi Ritesh,
    MDM Import Manager provides flexibility to Import Data from different types of Sources into MDM.
    You can import data into MDM from below mentioned sources using Import Manager:
    1. From Files (Access, Delimited Text, Excel, Fixed Text, XML and XML Schema)
    2. Directly from Data base source (SQL server and oracle)
    As mentioned by Mandeep, XML Schema is something which you define in MDM console in advance. and then later select the Data source XML file and XML schema from drop down list (it will show all schema defined in console ) to validate XML source file against the XML schema.
    For automated Import, Ports are used. Ports are nothing but a logical point of contact with other systems i.e. other systems or middleware will drop file on the port for authomatic import and MDM import server will scan the port directory and if file is present then will import data automatically from file into MDM using a predefine Import Map. (this map needs to be defined manually in import manager and then assigned to port using console).
    Please check page no 45 of import manager reference guide for more details about various source properties of Import Manager.  (*link for import manager reference guide is already provided on the earlier post)
    Also check, page no 53 to 64 for how to import process. Kindly revert if you have any query.
    Regards,
    Shiv

Maybe you are looking for