Importing 2 Qualified Tables

Hi Team,
Need suggestion:
I have 2 Qualifier tables. 1 with more than 3 Non Qualiers and the other with only 1 non qualier.
I am successfully able to import their main table data individually, using different maps.Both the values are getting populated.
But on importing the Main table data (1 map) with both the Qualified tables, only 1 of their Non Qualifer data getting displayed.
Both these Qualified tables have no common fields between them. No idea why it is affecting on importing together.
NOTE:
On importing the Qualified tables manually with 2 different maps, it is getting imported.
But on importing Automatically, only one of the Qualified table is getting populated.
Thanks,
Priti

Hi Priti,
For multivalued field you need to check for Qualified Update option. For this you can refer page 257 of Import manager 7.1 reference guide. Try this option, it should solve your problem.
Thanks & Regards
Dilmit Kaur Chadha

Similar Messages

Source file structure when importing a qualified table

Hello MDM:ers
I need to import a qualified table into the following repository
(it is simplified to illustrate the problem):
Main table: Products
Fields: ID (int), Name (Text), Part number (Qualified)
Qualified Table: Part Numbers
Fields: Manufacturer (Lookup), Part Number (Text)
Lookup table: Manufacturers
Fields: Name (Text)
The source file is a very large text file that has the following structure:
Part ID          Name     Part no. Manuf 1     Part no. Manuf2
123          Nut     ABC               XYZ
456          Bolt     DEF               QWV
The result Im looking for Is to map a file structured a above so that two main table records are created (Nut and Bolt) which both have two qualified table records for each manufacturer. I have not been able to create such a map. I have tried to partitioning and combining fields without success.
I have no problem creating the map if I manually restructure the file to look like:
Part ID          Name     Manufacturer           Part Number
123          Nut     Manufacturer 1          ABC
123          Nut     Manufacturer 2          XYZ
456          Bolt     Manufacturer 1          DEF
456          Bolt     Manufacturer 2          QWV
It where a way to import the file directly in MDM without restructuring it?

Hi Alexander,
MDIS will not work fine if you have multiple tables as the mapping is saved only for 1 table. If you have multiple tables then after performing the process of Pivoting/Reverse pivoting, you will have to use joins.
Join the other tables as Lookup in the Main Table
Save all your configuration in a map. And then configure the map in the port.
It should then work with the MDIS also.
hope it helps.
Thanks and Regards
Niitn Jain

SRM MDM - Multiple hyperlinks import into qualified table

Hi,
I need to create an import map where I can import two hyperlinks (URL2 and URL3) into the Hyperlink qualified table.
How can I achieve this?
I have an XML schema where the two hyperlinks are given in separate tags:
<URL2>http://www.test.net/xxxx</URL2>
<URL3>http://www.test.net/yyyy</URL3>
Can anyone provide me with a HOW-TO for how to map these two tags into the qualified table Hyperlink.
Maybe I should create two sections in the XML?
<URL2>
<MIME Type>URL</MIME Type>
<URL>http://www.test.net/xxxx</URL>
<URL Description>TEST URL</URL Description>
</URL2>
<URL3></URL3>
KR,
Thomas

Thank you very much. This worked fine.
Now I have another problem someone might be able to help me with.
The sending system does not wish to send a repeating XML tag with the two hyperlinks. It causes restrictions in the data amount that can be sent.
We see two possible solutions
1.
Building the hyperlinks in MDM, like a calculation.
<URL2>http://www.test.net/xxxx</URL2>
<URL3>http://www.test.net/yyyy</URL3>
xxxx and yyyy are values in fields we have in the MDM structure. Everything before this in the hyperlink is always the same.
Is it possible to create the hyperlinks based on the value of xxxx and yyyy? If yes, how could we manage this, also filling the fileds: URL Description, Hyperlink Type and MIME Type with correct information?
2.
PI can create the URLs during integration.
Which of these two should we use?
KR,
Thomas

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

Qualified table import

Hi folks,
could you please let know the procedure for importing the qualified table for a master?
Regards.
Jyoti

Hi Jyoti,
the procedure for importing the qualified table is as below:
1. First import the non qualifiers combinations and in this you may select the source table as main table and destination as the qualified table.
2. Now select main table as destination table and main table as source then first map the non qualifiers fields and all values.
3.MAke sure all the values are mapped for the non-qualifiers, now right click on any of the nonqualifier field and create a compund field.
4. the compund field will be created and automapped. BUt you have to map the values manually or "ADD" them.
REg,
Bis

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

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

Using Import Man to load Data into Multi Value Fileds in a Qualified Table

Hi there,
When using the Import Manager, i can not use the "append" option to load data into my multi value field which is contained within my qualified table.
Manually it works fine on Data manager, so the field has been set up correctly. Only problem is appending the data during Import Manager Load.
Any reason why I do not have this option available during Field mapping in Import Manager. The selection options are shown but in gray.
Would appreciate any sugestions.
Chris Huggett

Thanks Sowseel
Its a good document but doesn't address my problem, maybe My problem isn't clear.
The structure(part of) that I have currently is as follows.
Main Table - Material
                       QFTable- MNF PN
                           LUField - MNF Name(Qualifier Single Value)
                           LUField - BU ID (Non Qualifier Multi Value)
                           TField   - P/N- (Non Qualifier)
I know how to load data to the main and qualified tables, but what I can not do, using Import Manger, is updating the "LUField - BU ID (Non Qualifier Multi Value)" using the append functionality.
Thanks
Chris Huggett

Qualifier table option in import manager.

