Updating Qualifiers using import manager

I am having difficulties with updating my data in qualified lookup tables. I have a qualified lookup table Produkt Market Data with market as a display field (hierarchical lookup).
All other fields in this table are qualifiers, most of them multi valued. I have loaded the non multi value fields in the table first, so there is an entry for eg product 4711, market Health Care.
When i try to update a field text (multi valued flat lookup) using the import manager, the record 4711-Health Care is not updated but a lot of entries 4711-Health Care are created extra, each of them containing one line of text. I used the option update all mapped fields (and have mapped only product, market and text). When I choose the option update Null fields only, nothing happens: only the lookup table for the text is updated.
can anyone tell me what i am doing wrong. It should be possible to update qualified fields using the import manager instead of creating new entries shouldn't it??
Regards,
Bert

Hi,
See the below example.
HeirarchyT [Hierrachy Table]
Name Text[5]
Data in Hierarchy Table
Hier1
-H1
--H3
-H2
--H4
MainT[Main Table]
Field1[Text5]
QField1[Lookup Qualified multivaled]
LT1 [ Flat Table 1]
NameLT1 Text[100]
CodeLT1 Text[2]
Data in this Table
LT1Val1 LT1Code1
LT1Val2 LT1Code2
LT1Val3 LT1Code3
LT1Val4 LT1Code4
LT2 [ Flat Table 2]
NameLT2 Text[100]
CodeLT2 Text[2]
Data in this Table
LT2Val1 LT2Code1
LT2Val2 LT2Code2
LT2Val3 LT2Code3
LT2Val4 LT2Code4
QualTable[Qualified Table]
QH1 Lookup[hierarchy]
No(Qualifier) Yes(DisplayField)
QMLV1 Lookup[Flat]
Yes(qualifier) LookupTable[LT1]
Yes(Multivalue)
QMLV2 Lookup[Flat]
Yes(qualifier) LookupTable[LT2]
Yes(Multivalue)
Intial data in the repository:
Record 1: N1
Qualified Data:
QH1 : H3
QMLV1: LT1Val1,LT1Val3
QMLV2: LT2Val2,LT2Val4
Record 2: N2
Qualified Data:
QH1 : H4
QMLV1: LT1Val2,LT1Val4
QMLV2: LT2Val1,LT2Val3
Lets say u have source data in Excel sheet like below.
N1 H4 LT1Val2,LT1Val4 LT2Val1,LT2Val3
N2 H3 LT1Val3,LT1Val1 LT2Val2,LT2Val4
Follow the instructions given by Rajani till step 5.
In the Step 6 selct The default import action as "Replace".
I hope this helps.
Thanks and Regards
Subbu

Similar Messages

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

Tuple Loads using Import Manager

Running on 7.1 SP05 using the SAP supplied Vendor Master repostory archive.
Attempting to load company code data in the Vendors main table. Company Code Data is set-up as a tuple table in Console.
When defining the map in Import Manager it will only allow me to select Vendor Number as the matching field. And, as a result, it will not load all of the data in my load file - it loads the first value of Vendor Number and skips the other records where Vendor Number is duplicated. This makes sense; however, I need to be able to select both Vendor Number and Company Code as my matching fields when defining the map. These two fields are the unique identifier for the load file and all the data would be loaded correctly if I was able to select Company Code as well.
I read where you can set the tuple update option and I did this by adding Company Code, but for some reason, it is still only using Vendor Number as the matching field and not including Company Code with it.
Does anyone know how to get Company Code to appear in the "Mapped destination fields" so that I can match on both Vendor Number and Company Code? Or do other options exist where I could accurately load the tuple table?

You match on the correct vendor in the Match Records tab. This positions you at the correct vendor.
To match on the correct Company Code you use the update tuple option (as you have done). The Company Code should be the only field that you use to match on the Company Code tuple. So, when the incoming record has the same Company Code the tuple will get updated. If the incoming record has a different Company Code, then you can set the options to either create a new tuple or skip the input record.
You can not match on the Company Code in the Match Records tab.
Edited by: Tom Belcher on Feb 18, 2011 10:13 AM

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

Order to import data in to SAP MDM using import manager

