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

Similar Messages

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.

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

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

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

Import Manager Join Tables not working

Hi Experts,
for combining tables in the Import Manager i tried to use the join and lookup function.
My easy example is:
Table1
Product ID
Organsation ID
Table2
Organisation ID
Plant
Now I'm joining using the field Organisation ID which contains the same items and make a lookup on the field Plant. In the Source Preview I can see the looked up field but without any values and it is with a grey background.
Any suggestions?
Thanks
Andy

Hi,
I tried this at my end. It seems like a Bug. I am using MDM 7.1 SP3.
Facing same issue, I mean Grey background (not editable) in source preview, when we look-up field Plant from Table1 to Table2.
This field values are seen mapped in Map Fields/Values tab, but when i import data. Fields get populated for Product ID and Organization ID only but Plant field is not getting populated into MDM data Manager.
So, i am quite sure it seems like a Bug and I would Suggest you to Raise OSS note for the same.
Temporarily, You can import data in below manner.
I mean when you select Source table as Table1, you can import Product ID and Organization ID.
After importing Table1, select your Source table as Table2 map both fields Organization Id and Plant.
Import data by selecting Matching Field as Organization ID and Default Import Action as Update (All Mapped Fields).
So, in this way you can have your complete data in your MDM but obviously just because of bug which you can do in Single Step, Now going to be done in two Steps.
Note: For one of Client i did this on MDM 5.5 SP6, that time it was working perfectly.
Thanks and Regards,
Mandeep Saini

Qualified Tables Working

Hi All,
How to Map the qualified fields in the qualified tables if the qualifier for that field is set to YES, because such fields are not reflected in the import manager for mapping only the fields whose qualifier is set to NO are visible.Thee problem is wen the qualifier for a field is set to YES you can feed the data only in the DATA MANAGER as these fields are only visible therewhich become so much of a lengthy process if data is large.
Can any one please explain the importance of the qualifier in the qualified table in layman terms, how to make the best use of it and please if possible give a short and sweet example for it.
HELP NEEDED URGENTLY
Thanxs in Advance.

Hi Prasad,
Where do we use the Qualified tables:
At times data is stored in such a way that duplication is unavoidable due to the storing mechanism and other factors. It may also happen that the data is sparse. The efficient way of storing data in such scenarios is the use of Qualified tables as it reduces the size of the main table and removes the unnecessarily created duplicates.
Difference between Qualified lookup table and Flat lookup table:Flat lookup tables normally work on only a single field. It contains the set of legal values to which corresponding lookup field in the main table is assigned.
E.g. suppose we have a flat lookup table for Material Group for an automobile manufacturing company. Here we have a fixed set of legal values that can be looked up into the main table (for example Cars, Bikes, SUVs, etc.)
Qualified tables work on the combination of two types of fields where value of one or more fields (qualifiers) changes depending on the values of one or more other fields (non-qualifiers).
E.g. suppose we have a field Price whose values varies with the region for the same product. Here we have a fixed set of related legal values (combination of fields) that can be looked up into the main table. (For example Product A has a price of $30 in Southern region whereas $40 in Central region, then we get a set like Product A | Southern | $30, Product A | Central | $40 in the Lookup Qualified table)
Watch out for the definition of Qualifiers and non-Qualifiers:
This was something which took a long time for me to hunt down.
Qualifiers are those fields whose values change based on the value of some other field(s) and whose value is different for each main table record
Non Qualifiers These fields are only the part of qualified lookup table, but they apply not only to the qualified table but also to each association of the qualified table record to the main table record. Simply speaking, they are the fields that will decide the values in the Qualifier (main table)fields.
Our Scenario:
Suppose we have been provided with the following source data
Manufacturer Name of Drug Region Price Storage Temp
A Crocin North 280 27 Celsius
A Crocin South 300 14 Celsius
A Crocin Central 260 30 Celsius
A Disprin North 380 30 Celsius
A Disprin South 360 27 Celsius
A Disprin Central 320 14 Celsius
Observation:
Values of Price and the Storage Temp field change based upon the Name of Drug and Region field values and also their values are different for each main table record; hence these should be madequalifiers in the qualified lookup table
Since Name of Drug and Region fields are deciding the qualifier values hence these should be kept as non qualifiers in the qualified lookup table. Manufacturer and Price will be part of the main table.
Design of repository:
We will discuss only the design of the main table Products and the Qualified lookup table Prices as they are of our immediate concern.
Products
Field Field Detail
Manufacturer Name- Manufacturer
Type - Text
Required Yes
Display Yes
Lookup[Price] Name- Lookup[Price]
Type - Lookup[Qualified Flat] (multi-valued)
Required None
Display No
Multi-Valued - Yes
Lookup Table Prices
Prices
Field Field Detail
Name of Drug Name- Name of Drug
Type - Text
Required No
Display Yes
Qualifier - No
Region Name- Region
Type - Text
Required No
Display Yes
Qualifier - No
Price Name- Price
Type - Currency
Required No
Display Yes
Symbol - $
Decimal Place - 0
Qualifier - Yes
Cache - Yes
Storage Temp Name- Storage Temp
Type - Measurement
Required No
Display Yes
Dimension Temperature
Default Unit Celsius
Qualifier - Yes
Cache - Yes
Note: Caching of qualifiers is strongly recommended as it dramatically improves search performance.
Once the design of the repository is through, we now move on to the trickiest area the one of the Import Manager
Importing records:
As per the standard practice, we load the lookup table first, here Prices and then the main table Products.
Step1:
Loading the Qualified lookup table data:
Select the corresponding tables in the source and destination hierarchy in the Import manager.
Go to Map Fields/Values tab and Map the corresponding fields in the field mapping grid.
Note: Here only two fields (non qualifiers)can b seen in the destination field grid, however in the repository design we have created four fields.
The qualifiers (fields) never appear in the destination field of the qualified lookup table in the Import Manager.
Go to Match Records tab and select the non-qualifiers as matching field and Add it as Combination.
Select Import Action as Create as it is an Initial load of data.