Hi Sdners,
I want ot know what is usability of "Set Qualified Update" option in menu bar of import manager.
How to use above mentioned option because when im trying to use it, its greyed out.
Iam using MDM 5.5 SP04.
Explain with below mentioned example.
Main table:
1)Material_number -
> Integer
2)Material_description -
> Text
3)Region -
> LookUpQualified(multivalued).
Qualified Table.
1)Region -
> Nonqualifier.
2)Tax -
> Nonqualifier.
3)Price -
> Qualifier.
Points will be rewarded for genuine answere.
Thanks in Advance.
Regards,
Neethu Joy.

Neethu,
Here's the scenario where you would use this option.
Suppose you are importing the main table data and qualified table data. The initial load will go fine and you will see correct data in the main table and in the qualified table. However, if you are loading the same data again (somebody made some changes and now the client wants you to re-import the data) then you should be very careful with the qualified data. By default a qualified link is set to 'Append' which means every time you import data (even the same data), import manager will create a new link in the qualified tables. To avoid this, you choose the option 'Update' instead of append. This option will allow you to update the existing links and create new ones ONLY if there is new data for them.
Now about why the option is grayed out. To enable this option you have to right click the field that links the qualified table to the main table. For example, in your example below, the field 'Region' is the link between the qualified table and the main table. Right click on this field to set the import option.
Regards,
T

Import Server - Multiple Qualified Table - Map Crash

Hello,
Requirement: I need to update multiple qualified table using single source file.
Preparation: I have created a map where mapping to multiple qualified table fields maually.
Have created a Inbound Port using the above map.
Problem: Import server throws an exception; while opening the Import Manager using the Port Option and corresponding Exception; Lot of fields were un-mapped. Looks like Import map crashed.
Please feel free to throw some light reg the same!
Thanks
Alexander

Hi Alexander,
If you are performing multiple qualifier table mapping and importing then you will hav eto create differnt map for each table importing.In that case you will rrquire multiple inbound ports and in each ports deatils you will give the map name pertaining to which qualified lookup table you wish to import.
Actually using automatic importing for lookups is not desirable as the lookups always need to be prepopulated before your main table importing.
The exception taht you are receiving could be due to the reason that the map you are saving is using only one table mapping and so most of the fields are left unmapped.
try not to use automatic importing for Lookup qualifier tables and use manual importing and see if the the exception still comes.
Hope it helps
Kindly reaward points if found useful
Thanks
Simona

Qualified Table (Bank Details) Import Question

I am using MDM 5.5 SP6
I am using the Standard SAP delivered Vendor Master Repository and trying to load the Qualified Bank Details table. Bank Details qualified table we have 9 non-qualified fields and 6 qualified fields.
Do we need to load the non-qualified fields in the bank detail table first?
Anyone help me with details about how to load this table including linking this to the main table?. If anyone has any document explain the steps in detail then could you send it?
Thanks in Advance
Steve

First thanks to all who contributed.
I am able to load the qualified table but these non- qualified fields (Street, City, Swift Code, Bank Group, Bank number and Bank branch), I am not able to map it so after loading it was blank.
Out of the 9 non-qualified fields in the Bank Details Qualified table, Country, Bank Key and Bank name are DISPLAY fields and I am able to map and load these fields.
Other non-qualified fields such as Street, City, Swift Code, Bank Group, Bank number and Bank branch are NOT DISPLAY fields. While using the import manager and doing field mapping, for these 6 fields there is NO destination fields displayed. So I couldnu2019t map it.
When I made the above 6 non-qualified fields as DISPLAY fields, then try to map it, I am able to see these fields in the destination side and did the mapping. After import still those 6 fields are blank.
What I am missing here?. Is there any limit that only 3 non-qualified fields we can map it?
Steve.

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

Import Qualified Tables

Hi All,
When im tryin to import a QT im performing following steps:
1. Import Non Qualifiers with QT(Bank Details) on destination side.
2. Map other fields along with Qualifiers with Main table on destination side.
3. To map teh Qualified main table field i need to create a compound field on source side. When im doing a right click on LHS it gives a option to create compound field, but beyond that Bank details QT comes as a read only field.
Please let me know where im missing out on this.
Thanks
Manish

Hi Manish,
For creating compound field, you should have more than one display fied.
In your case if you have only one non-qualifier then simply map that with the qualified field and if you have more than one then map them will the fields marked as D on the destination side then select both the mapped source fields, right click and select create Compound Field -> Bank Details.
Regards,
Jitesh Talreja

QUALIFIED table import at single step

Hi all if any one can tell me hoe to import qualified table and hierarchy table.
Qualified table has 3 yes qualifiers and one 2 no qualifiers.
Thanks in advance
Nm

Hi New Man,
For the hierarchy import, there are two cases 1) you already have the source data which you need to import 2) you need to create the hierarchy from the fields given.
If you already have the source data you can first go in the hierarchy table select the source field and add the field on the destination field side by right clicking on the hierarchy value in the source side in the value mapping tab and selcting the option "Add As Sibling/ As Child" you can choose any of the option as per your need.
After doing this you can choose the main table and import the hierarchy field from the source side to the destination side.
In the first step, we get the records in the hierarchy table on the destination side and in the second step you get to see those hierarchy records in the main table's hierarchy field.
If you dont have the hierarchy and you need to create it before importing with the help of the fields on the source side you can follow this link.......
Hierarchy Import
Reward points if found helpfull
Hope this helps you ......
Prasad.................

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

Importing 2 Qualified Tables

Similar Messages

Maybe you are looking for