HI All,
Is this the order to import data in to SAP MDM?
Import look up tables
Import Hierarchy Tables
Import Taxonomy Tables -
Non -Qualifiers
Then import main table----map Qualifers along with Mian table and import...
Can we import entire taxonomy tables (Qualifiers, Non-Qualifers) along with main table after importing look up tables?
Thanks
Rajeev

Hi Rajeev
The sequence mentioned by you is correct for importing data in MDM- flat lookup, hierarchy first followed by Main table.
Can we import entire taxonomy tables (Qualifiers, Non-Qualifers) along with main table after importing look up tables?
I am assuming that you are implying Qualified table here.
Import to qualified tables can be done in 2 ways-
1. Import separately using the unique field for the main table for linkages to the main table records.
2. Import can be clubbed with the main table import itself. In the import map we can use Join functionality to do a lookup based on the unique field for the main table.
For more details on the mechanism please go through the threads below-
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/6090d0bd-1da7-2a10-468f-bdd17badb396
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8090941f-a5a7-2a10-3ba6-b4af5ec6d97b
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/308c62a2-5faa-2a10-fda6-fa4aa7169734
thanks
Ravi

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

Hierarchy Loads using Import Manager

Running on 7.1 SP05 using the SAP supplied Vendor Master repostory archive.
Attempting to load the Regions hierarchy table which contains three fields: Country (lookup flat), Region Code (text) and Region Name (text). When defining the map in Import Manager it will only allow me to select Region Name as the matching field. And, as a result, it will not load all of the data in my load file - it loads the first value of Region Name and skips the other records where Region Name is duplicated. This makes sense; however, I need to be able to select both Region Name and Country as my matching fields when defining the map. These two fields are the unique identifier for the load file and all the data would be loaded correctly if I was able to select Country as well. I have tried making Country both a unique field and a display field in Console, but to no avail.
Does anyone know how to get Country to appear in the "Mapped destination fields" so that I can match on both Region Name and Country?

Hi Reinhardt,
I think you can achieve it by setting country field also as Display field (DF) along with existing Region name (DF) in Regions Hierarchy Table of MDM console.
Regards,
Mandeep Saini

Using Import manager with XI

Hi,
I am working with Import manager without any connection with XI. So, I have created by myself a XML file and a its corresponding XSD file, and I have put the XSD file into the console using XML Schemas Table.
Finally, I choose into the MDM Import manager the next options:
 - Type: XML Schema.
 - Client System: MDM.
 - XML Schema: the XML Schema declared.
 - File name: the XML file created.
