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.

Similar Messages

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

MDM iviews in Portal throws error in key Mapping

Hi,
I have EP7 with SP15 and MDM 6.0, recently upgraded. Before upgrade we have an application which uses the MDM iviews and maps the fields of one table to other and displays in some other iview.
The application was working fine before upgrade of MDM. But after upgrade, the mapping seems not working.
My scenario is as : Using MDM Search iview, I search records from MDM repository, Main Table. This result is displayed in MDM Result iview. From this result iview, I select a record. From this selected record, a field is mapped to the other table. The mapped record, then, is displayed in MDM Details Iview.
After MDM upgrade, whenever we select a record from the result of table 1,the mapped iview throws erros :
Error occurred: Error performing search. com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter, com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter (see log for details)
when serached log : it says error in <table 1>-Key mapping <table1> is first table.
We have used EPCF eventing for MDM iviews.
has anyone out there faced same issue ?
Please let me know your views.
Regards,
Abhijeet

Hi Abhijeet ,
check the below wiki
findout anything is needed related to keymappings
"if Keymapping is selected, your Result Set iView only displays fields that are related to key mapping.This step depends on the search table selected and the schema of the repository that you are connected to"
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/set%2biviews
check the search table and schema of repository properties you connected
Koti Reddy

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.

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

Import Manager - Problem with 0..n field in Import Manager

Iu2019m having problems with XMLs that contain multiple or single tags in MDIS process. For example: I did the map using a XML with multiple tags for Address:
<address>
<item>
u2026
</item>
<item>
u2026
</item>
</address>
When I send two address or more Address, the Import Server work fine, but when I send only one Address, the address is not imported.
<address>
<item>
</item>
<item>
</item>
</address>
Opening the xml file with only one Address in Import Manager, I saw that the fields isnu2019t mapped, but when I open a xml file with multiple Address itu2019s open correctly.
The XSD cardinality for the Address\Item is 0..n

Hi Evandro ,
If it is processing the input file correctly through the Manul Import manager process then update your latest Map by using SAVE As option or else save this correct map with a new name altogether and use this new map in the port for automatic importing.
If your file is able to process correctly through the Import manager without showing any errors till the Import step in the Import manager then this map must be correct and shoul automate the importing correctly.
Provided you are using the similar file for automatic importing as well.The file name and the fields as well as the value mapping as saved in this corrected map must not differ with the input file else this saved map will not be able to import correctly.
Check to see if you have made correct setting for automatic importing by refering the below link:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm (Automatic importing MDIS - Import manager ref guide>MDM import server(MDIS)>MDIS Consfiguration)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e(mdm import and syndication server)
Also check the exception folders if your import is not taking place automatically:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm (Exceptions- MDM Import Manager MDIS-Exception handling)
Hope It Helped
Thanks & Regards
Simona Pinto

Steps in Key mapping

Hi all,
i have gone through many forum's regarding key mapping.
i can see that the following are used..
--> remote systems
--> key mapping option in table-field properties
--> key mapping option in table properties.
-->key generation(none, range, qualified range) field in remote system properties.
But never understood like in which order we need to define all the above, what is the relation b/w them.
i have gone through some theory in sdn regarding key mapping but unable to get the logic..
can any one one show me with 2 records in 2 tables so, that i can clear my confusion.
Thanks in advance.
Regards
phani

