Issue in Mapping Qualified Table in Import Manager

Hi Experts
I have extracted Customer data from R/3 ECC, I could successfully loaded reference data, but when trying to load Main table data (Using DEBMDM06 MAP) I am getting mapping issues with Qualified table (Sales Data and Bank Details).
Error Messages
Map 'Sales Data' field to import qualifier(s)
Map 'Bank Detals' field to import qualifier(s)
I have checked and found that all the field and value mapping is in place, If i remove mapping for the qualified table fields then the data is ready to import.
What is the issue, and how do I import Qualified Table data.
Appreciate your inputs
Gaurav.

Hi vickey ,
Kindly go through the below link it will help you understand better the mapping the workinga nd importing of Qualified tables:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e(Qualified importing with main table)
Hope It Helped
Thanks & Regards
Simona Pinto

Similar Messages

Not able to Populate Qualified Table in Import Manager

Hi,
I am performing following steps for populating Bank Detail Qualified table in MDM from R3 but not able to populate the data.
1.Populating all lookup tables like Account_no,Bank-Key.......
2.Mapping all fields in Bank detail table except the 'Collect Auth'
field which is Qualifier
3.In Customer table(Main) mapping Collect auth to Bank Detail field and
customer_no to its corresponding ID.
It is not populating the Bank detail data which are available in lookup tables
Appreciate your suggestion
-regards,
reo

Reo
Matching will be based on the Display field (at least one) of the Main table. This is for example the Customer Number.
You also need to map all the display fields of the qualified lookup table. Then you can set the Qualified Update Action by right clicking on the field in the main that is linked to the qualified lookup.(the Collection_Authorization I think). Set the option that well update/append/replace the qualified data fields of the looked table.
There is two how_to_guides that will help. You can download from SAP Service Market Place. (Otherwise I can email to you)
How To Troubleshoot MDM Import Manager
HowTo_LoadQualifiedFields
Rgs
Con

How to map Boolean Types in Import Manager

Hi,
I have a issue in Import Manager for mapping Boolean Types.
I have a field which has a single KEY and multilple values(for different languages).
I want to map it to a field in a Tuple.
I can map the Key to field name.
But the values, I am not able to map. Could you help me here please.
Thanks a lot in advance.
Regards,
Rashmi

Hi Anton
Format your GM Time source as YYYY:MM:DD:HH:NN:SS:TTT (e.g. 2010:02:19:14:34:28:000). Deviations from this format seem to confuse the IM.
HTH,
Mark

Creates new record in the Qualifier Table while importing.

Hi Guys,
When sending new bank details to MDM, then MDM creates a new record in the Bank Detail qualified lookup table. This is OK. But when sending exactly same bank details again to MDM, then MDM creates again a new record in the Bank Detail qualified lookup table. I would expect that it
first performs the Automap and only if it cannot find a value, it will add a new record!
Can you guys help me out from this?
Best Regards
Devaraj PK

Hi Devaraj,
Please check these configuration options of Import Manager
1. Default Qualified Update - The default setting for whether incoming source subrecords either are appended to, completely replace,or update the set of existing qualified links of a qualified lookup field when updating existing records.
2. Default Matching Qualifiers - The default setting for which qualifiers to use as matching qualifiers when matching existing qualified links when updating existing records.
Any operation on the qualified tables will depend on the above two options.
Reward if found useful
Regards,
Jitesh Talreja

Force one unique record in a qualified table in data manager

Our main table is Customers. We have a qualified table that stores Company Code information. We need to ensure that each customer in the main table has only one record per company code in the Company Code qualifeid table.
Company ABC can be linked to Company Code 1, Company Code 2, Company 3 (three records in the Company Code qualified table)
Company ABC cannot be linked to Company Code 1, Company Code 2, Company 2 (three records in the Company Code qualified table where two are duplicates)
Company code is a the only Non-Qualifer field in the Company Code qualifeid table. I have set field as Unique in the console but i can still add duplicate records

