Import Manager MDM 3.0 Updating old Maps

Dear MDM Catalog gurus,
After having upgraded from MDM 2.0 to MDM 3.0 the maps have to be
updated in Import Manager.
1.
When trying to update MDM import Maps in the new "SAP Import Manager" messages
like
- "There are multiple roots for the XML Schema. Please select the correct one" or
- "There are multiple path for Table "ARTICLE". Please select the correct one"
come up.
What exactly do we have to do? What is the root of an XML-Schema? Can
I find that in Console or by looking into "old" Maps with the old Import Manager?
I saved the old Schema files from Console before upgrading to MDM 3.0.
Now when I open this old XML-Schema file with an editor, where can I
find e.g. the "old" root node.
2.
What happens if I say "No" I don't want to update the old Import Maps
when starting Import Manager.
Then all old Maps are gone and I have to recreate them. But does this
have an effect on the further upgrading process to MDM 3.0? Will the
old repositories work under MDM 3.0 after having sais NO?
Any idea?
Thanks a lot for your help in advance.
Best regards,
Henning

Hi there,
thanks for that hints, but this does not really help.
I already read a lot of sap links, but don't really get a solution where I can find information about where to find the rood node (or what it is) or information to former paths.
Is there perhaps anybody how also made an upgrade from MDM Catalog 2.0 to 3.0 with similar experience?
Thanks in advance,
best regards,
Henning

Similar Messages

Map cannot be loaded in import manager | MDM

Hi ,
I am trying to upload some data in customer repository (I am on MDM 5.5 SP05) . I have a few XML files (IDOCS) from customer master in an ECC system ,which I am providing as a source for the import manager . In the source preview I can see the following tables
- DEBMAS06
- E1KNVIM
- E1KNVPM
Now when I try to open the import map 00_DEBMDM06_R3.map (standard map provided by SAP) it gives me an error message "the map cannot be loaded because table E1KNA1M is not a source" .
What do I need to get this file uploaded to the import manager ?
Regards
Deepak Singh

Hi Maheshwari/Harrison ,
I tried giving the type as XML schema as you guys suggested but now the the import manager won't open at all and I get the following error " The element DEBMAS06 is used but not declared in the DTD/Schema " .
In the console inside the customer repository > Admin > XML schemas i have made sure that the schema name DEBMDM06 points to DEBMDM.DEBMDM06.xsd that is provided in the business content with the customer repository . Infact for all the schemas( lookup tables , bank check tables , customer check tables ) i have made sure they point to the right XSD's provided in the business content for the customer repository .
Now what do you guys think is the problem ?
Regards
Deepak Singh

Import manager save Vs Save & Update

Hi all,
I am getting this message when I use Import Server .
515 2008/09/03 11:42:30.091 Some portions of this import map are out of date.
Solution: Please, Launch the Import Manager GUI, preferably using the original source file that the map was generated for, otherwise the same source file and Save Update [File->Save Update] the map.
And when I do the action suggested, it does solve the problem.
My question here is why is this even happening, i use Import manager for the same data file, I am using Save rather than save & Update. So is that causing this problem??
Thanks,
really appreciate any thoughts.
Sudhir

Hi Sudhir,
This problem usually occurs because the XML source that gives the structural error when importing, contains an element which had not been part of the original XML that was used for generation of the original map. Since this element is not defined as mandatory in the XSD the Import Manager could open it with no schema conflict. But since the source file contains a new element the Save Update option must be applied to add this new element to the map definition.
There are two ways to overcome this issue:
1. To create an input file which contains all the elements and use this to create the map (you do not need to run the actual import, it is sufficient just to save the map after mapping all the required fields.
2. Open the Import Manager GUI and choose a number of files together (the more files you open, the better your map will be).Map all the required fields and values and then use the "Save Update" option to save your changes. Open Console and update the same map for the ports also. Doing this it wont ask for save update for the this element again
You should now be able to import all of the files as well as other files that do not have new unmapped elements. The XML files are valid against the schema and the Server is looking for the mapping not for correctness of the schema.
I hope I am able to help you
Thanks & Regards
Dilmit Chadha

Concatenation in Import manager(MDM)

Hi ALL ,
I want to concat or merge my 3 fields of my Qualified table during Import manager and then map it to one field in my destination table .Please help me in that .
Ex.Name /Country/City into a destination field Info
Thanks and Regards.
Ankit Jain

Hi ankit,
The requirement that you have to merge three fields together in the Import manager can be done by methods.
1)Compound field creation
2)Partioning
1)Compound field:
A compound field will only be created if you map all the exsisting fields in the source side with the fields in the destination side.
For qualified table mapping this is the requirement that if you want to create a compound field you must make sure that all the fields are mapped in the source side.Then when you right click on the non qualifier it will create a compound field and automatically map it with the required field.
2)Partitioning:
You can also use partitioning to merge three fields together.
just click the desired field in the source hierarchy and click the partioning button in that dialog box select all the fields that you want to club under one field.
Regards
Simona