Hi Phani,
first you should understand the basic idea of key mapping. MDM usually wants to consolidate master (objects like vendors, customers, and so on) and/or reference (lookup tables like countries, regions, and so on) data. The idea is to load this data from various remote systems into MDM, compare and match the data, and in some cases merge multiple records into a single one. Let's take an example.
Image you have attache two remote systems to MDM. The first is an ERP system, the second a CRM system. Both system contains countries as reference data. In ERP, your country India looks like
Name = India
Code = INDIA
whereas in CRM it looks like
Name = India
Code = IND
It is obvious that the country is the same, but the systems use a different internal code. Now you load this data into MDM. What do you do? Do you want to create two records having different codes? Or do you want to "merge" the indentical records into a single one. The common decision in MDM is the second one.
But what happens now if you send customers from ERP and CRM to MDM? Usually the Customer message contains the Country CODE but not the Country NAME. From ERP the message could look like:
Customer = Mr. X
Country = INDIA
whereas from CRM the message could look like
Customer = Mr. X
Country = IND
Surely you want to map the different code in both case to the same country "India". That's why you use key mapping in MDM. Key Mapping allows MDM to store different codes for the same data. So in MDM you store just one record, but if you receive and/or send data from and/or to remote systems, you can always ensure that you store and/or send the correct codes.
Hope that clarifies your doubts about key mapping in general?
OK, now regarding your question about "Update NULL fields only":
In Import Manager you have several options for data import. If you import for the very first time (for RS1), your table in MDM is usually empty. That why you need to "Create" the records. If you import the second time (for RS2), your table in MDM already contains data. Depending on the matching field for import, several options are now possible. If Import Manager is not able to match the record you want to import against any other existing in the repository, you have to "Create" the new record. If Import Manager is able to match the record that you want to import with a record of your repository table, you can choose what happens next. "Update NULL fields only" compares the record you want to import with the existing values in MDM. In your case, following info is already part in MDM:
Country = India
Code = INDIA
Remote Key RS1 = INDIA
Remote Key RS2 = NULL
Now the file you want to import contains the following values:
Remote System = RS2
Country = India
Code = IND
Import Manager identifies that only "Remote Key RS2" is NULL. All other fields already have values. As you choose to "Update NULL Fields only", only Remote Key RS2 gets a new value. If you choose a different option, e.g. "Update All Mapped Fields" Import Manager would update the Country and Code fields, too.
Best regards
Michael

Can Key Mapping details be available as a serach parameter in MDM DM?

Hello Experts,
Is there any way that we can display or search certain Records in Data Manager/Portal based on the Key Mapping details (Remote System/Key Value assigned for any remote system).
The scenario where I am trying to apply this is:
I have say lacs of records in MDM and i have merged certain records into a new record (Record1) and assigned key mappings to this record1 to point to System1 and System2.
System1 has the key value as ABC and System2 has value set as DEF. If any user wants to now find the merged record based on the key value of system2 (i.e DEF), how will he proceed?
Kindly advice.
Thanks and Regrads,
Elizabeth.

Hi Elizabeth,
In MDM Data Manager, once the record is merged you can see only one record in place of all merged records.
In your case ABC from system1 and DEF from system2 are merged into ABC.
So in data manager you can just search the record based on ABC but not DEF.
However, if you select the record ABC and right click and select Edit key mappings, then you will see both the records and its respective system.
So the work around is using syndicator, send the records in excel sheet or CSV file where you can send both the merged records with merged values.
The users can make a search in that CSV file with DEF as well.
Regards,
Sravan

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

Import manager error, when using Standard maps

Hi,
I am trying to import data using Import manager statndard Maps.
For certain maps I am getting the following error message.
<b>"Unable to retrieve unique values for field 'Key <Clone>'."</b>
And also after getting this error if I close the current statndard map and open another standard map, import manager crashes.
I am using MDM Version 5.5 SP2(5.5.24.04).
Thanks
Subbu

Hi Subbu,
I encountered this issue around inability around unique values for cloned fields too, although in custom maps, not standard ones.
1. When reported, this was fixed in 5.5.24.05. So, try usin 5.5.24.06 and see if you still face it.
2. The other option or workaround to be precise is to uncheck the Read-only box in bottom left hand corner of the second screen. This should work too.
As a last note, even in 5.5.24.06, I still encounter this issue when importing into nested look up tables. This is up for future fixes.
I use the uncheck read-only as work around for now.
Good luck!
Savi

Runtime Error in Import Manager

Hello,
when I try to import data using Import Manager it brakes up showing the message "Runtime Error! ....path to application... R6025 - pure virtual function call".
I'm running MDM 5.5 SP02 Release 5.5.24.06 and also tried to use the Import Manager on another computer but the same mistake happened.
Can someone help me ??
Greets,
Daniel