Tammi,
Choosing Qualified table is wise option, when we really want to maintain possible duplicate data!
otherwise Normal Lookup table would be ideal option.
befor we proceed further, cud u pls explain me the unique factor to choose qualified in ur Business requirement?
thanks
Alexander

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

Qualified table update

HI MDM Gurus,
i'm facing a challenge when importing main table records into MDM. After main table record is imported with qualifiers, i want to update only qualifiers. But when updating qualifiers, the qualifier values are appending instead of replacing.
pls help.
Thanks.
Jyoti

Hi Jyoti,
While importing the qualified table thru import manager, right click on the non-qualifier combinations and choose any option either to "replace/update etc" for the non qualifiers.
Regards,
Bis

Import issue with Auto-id in Qualifier table

Hi,
I am trying to load Customer_contact table in MDM5.5 sp4 from R3.
Since SAP-Id is generated in R3, initially portal will send all data to R3 w/o SAP-id but with the MDM-Auto-id.
In return from R3,MDM receives the SAP-id and Contact-id against this MDM-id for update.
In conversion,I am getting "Error in Look uptable" "Internal Error" message to load this file in Main table.
Is there any workaround to map qualifier table with a auto-id in Main table?
This auto-id needs to be non-qual for portal to create the initial record in MDM.But since this is a non-qual fld and we are not able to map it in main table giving "Internal error" . It is my guess.
Appreciate your idea and help
-reo

The issue was fixed after dropping the calculated fld as Non-qual one which was giving problem since required to be mapped in Main table.

Value Mapping in Import Manager

Hi All,
I have Probelm while loading data to MAIN TABLE through Import manager,I am getting XML file from Legacy System in which legacy sends State Code like NM (for New Mexico) .In my region table I made Name and Code as display field .Created my Import map ,when ever new value comes for region value mapping is not working ,I tried changing my region table with code only display field it works ,but I want Name also display field .
Note : all my lookup table Remote key mapping Enabled
Is there any way we can acheive this or am I missing some thing here .
Thanks,
Madhu

Hi Madhu,
to achive this:
1. First go to the table where you are maintaining the region codes.
2. Enter the region code there and then go to the import manager by connecting to the source file.
3. go the region field map by opening the map.
4. go to value mapping pane and select unmap.
5. then select Automap and check the that your region code added manually is mapped with the source file.
6. You may see some unmapped source values, map it to Null values at destination.
7. Save the map.
8. This shoul enable the import for you.
if you want to avoid the manual mapping everytime, you should be getting all the region codes once and import/update it in the data manager as a one time job.
Then you avoid steps 1 to 3 everytime and carry out the remaining steps to import the records.
Hope this helps resolve the issue.
Thanks
Rahul

Using MDIS to import qualified tables

Hi, All !
I've encountered a strange problem - MDIS throws structural exception during import of data from xml into qualified table.
In MDIS logs I found this record: "Create lookups failed. Source record No. : -11, Error message : Invalid field values."
But if I try to import the same file with the same import mapping, using Import Manager, everything is ok!
Has anybody faced same problem?
Edited by: Alexander Pomazunoff on Apr 22, 2008 6:14 PM

Hi Alexander,
According to me, there can be 2 reasons of failure:
1. You have mentioned that your source file has 3 tables in it. MDIS can handle only 1 table mapping at 1 mapping. For mapping all the 3 tables at 1 go, you will have to look-up all the fields in the 2 tables to the Main Table. This will ensure that all the fields that you want, exist in the Main Table Mapping.
You have mentioned that you have done this for the Quailifer table, Kindly check it for the Look up FLat also.
2. If the above problem is not there, then kindly check the Map. I think, You have mentioned that the Map works with the Import Manager. The map should be perfect, only then the MDIS will be able to import it.
Now, Actaully sometimes what happens is,
The map is saved with a source file. After that it might happen that you would be using a source file which would have extra Tags ( Fields). That means, now the source file that you would be using might be having some extra tags as compared to the source file which you must have used for saving the Map. The Map becomes Out of Date. Perfom, Save Update ( in the Import Manager) after any changes made to the map.
Also, try creating 1 map for the current source file.
Configure the same map for the MDIS and keep the same source file in the Ready Folder. If MDIS does not gives an error and it imports the file, then the problem is with your Old map as it throwing a structural Exception.
Kindly check it.
Hope it helps.
*Please reward points if useful.
Thanks and Regards
Nitin Jain