Step2:
Loading the Main table data:
Map all the source fields to corresponding fields in the repository.
Notes: Here many fields in destination (including qualifiers (Q) which are defined in the qualified table and not in the main table of the repository structure in Console).
Minimum required field mapping: All non-qualifier fields of the qualified lookup table should be mapped. Qualifier field (Q) is optional.
Now we are left with one field (Lookup [Price]) in destination which is still unmapped and we have no corresponding field left in the source to map it with. For this, go to source field tab and right click to create compound field
Lookup [Price] will be available in the source field and will get automatically mapped to the corresponding destination field.
Note: If any one of the non-qualifier fields of the qualified lookup table is not yet mapped, we are not allowed to create the compound field.
Do the Record Matching and Import the data into Data Manager Client by selecting the appropriate Import action.
Final Qualified data in main table:
The data is available in the Data Manager.
P.S. If there is only one non-qualifier in a scenario, then the Compound field is not created and direct one to one mappings suffice.
Please award me points if u find trhis blog as a value addition.
Thanks & Regards ,
Deepankar

Import Manager and Display Fields

I've been using SRM-MDM 3.0 for a couple of months and 1 fundamental MDM design has always bothered me and I was hoping to get some resolve on this.
The purpose of Display Field is 2 folds:
1. Display the field in the Catalog Search UI for a lookup table: i.e. if both Supplier Name and ID are Display Fields, then in the Search UI, both fields are displayed to the end-user. If only Supplier ID was the display field, then in the UI only the ID is displayed.
- From a usability pov, tables such as Supplier and Product Group should have the name or description fields displayed in the Search UI as the numeric values are meaningless to the end-users.
2. Display field ALSO affect what is the key used to import data into a table. So if Supplier ID is the display field for Supplier table, then in Import Manager, the Supplier ID values are displayed and must be mapped to the source values.
- From an importing pov, mapping values should always be an index-like field, such as Supplier ID or Product Group ID, or ISO, and usually never the actual name or description field.
But SAP has tied the two together. So in order to display the name/description to the end-user, we must enable the name/description field as a Display Field. But we also want to map based on the index/ID field, so we also enable the index/ID field as a Display Field. Now in Import Manager, we have two Display Fields for a table (i.e. Supplier ID and Supplier Name for Supplier table) and I've noticed some issues with this:
1. You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible. What is funny is that standard SAP extract program only extracts the ID fields, BUT the standard SAP repository has the name/description fields as the Display Field. Automap is a must for tables like Product Group where hundreds of lines can make manual mapping a pain.
2. I also noticed you cannot Add values to a table that has 2 Display Fields, you can only map to existing values. The Add button is grayed out.
With all that said, when you're replication ECC Contract Data using MECCM, for tables like Supplier and Product Group, what fields should be set as Display Fields, and if there are multiple Display Fields, what special setting needs to be done in Import Manager to enable automapping? Even standard SAP Import Map (_MDMContractDataTransmission_ProductID) throws errors when multiple fields are set as Display Fields.
I'm not familiar with the partitioning function, and I've seen PDF's about it, but don't really see how it could be helpful. I've also read someone suggesting changing the DF's before import, which I think is unacceptable, as this requires unloading/loading repositories everytime an import happens.
Thanks for reading my paragraph and any input is greatly appreciated.
Edited by: Derek Xu on Apr 30, 2009 6:50 PM