I had this problem a few times in the last 5 months. A few tips that solved:
a) To rule out that it does not have anything to do with server, I usually close my applications, stop and restart the server. Sometimes, I had to reboot the server.
b) Then, I make sure that for the table I am loading, display fields are flagged accurately; table level key mapping setting is turned on.
c) In the import manager itself, depnding on my display field(s), that remote key is mapped to the display field or compound key of the display fields (in case of more than 1).
d) If I am loading a multi-valued field, right click on the multivalued field in the destination pane, after mapping, and set the multi-valued update option.
e) If it is qualified table load, again, right click and set qualified update option on the field in the destination pabe.
Hope this helps. Good luck!

Import Manager Out of Memory error

I am running MDM 5.5.24.06 server on Windows XP Professional. The server has 4.0 GB RAM with 1.5 GB Virtual memory.
I am trying to load 129 material master records from R/3 4.6 ( XML file size 8 MB), into MDM using Import Manager.
When I click on import icon (Import Status tab selected), MDM Import Manager rightway returns 'Out of Memory' error.
Tried to import the file again after rebooting the machine, restarting MDM Server, but still it returned the same error.
Has anybody tried loading the R/3 material data into MDM? What's the experience? What was the load (# of records)?
What was MDM IM performance? What's your hardware/software config?
Appreciate your help.
Thanks,
Abhay

Hi Abhay,
My workstation has Windows 2000, Pentium 4 CPU 3.2 Ghz, 515,555 KB RAM. The recommended specifications can be found on service market place of SAP, and we used those to procure our workstations.
MDM server must be more pwerful than a workstation. Try running the import manager from the server machine itself. If it works there but not on your machine, it is memory of your workstation.
Sometimes, I think this error comes when import map some issues- fields not mapped accurately or remote key mapped wrong etc.
It is probably judicious to rpove the system memory as first step.
Good luck!

XML file error while loading import manager

Hi all,
I am new to MDM.
I have archive repository(.a2a file),xsd files,import maps and export maps.I have unarchived the repository in console and I am trying to load import manager by selecting the file type as XML schema, client system as MDM, XMl schema name and file name as XML file of given XSD in import manager folder of server.
I am getting error like "failed to parse XML file".
Please help me out regarding this.
Thanks in advance.
Ravi.

Hi ravi,
Is it MSXML 4.0 SP2 parser?
<a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en">http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en</a>
Try installing this and let me know.
Thanks and Regards,
<b>Sagar Sonje</b>
Message was edited by:
Sagar Sonje

Error while using Import Manager in MDM 7.1 SP7

Hi,
We are using MDM 7.1 SP7. I am trying to import a Tab delimited flat file through import manager. When I try to connect the source file, I get the following error * Logon Error: Found non-complaint CSV format in input stream [Encoding:UTF16].96*
If I try to import through an excel there is not problem. Can someone help to solve this error while importing in Tab delimited flat file through import manager.
Best Regards
Manoj

Hello Mandip,
I had tried doing it before posting my question. I saved it in UTF8 and then tried importing. Saving in UTF8 format made the import manager accept characters like Ä and the original error was solved, but when then a new error came which called for UTF16 format. When I digged into it I found that it is due to the double quotes(" ") in the flat file. When I removed the quote import manager accepted it.
So the conclusion is there should be a way to save the flat file in UTF16 format or the workaround is importing it in excel but again excel has limitation of importing 100000 records in one file.
Can you suggest how to save the flat file in UTF16.
Best Regards
Manoj

Error in Import Manager if Constraints are assigned to lookup table

Hi Folks,
I am using the Repository SRM-MDM Catalog...and in the Console,
For a Role, if I assign a Constraint for the lookup-table Product Groups, System shoots the error message in Import Manager when I try to Map the file.
Scenario: Say I have Product Group from LOC1-LOC5, and for a Z-Catalog Manager Role(Manager1) if I assign the Constraint-LOC1.....and if I Import a file in the Import Manager, system shoots the error message "Unable to retrieve Unique values for Product Groups".

Hi Mohan,
Are you updating any Qualified table.Please explain what table and also some more details.
Thanks
Ganesh Kotti

Import Manager 'Error 5611520 - Error Saving Key Mapping'

Similar Messages

Maybe you are looking for