The import manager imports the XML file correctly. But, my question is:
It's the same using XI? I mean, How works MDM Import manager using XI?
For instance, If I want to work with a CRM client system:
 1. XI works with CRM and tranforms its IDocs to XML.
 2. XI puts its XML file into any folder (than doesn't correspond with the ports declared into the MDM Console).
 3. Finally, XML takes the XML file in to that folder (exactly in the same way that I did before)
 4. MDM Import manager then imports the XML file into the repository.
Is that correct or the process is absolutely different using XI?
Thanks in advance,
Marta.

Each time you create a Port in the MDM Console directories are created on the server to hold data being exported and imported via the Import Server and the Syndication Server. If you log into your server you can find these directories in a heirarchy similar to this:
/opt/MDM/Distributions/ServerName/Repository/
So for example, a directory for one of your Ports may be:
/opt/MDM/Distributions/MDM_ORA/Material/Inbound/ECC(clientsystem)/In_ECC(portname)/
In that directory you will find several folders. One of which is the Ready folder. That is where the import server looks to find files to import. You can change the settings for the Import Server in its .ini file. This file is probably located in either your /opt/MDM folder or /opt/MDM/bin depending on how the installation was set up. There you can set how frequently you want the import server to check that port directory. If you are on unix you start the import server by navigating to the /opt/MDM/bin directory and running the command:
./mdis
Then check that it's running via command:
ps -ef | grep mdis
If you are on a Windows server you simply have to right click -> start the service in Services panel. Also make sure to check the /Exceptions folder in the port directory (same location as the Ready folder), because if the import fails, a file will show up there and lock the port from further use until that file is removed from the Exceptions folder.
Good luck
Message was edited by:
 Harrison Holland

How to Modify Hierarchy Filed Values by using Import Manager

Hi All,
I have some lookup table values in my source file in 1st attempt I have updated successfully. But, after cross checks the same i found that hierarchy level are incorrect at the destination side.
Source Hierarchy lookup values
Item1
Item 2
Item 3
Item4
Destination Hierarchy lookup values
Item1
Item 2
Item 3
Item4
Note: After Adding the Source filed hierarchy structure by selecting the Add Branch as child opting in the value mapping area
I am getting unique constraint Violated error message while importing the values.
So, how can I update the Source Hierarchy fields structure to Destination Hierarchy Field structure?
Thanks in Advance.
Mahesh

Hi Mahesh,
While importing the values if you get the error unique constraint Violated, that means that the same value has been mapped twice.
when you try to map the values of the hierarchy, NULL would have been automatically mapped.
When you select all the records and do add branch as child, the same NULL would have been added and mapped again.
If not with NULL, this could be the case with some other value.
Just check if some value is added and mapped twice in your value mapping.
This should solve your issue.
Try and let me know the result.
Regards,
Sravan

Loading data in multiple languages using Import Manager

Hello Experts,
I have a description field associated with Main table, and need to load the data in multiple languages.. How to load the data in Multiple languages using Importmanager?
Thanks in advance..

Hi Kiran,
Please do the changes as mentioned in this threads:
Re: Multi Language Question
Multilingual field
Regards,
---Satish

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

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.
"Unable to retrieve unique values for field 'Key <Clone>'."
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

Updating nokia n95 8 gb using device manager?

Hi friends
Can anyone tell me how to update n95 using device manager option in the phone?
Solved!
Go to Solution.

Hi amitkr
Presumably you are referring to FOTA feature for which ironically it seems that more S60 3rd edition devices (Non-Feature Pack 1) were supported and actually used this feature than the actual FP1 devices themselves. Think of the N80, N80IE and N73, all supporting and even frequently updating via FOTA.
Nokia then seemed to be making a new attempt at using FOTA by releasing the FOTA-only software version 11.043 for the FP2-based N78 and of course now for N96.
Happy to have helped forum in a small way with a Support Ratio = 37.0

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 Issue

Hi,
I have a bunch of records which have similarities in the description field of the source file and I need to consolidate all such records and add a separate ID to all such records in a different field. Example data is like this.
1 Rajani Kumar
2 Roman Rytov
3 Rytov Roman
4 Rytov R
5 Kumar Rajani
Here,1&5 represent the same Record for Rajani Kumar
and 2,3 & 4 represent same record for Roman Rytov.
So, I need to give an Id into a different destination field - A for Rajani Kumar(that is for 1&5 records)and B for Roman Rytov (that is for 2,3 &4 records).
Any solutions for this scenario while importing the records using Import Manager? Which is the best method ??
Regards,
RK

The process your are describing is a de-duplication process. For this exercise you need first to define a matching strategy and then implement this in MDM 5.5. This concepts has been demonstrated in a similar scenario identifying duplicate customers. Since this is rather extensive example I will only describe the highlights of what was done.
Based on the customer definition, a set of matching strategies was defined, each representing a specific matching scenario (e.g. one such strategy is: a matching consisting of : VAT number + Street + Name + Postal Code fields is assigned a Match Rage of 100, Match Group = Vat Number and Match Type = Matched.) Each element was initially assumed a weight (e.g. Vat Number = 34 ,street = 14 etc..) and the criteria was set to match results > 60 to be Match, result between 30 and 60 to Dubious and result <30 as Not matched.
For each of the above strategies a specific map was constructed based on the corresponding matching criteria per each strategy. Once these maps configured, the records for the de-duplication process are imported with this import only updating pre-defined fields for each of suspect matched records recording the Match Rate, Match Group and Match Type.
Once completed (all imports run ) you can see the MDM client all the matched records and group/sort them by Match type and grouping finally if you wish , merging the duplicate records while maintain their remote key information.
Kevin

Updating Qualifiers using import manager

Similar Messages

Maybe you are looking for