Reuse of MAP in Import Manager

I am trying to reuse a MAP created to load KNA1 table in Import Manager in the same server. The Source file name and file type (.xls) is the same, as well as the original worksheet name. While the Import Manager is matching records, it is abending w/ following msg - Error sig:
AppName: importmanager.exe; Appver 1.0.0.1; ModName: importmanager.exe; ModVer: 1.0.0.1; Offset: 004e9c90
Thanks

Sure, this is possible. Remember that map/syn files are useful when you know in advance nothing has changed, that is, when automating the process (via batch/server processing).
One example might be if MDM is expecting numeric value, whereas in the past you used a text value. You might not be changing the source data, but you have made the MDM Repository more restricted.
Perhaps you should review which changes have taken place, something might be escaping your sigh
I hope this helps
Regards
Alejandro

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.

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

Multple Actions on single Qualified table??

Hi Experts,
I have a QT with 1 Non qualifier and 2 qualifiers..
My requirement is
Main table
CC Code (Unique key)
CC Contact info (LK QUAL)
Qual Table
Type (Non Qualifier)
Telephone (Qualifier)
Fax (Qualifier)
Value in Type Field is
General
In data manager i have the following..
COde :99
type : General
Telephone: 43
Fax: 11
There are 2 requirments for this table..
if my second file has inputs as..
Code: 99
Type: general
Telephone: 3342424242
fax: 222342
Code: 99
Type: External
Telephone: 24224567
fax: 3432342
Now My record after import should look like..
Code: 99
Type: general
Telephone: 3342424242
fax: 222342
Code: 99
Type: External
Telephone: 24224567
fax: 3432342
So here New External is added(Which is not available in DM in prior) and Old 'General' is replace with new values..
Is this possible???
i tried with Qualified update in Import manager
If i set Update then new values(External) is created but the 'General' is added as a new Entry instead of Updating the old 'General' entry..
If i set Replace/Append then the External values are not being added..
Can any one say whether this is possible & What is ONLY possible??
Please Help..
KR
John

Hi,
In the mapping tab..
I selected the Type Filed -> Right click-> set qualified update - > here i selected update-> i can see the telephone and fax moved to the selected qualifiers -> New links Create -> existing link update (all mapped fields).
If i do the above the New entry (Type: External, Tele and fax ) is added, But there is a new entry for Genral(Which should be actually updated with the Old entry of general)
Can anyone help!!
Kind Regards
Venkat

Mapping issue with Qualifier table

Hi,
1. I have an issue after mapping all 3 non-qual flds of a qualifier table in main table getting the compound fld enabled but selecting it , not mapping automatically to the appropiate compound field in the destination side, but giving an error message
"unable to retrieve source record".
2. The second issue is that after mapping some of the fields and qualified table and loading the maintable data, saving the map but subsequently when trying to open the saved map , it is coming out with the usual main error window
SAP MDM Import Manager
SAP Import manager has encountered a problem and needs to close.
We are sorry for the inconvenience.
Debug Close
Appreciate your help/suggestion on this issues.
regards
-reo

Answer for Qn2:
First you have to map all the display fields to individual Source Fields..
Once you have mapped all the dispaly fields of the Qualified Table, you have to do value mapping for the Fields that require Value Mapping.
Ex: Source Field A -> Destination Display Field 1
Source Field B -> Destination Display Field 2
Source Field C -> Destination Display Field 3
Now Value Mapping where required should be done.
Once the value mapping is done, then you can create a Compound Field.
If you have done the previous steps correclty, then the compound field name is enabled for you to create Compound Field.
Now map the newly created Compound Field to the Qualified Lookup field of the main table.
Now you have to click on the Automap for value mapping.
Hope this helps.
Please reward if you find this helpful

Issue in Mapping Qualified Table in Import Manager

Similar Messages

Maybe you are looking for