Hi Derek,
Thanks for writing your thoughts. I would like to provide some information on one of your points where in you have mentioned that :
You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible.
I completely agree that if you have 2 fields in MDM repository and you are only importing only one of them, then you cannot use the Automap feature of Import Manager. So in your case, the description is not getting importing, so you cannot use Automap in that case.
I had a very similar requirement in one of my project and we went with creation of a Import Value template. We created a template with all the possible values for all the look up tables in that and mapped it once in the Map. Hence, next time, the Map was used to automatically Map the source and Destination values for all the look up tables.
SAP-MDM Automatic Import Requirement u2013 Creation of a Value Mapping Template:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
Please read the above article and hope its useful. You can go for this approach in your case if suitable.
I have mentioned examples of descriptions and their respective fields in the article.
Hope it helps.
Thanks and Regards
Nitin jain

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

Truncate / Trim and Convert the values while importing in Import Manager

Hi,
I am facing the following issues while importing the values in Import Manager.
1) The incoming value is a 4 character text value (e.g. D004) and i need to truncate the 1st two characters so that i get the output as "04" and map it to the destination numeric 2 character field.
Can any1 help me on this as to how can i truncate the 1st two characters?
2) My incoming value is a numeric field which is coming from ECC. this value can be negative as well. the ECC sends this value as (78.00-) ie the minus sign is suffixed to the value but in MDM i need it as (-78.00) ie minus sign prefixed to the value.
Is there any setting in Import manager where i can set the minus sign as a prefix?
Useful answers will be rewarded with points.
Regards,
Roshani

Hi Roshani,
Can any1 help me on this as to how can i truncate the 1st two characters?
As suggested by everyone, none of these options will work. Since your field has alphanumeric Value i.e. D004. Use Option Replace.
After mapping your source field with target field which must be of Type TEXT, Right click on your source field>Set Value Conversion filter>Replace..-->a pop up window will come Replace write Find What: D0 and Replace with: keep it blank(dont write anything) and then Press Ok, you will see all your Source values D0XX converted to XX and then can save in Import Map which will give you the desired result.
If you set your target field of type INTEGER, you cant have option Replace. And the TRUNCATE option as suggested by everyone will not work as Operand 2: you can set as Numeric values only, you would not able to write D.
Is there any setting in Import manager where i can set the minus sign as a prefix?
I dont think this is possible alone with Import Manager, you need MDM workflow for this where your workflow trigger action = Record Import in Data Manager, and need to select the same workflow in configuration options of Import Manager>Import>checkout/workflow = select the workflow name from drop-down which you set in Data Manager and then need to save this in your Import Map. So in this manner whenever record comes through import Manager, these records automatically will go through this Workflow and will give you the desired result.
START(CHECKOUT)>Assign>STOP(CHECKIN)
Assign step where you give assignment on this field and write assignment expression as:
IF(FIND(XXX, "-"), "-"&LEFT(XXX, (LEN(XXX)-1)), XXX)
where XXX = Field name which you defined in MDM repository.
Regards,
Mandeep Saini

How to import data usin Import manager if one of the field is of type LOOKUP[FLAT].

Consider a scenario:
Where I created a Main table named STUDENT and it has 4 fields,
a) Among which 2 fields are OF DATA TYPE TEXT[50] and
b) Remaining two are of DATA TYPE LOOKUP[FLAT] and corresponding look up table also created in the repository.
When I tried to create a file with certain input records and tried to import the values into the Main table using MDM IMPORT Manager, I am getting error at the IMPORT STATUS tab with the action item message: MAP 'FILED NAME OF LOOKUP[FLAT] TABLE' FIELD VALUE(S).
Do I need to do any special action to import record if the field is of data type LOOKUP[FLAT].
Please advice.

Hi,
Since you need to import value into a field which is referred by a flat look table, you need to map the values of that field to the values maintain in flat look up table.
You can do the mapping from "Map Fields/Values" Tab.
You have probably Mapped Source fields with destination fields, but in case of importing values in lookup fields you need to map Source Value with destination value.
Keep the cursor on the required lookup field in Source field section, below that section you will be able to see Source Value section perform the mapping in that section too and it will resolve your issue.
Regards,

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

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

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

MultiValued Update option is disabled in Import manager

Hi,
I have a scenario where one of the qualifiers specified in Qualified table is LookUp Flat(multi-valued).
Mult Valued look up table has 3 fields in it 3 are display fields.
While doing the mapping in import manager it is allowing me to create compound field and getting mapped.But when i right click on the qualifier and select Set Mult Valued Update option the features like Append/Replace/Inherit Default are disabled.
How to enable this option?
Regards,
Lakshmi

Hi Lakshmi,
But when i right click on the qualifier
No u hv to right click on a field to which Compound field is mapped ( Ur Main Table Field)
Right Click on Compound field & choose option Set Qualified Update.
New Links: Create
Existing Links: Update (All Mapped Qualifiers)
Thanks,
Maheshwari

Qualifier table option in import manager.

Similar Messages

Maybe you are looking for