Import Manager 'Error 5611520 - Error Saving Key Mapping'

I am using CREDITOR_EXTRACT in R/3 to send Vendor IDoc to XI and use CREMDM04 type. XI generates an XML file that I load into MDM using a client that is set up for Inbound/Outbound. The key mappings have been turned on for the Vendor repository.
In IM, I use the standard map CREMDM04 and the system maps the incoming XML file to the vendor main table. There are few values that I have to map manually - fine. Next, when I click Import, I get a error pop-up message 'Error Saving Key Mapping - Errno 5611520'.
Has anybody experienced this when using all standard content (schemas and maps) for Vendor?
Thanks in advance.

Subbu,
Found another system that has the same versions as you do. This particular error did not appear, but we got some internal IM error. Also, the SAP training demos are on the same versions as mine.
I am using MDC R/3 as the client and the CREMDM04 schema map. Not using MDM inbound ports for now. Just loading XML file generated by XI based on CREMDM04. Do you think that I need to define a Qualified Range for this client in the Console or can it be left blank?
Thanks.

Deleting unwanted Maps in Import Manager

Hello All,
I wanted to the steps to be delete unwanted maps from the import manager.
Regards
Sathya

Hi Sathya.
1. Login to MDM Import manager
2. Provide the necessary information(Repository details, credentials)
3. Provide information like Type,Remote System, File Name etc(You can also give some dummy information since you are going to delete the import maps)
4. Click Finish
5. you are now logged into the Import Manager.
6. Click Open Map icon which is next to the Destingation table drop-down.
7. Select the map which you want to delete.
8. click Delete button, you will be asked for a confirmation
8. Select Yes
9. The map is deleted from the repository.
Note: Make sure the map is not associated to any of the ports.
Best Regards
Bala

Problem in mapping from import manager to Data manager

hi friend's....I got a problem while mapping the data from import manager to Data manager .The problem is the data in import manager (i.e source hierarchy) will map to single filed in data manager ( i.e target hierarchy)..
Help me it will be great full to me
Regards
Yugandhar

Hi Ana,
If you have a hierarchy in this format:
N1            N2                 N3
A              A1                 A11
A              A2                 A21
A              A3                 A31
B              B1                 B11
Then u have to follow these steps for import.
1. Select source file and destination hierarchy table at top of import manager.
2. Go to Partitions tab (Second tab) Just above the tabs, if u click on the plus sign against your source file, you will see N1, N2 and N3. Cick on N1 and in partition tab, add N2 to right side by double clicking on N2.
3. Now add N3 to right side by double clicking on it.
4. Go to field mapping (Third tab). There you will see a field N1(Partition). Map this field to yourhierarchy field on destination side.
5. In value mapping (Below the field mapping), Expand your source hierarchy. Select all (ctrl + A). Click on "Add" button. Select "Add Branch as child" option.
6. Go to Matching tab (Fourth tab). only one field will be there. take ity on the right side. and select the import action as "Create".
7. Go to last tab. Click on import button.
Your hierarchy has been imported. You can check it in data manager (in hierarchy mode).
Hope this solves your problem.
Regards,
Dheeraj.

Accessing Unix folder while selecting source file in Import Manager,GUI

Hi,
I am using MDM 5.5 sp04.I am trying to use MDIS to automat the importing process.
Challenge is to use a map in port which will be used by MDIS.
Our MDM server system is in Unix. How I can select input file residing in unix folders( say ready folder of Material) from IM tool drop down so as to save that map and assign that map in Port.
Is a file can be used from window folder in IM ,save the map and assign it in Inbound port ?
Is there will be an conflict in this case since MDIS will be receiving the file from Ready folder(in unix) but the map of the inbound port will be having the source in different folder in window?
Appreciate your help/suggestion
Reo

Hello:
you shouldn't need to do that under MDIS. The thing is, use the Import Manager on windows to create the mapping file (importing a file also in windows)
When you created the mapping file, assign it to a port. Ports include a specific folder where you need to put the new file to be imported. Please refer to port documentation to find out where this folder is.
The map only has the "mapping structure", and the file will be taken from the port specification
Greetings
Alejandro

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

MDM Maps in Import Manager crashes and does not open

I am having problems with some of my maps in the Import Manager. While working in the Import Manager the maps are fine and I am able to import the data, but once I exit out of Import Manager and try to open the same map, it crashes and closes the application. I am not sure what the issue my be. Could it be the fields I am mapping to are creating a conflict somewhere? Has anyone encountered the same problem. Any insight on this issue would be greatly appreciated. Thanks!

This was happening to me as well. Basically, the data I was submitting was much too large for MDM to handle which resulted in a timeout. To resolve this, I copied my data to temp tables to minimize the number of records I was sending it. After my experience with Import Manager, I think it's safe to say that it was not intended for large data loads. In the future I will be using Import Server and translate my data to XML.

Updated xml schema not reflected in Import Manager and Syndicator

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

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

Partial match for Value Mapping in Import Manager

Hello Experts,
We have a import map which is used to do mass insert of data into the main table. This is done as & when required by the end user.
We have a qualified lookup field which has a flat lookup filed as the Non-Qualifier. This flat lookup field is refering to a Lookup Flat table, which has mulitple dispay fields like Code,Name, Status etc. (14 fields in total) where as only the Code is the unique field.
We have only the unique field in our source file which we use for the import. Since we have only a part of the display fields in the source, the automap functionality in the Value maping section doesn't work. It becomes very tedious for the user to manually map all the values for this field.
Is there any way by which we can convert the source or target values in the import map, so that we can map the values using the Automap feature?
Your help & suggestion for alternate approach is highly appreciated.
Thanks in advance.
Regards,
Uday
P.S. We are using SAP MDM 5.5 SP6.

Hi Uday,
No need to enable remote key mapping for QLT. Please execute the below steps(stated with an example) -
1. Among all the fields in the referenced lookup table, identify the lookup fields and the tables they are looking up .
For eg.If you have a lookup field as 'Country' as one of the fields, look up table will be 'Countries'
2.For the identified lookup tables, set 'key mapping =Yes' in Console.
For eg, For Country Lookup table ,set Key mapping to 'Yes'
3.Import values into Lookup table (Import manager)/ Remote key update -
In import manager, select source (local file) and destination as Countries flat table.This Table will be haing 2fields - Code and description.Clone the 'Code'field and map it to Remote key field in destination hierarchy.Map code and description to equivalent destination fields. Select 'Code' as matching field > Perform import into lookup table.
Check if the records in countries table are updated with remote keys(in Data manager> right click on a record> select 'Edit key mappings' > view key mapping for the record)
3.Import to Qualified table/Auto value mapping -
Now, in the import map for qualified import , map the source field and destination field (of lookup type), all the values of this field will automatically map.
Similarly, refresh remote keys mappings for all the lookup tables first and then you can see auto mappings of values happening for the lookup fields.
Regards,
Vinay M.S

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

Create key mapping using import manager for lookup table FROM EXCEL file

hello,
i would like create key mapping while importing the values via excel file.
the source file containing the key, but how do i map it to the lookup table?
the properties of the table has enable the creation of mapping key. but during the mapping in import manager, i cant find any way to map the key mapping..
eg
lookup table contains:
Material Group
Code
excel file contain
MatGroup1 Code System
Thanks!
Shanti

Hi Shanti,
Assuming you have already defined below listed points
1) Key Mapping "Yes" to your lookup table in MDM Console
2) Created a New Remote System in MDM console
3) proper rights for your account for updating the remote key values in to data manager through import manager.
Your sample file can have Material Group and Code alone which can be exported from Data Manager by File-> Export To -> Excel, if you have data already in Data Manager.
Open your sample file through Import Manager by selecting the remote system for which you want to import the Key mapping.
(Do Not select MDM as Remote System, which do not allows you to maintain key mapping values) and also the file type as Excel
Now select your Soruce and Destination tables, under the destination fields you will be seeing a new field called [Remote Key]
Map you source and destination fields correspondingly and Clone your source field code by right clicking on code in the source hierarchy and map it to Remote Key if you want the code to be in the remote key values.
And in the matching criteria select destination field code as a Matching field and change the default import action to Update NULL fields or UPDATED MAPPED FIELDS as required,
After sucessfull import you can check the Remote Key values in Data Manager.
Hope this helps
Thanks
Sowseel

Update (All Mapped Fields) Import Action creates a new record.....

Hi All,
I am on MDM 5.5 sp6,and this weird thing happens everytime i run the "update all mapped fields" option in the import manager,it creates a new duplicate field with the updated value record.Is this a bug in sp6 or I guess i am going wrong somewhere.I want to update a particular field in the qualified table and i am using a import file which has values for qualified field on the main table and the values for the qualified table itself.
Any Help greatly appreciated
Thanks

Hi Aravind,
I am on MDM 5.5 sp6,and this weird thing happens everytime i run the "update all mapped fields" option in the import manager,it creates a new duplicate field with the updated value record.Is this a bug in sp6 or I guess i am going wrong somewhere.I want to update a particular field in the qualified table and i am using a import file which has values for qualified field on the main table and the values for the qualified table itself.
MDM should not behave in this way. I thing there is an issue with the Matching Field you have choosen.
I think you have choosen all the FIeld as the Matching Field ( Tab) while IMporting.
Hence any change in any value, creates another dupliacte record( which we do not want)
Please select any Field with unique values ( like the Material ID, Customer ID etc) which will ensure that the particular records are updated with the new Values coming in.
You will find the new value getting updated for the records which are already present. It will not create a duplicate record
Hope it helps.
*Please reward points if helpful
Thanks and Regards
Nitin Jain

Import Manager MDM 3.0 Updating old Maps

Similar Messages

Maybe you are looking for