Qualified Tables Problem

hi,
I would like to know if possible to avoid duplicates in a Qualified table. When you create a qualified table you can set several things. firstly you can set if fields inside the qualified table are Non Qualifiers or Qualifiers and furtheremore you can set some field properties like display field...and unique field.
I realized that you can put 2 iqual records inside of a qualified table.
I would like to know how i can make so that there are not duplicate records inside the qualified table.

Hello Jose,
   Here is the example how you can eliminate the duplicates by using a qualified table
first the main table of product records shown in the figure below that contains sparse quantity pricing data for each product.
SKU     Name     1-9     1-24     1-49     10-24     25-49     50-99
113     Widget     $3.51                 $3.48     $3.44     $3.40
114     Wrench           $8.75                 $8.30     $7.99
115     Bearing                 $5.12                 $4.80
Using a qualifier to store the quantity pricing data, the qualified table would have a single field Quantity and a single qualifier Price, and would contain the quantity records shown in the figure below.
Pricing:
Quantity     [Price]
1-9
1-24
1-49
10-24
25-49
50-99
A qualified lookup field in the main table would replace all of the quantity price fields, and the pricing data would be stored as qualifier values associated with main table/qualified table links, as shown in figure below.
SKU     Name     Lookup [Pricing]
113     Widget     1-9; $3.51
          10-24; $3.48
          25-49; $.344
          50-99; $3.40
114     Wrench     1-24; $8.75
          25-49; $8.30
          50-99; $7.99
115     Bearing     1-49; $5.12
     50-99; $4.80
A main table/qualified table link is created only for those product/quantity combinations for which a price value actually exists.
So!, finally we can conculde this as ONLY THING THAT NEEDS TO TAKE CARE IS THAT THERE SHOULD BE NO COMMON DATA INVOVLED IN ANY OF THE COLUMN, IF THERE IS ANY COMMON DATA - THAT NEEDS TO BE CREATED CREATE IT WITH A NEW COLUMN.
Thanks,
Suresh

Similar Messages

How to create a unique group field in Qualifier table

Hi,
I am trying to use a qualified table in Product maintable like "Site items".
However I would like to have two non-qual field in that like 'Plant' and 'item#' which should be an unique combination.
I have tried to create a table(X) with the above two fields with display and another table (Y)that uses the table X for lookup (site-item) so as to make it dispaly and unique both. However when i am using this Y table as a lookup for the qualified table(site items) , not able to load data.
Error message:
"Import failed. Unable to find source column index for 'Site Item ID' field"
Another issue also not able to populate data for the qualified flds even if when able to load data without making a group unique field for this qualified table.
In MDM 5.5 sp4. Thanks in advance for any tips.
-reo

Hi Beena,
In the above post of mine I suggested you to use STRING data type.
As you are telling that when creating TABLE MAINTANENCE GENERATOR you are
getting an error saying that " Datatype STRING is not supported ". I tried this, what you said is right.
After your reply I did research on this and I also met my heads,
The conclusion is IT IS NOT POSSIBLE TO GENERATE TABLE MAINTANENCE for the table which is using STRING type. At last I can give you one suggestion, i.e., In the short text of that field write STANDARD TEXT name.So that whenever you want, go to this standard text, but the problem is you have to maintain it manually.
Reward all helpful answers.
Regards,
V.Raghavender.

How to add record in Qualified table using MDM Java API

Hi experts,
I am trying to add a record into a Table.
but I am facing the problem in setFieldValue method.
//Getting Field-ID to pass in setFieldValue() method.
FieldId[] fields = new FieldId[6];
 fields[0] = repSchema.getFieldId("GTINs", "Description");
 fields[1] = repSchema.getFieldId("GTINs", "Unit_Descriptor");
 fields[2] = repSchema.getFieldId("GTINs", "GTIN");
 fields[3] = repSchema.getFieldId("GTINs", "Alternate_Item_Classifications");
 fields[4] = repSchema.getFieldId("GTINs", "Country_Of_Origin");
 fields[5] = repSchema.getFieldId("GTINs", "Bar_Coded");
Record rec = RecordFactory.createEmptyRecord(mainTableId);
rec.setFieldValue(fields, );
but I am not getting how to assign the value to these fields using MDMvalue Interface.
Can anyone provide me the code sample or Code flow so that I can do this.
Plz help me it'll be great help for me.
Thanks
Tarun
Edited by: Tarun Sharma on Feb 4, 2008 11:39 AM
==========================================================================================
Hi Gurus
I found the way to add the MDMValue in setFieldValue Method.
we can set like this:
setFieldValue(<fieldId object like fieldId[], <MdmValue like this> new StringValue("ABC"));
Now I am facing problem in adding value to lookup flat table.
According to the setFieldValue method we can assign the loookup like this:
setFieldValue(<fieldId[0]>, new LookpValue(<here we have to pass the recordID of lookup table>);
so I want to know how I can pass the recordId of lookup table here.
Please suggest.
Thanks
Tarun Sharma
Edited by: Tarun Sharma on Feb 4, 2008 3:15 PM
Edited by: Tarun Sharma on Feb 4, 2008 3:25 PM
Edited by: Tarun Sharma on Feb 8, 2008 6:58 PM

Hi Andrea,
I tried your suggestion but now i am getting Type Mismatch Error.
Please suggest me what I can do?
//TableId for Lookup[Flat].
TableId lookupTableId = repSchema.getTableId("Return_Goods_Policies");
FieldId[] ReturnGoodsPolicyTableIdFields = new FieldId[1];
ReturnGoodsPolicyTableIdFields[0] = repSchema.getFieldId("Return_Goods_Policies", "Name");
Record recLookup = RecordFactory.createEmptyRecord(lookupTableId);
try{
recLookup.setFieldValue(ReturnGoodsPolicyTableIdFields[0], new StringValue("New_Brand"));
}catch(Exception ex){
System.out.println(ex);
//Creating Record in Qualified Table - Request Details
CreateRecordCommand createLookupcommand = new CreateRecordCommand(simpleConnection);
createLookupcommand.setSession(session);
createLookupcommand.setRecord(recLookup);
createLookupcommand.execute();
//Getting the recordId of Lookup record.
RecordId lookupRecordId = createLookupcommand.getRecord().getId();
//Table Id for Qualified table.
TableId qualifiedTableId = repSchema.getTableId("Ext_Hardlines");
FieldId[] ExtHardlinesFields = new FieldId[3];
ExtHardlinesFields[0] = repSchema.getFieldId("Ext_Hardlines", "Name");//Text
ExtHardlinesFields[1] = repSchema.getFieldId("Ext_Hardlines", "Pieces_Per_Trade_item");//Integer
ExtHardlinesFields[2] = repSchema.getFieldId("Ext_Hardlines","Return_Goods_Policy");
Record recQualified = RecordFactory.createEmptyRecord(qualifiedTableId);
try{
recQualified.setFieldValue(ExtHardlinesFields[0], new StringValue("Qualified Value"));
recQualified.setFieldValue(ExtHardlinesFields[1], new StringValue("Qualified Description"));
recQualified.setFieldValue(ExtHardlinesFields[2], new LookupValue(lookupRecordId));
}catch(Exception ex){
System.out.println(ex);
//Creating Record in Qualified Table - Request Details
CreateRecordCommand createQualifiedCommand = new CreateRecordCommand(simpleConnection);
createQualifiedCommand.setSession(session);
createQualifiedCommand.setRecord(recQualified);
createQualifiedCommand.execute(); I am getting this Type match here, but i m not getting what mistake i did.
RecordId qualifiedRecordId = createQualifiedCommand.getRecord().getId();
//Adding to Main Table
TableId mainTableId = repSchema.getTableId("GTINs");
FieldId[] gtinsFields = new FieldId[1];
gtinsFields[0] = repSchema.getFieldId("GTINs","Ext_Hardlines");
Record recMain = RecordFactory.createEmptyRecord(mainTableId);
//Adding the new record to Qualifed Lookup value and setting the Yes Qualifiers
QualifiedLookupValue qualifiedLookupValue = new QualifiedLookupValue();
qualifiedLookupValue.createQualifiedLink(qualifiedRecordId);
try{
recMain.setFieldValue(gtinsFields[0], new QualifiedLookupValue(qualifiedLookupValue));
}catch(Exception ex){
System.out.println(ex);
CreateRecordCommand createCmd = new CreateRecordCommand(simpleConnection);
createCmd.setSession(session);
createCmd.setRecord(recMain);
createCmd.execute();
Could you help me out?
Thanks
Tarun

SRM-MDM Catalogue Search UI - Qualified table search

Hi,
We are having the following situation:
- We have a catalogue of articles
- We have to tie an article to a location, in addition to a location-specific parameter.
- Exampe:
Article A is tied to location A, parameter A
Article B is tied to location B, parameter B
Article C is tied to location A, parameter B
- The way to solve this in MDM is to use the qualified table. I have created one where:
Location = non-qualifier
parameter = qualifier
I want to make this searchable in the SRM-MDM search UI.
The user should be able to choose one Location, and then one parameter tied to that Location, to view relevant articles.
This is no problem using SAP Portal with MDM. But how can we realise this using SRM-MDM search UI?
I have tried, but can only get a drop down or text search on the non-qualifier field.
Can anyone please help? Is this even possible?
KR;
Thomas

Hi Thomas,
Is there any possibilities to configure/add code to the search UI, or is this completely locked for customization/altering through code? Unfortunately, I feel it is standard and we can not customize it.
There is no issue in your design but if your location as well as parameter has certain(limited) number of values only. You can create location field in MDM Main table which is lookup to Locations Flat table and similarly for Parameter field lookup to Parameters table rather than using Qualified table. As you can set lookup/Text field search only, so you can set these two fields in your search criteria. where first you search for Location say US it will search records with US location and when you further give search according to parameter it will further filter(navigate) records based on both Location and parameter, just a thought came which i feel to share with you, try it if it helps you.
Regards,
Mandeep Saini

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

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

How to replace a qualified table with Tuple

Hi Experts!
I have a Qualified table woth 2 non qualifiers,which refer to 2 lookup flat table and one text field which is Qualifier.
Now I want to replace this design with tuple.Please give me steps to do so and also how is the linking of field relation maintained in Tuple.
Thanks
Ravz

Hi Ravz,
Please refer the complete section 5. Migrating from Qualified Lookup Table to Tuple
Here, must check Page No 48/58 example for converting Qualified tbale to Tuple. It will solve your problem.
Sample: Manufacturer Part Number (MPN) in standard Products repository
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80765a21-78f3-2b10-74a2-dc2ab57a1bd2?quicklink=index&overridelayout=true
Regards,
Mandeep Saini

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

Calculated field in qualified table

Hello
I have created three very simple calculations i qualified tables. The calculated field as well as the fields that make up the calculation are qualifiers.
None of the calculated fields are updated!
I have tried to hit the recalculate button and calculated fields in the main table work without problems.
Is this a known limitation? What can I do to trigger the update?
BR
/Alexander

Hi,
This is not the case.
Suppose in Qualified table, you have 4 fields one Non-Qualifier and three Qualifiers say FNAME, LNAME and FULLNAME all of type text.
Now for Qualifier Field FULLNAME i define Property Calculated = Yes and In Calculation Expression I write as:
CONCAT(FNAME,LNAME)
So on updating Qualifiers Value value of Qualifier Calculated field FULLNAME get updated.
Suppose intially for a record i have qualifiers value as
FNAME LNAME
Mandeep Saini
FULLNAME = Mandeep;Saini
when i update value for these two qualifiers for the same record
FNAME LNAME
Alexander Isacson
then value in for Qualifier field FULLNAME get updated to Alexander;Isacson
i tried this and it is working fine.
Hope it will Help you,
Rewards if found Useful....
Mandeep Saini

Issue creating qualified tables in MDM 5.5 SP04 Console

Try the following:
1) Make sure you are using SP04 Patch 1 (Build 5.5.33.13)
2) Unarchieve one of the supplied business content repositories (Eg. Customer, Material, etc).
3) Create a flat lookup table
4) Create a qualified table with only one field: Field type lookup flat referencing the flat lookup table created in step 3, non-qualifier, display field.
5) Create a new field in main table, type qualified multi-value, referencing the qualified table created in step 4.
6) Load the repository
7) Login to repository with data manager
8) Create 1 entry in lookup table created in step 3
9) Create 1 entry in main table, also creating 1 sub-entry in qualified table, save the record with SHIFT-ENTER
10) Make sure the record was saved, including qualified table entry
11) Close data manager
12) Open data manager again
13) Select your record and try to go in to the qualified sub-entry
In my case this produces data manager to crash.
This does not happen for qualified tables created in SP03 and updated to SP04, only for tables created directly in the SP04 console.
Please let me know if everybody is having the same problem.

Hi, Jorge,
I have MDM5.5 SP4 P1 HF1 and followed your steps (except in step 4 (THANK YOU for numbering them), I have more than one field.) At step 13, I selected my record and to my amazement the record was there but my qualified table data was gone. And I then performed your step 14, and opened the qualified lookup table, and again to my amazement the console crashed.
This definitely appears to be a bug and you should report it. I will also see if I can ask around for other solutions.
Kristin

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

How to enforce unique records in a Qualified Table

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 a Unique in the console but i can still add duplicate records.

Hi Tammi,
Don't expect to get many answers from this forum, which is Business Process Expert General.
Your question sounds more like an ABAP problem. Actually, it seems to have nothing to do with SAP; it really sounds more like a general programming problem.
You will probably have better luck in one of the ABAP forums, maybe
ABAP Development
Good Luck,
DB49

OCI mapping 2 Qualified tables

Is it possible that 2 qualified tables can be OCI mapped to the same set of fields on requistions page?
We are storing Material Master information in one Qualified table and Calalog information in another Qualified table. The end user can EITHER select Material Master information OR Catalog information, add it to the shopping cart. But, when the items from shopping cart are brought back to the Requistion page, it populates the same fields.
Can it be achieved. Any Ideas.
Thank you guys.
Shai

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

Qualified tables

Hi, due to characteristics of our implementation we need a qualified table for mails. The standard one can be used but i have a problem, i need a restriction for avoiding duplicated records and for now, i´ve not got the right key.
I.E.
ADDRESS TYPE: non qualifier. Unique field
MAIL TYPE: Qualifier . Unique field.
mail address: qualifier.
I need to get the structure below with one record for value like this:
add type:
Standard
mail type: KEY1
Mail address: [email protected]
but if trying to create a new record with the same keys but with the different mails it succedes thing that it´s what i don´t need. Does anyone know how to fix those values, i can´t have any duplicates and i can use other table type as needs to be syndicated as qualified.
Thanks in advance.

Hi Antonio - Have one quick question on your question...to understand it better..
do you mean to say that you are creating records like the following...
Ex1 :
Standard,Key1,[email protected]
Standard,Key1,[email protected]
or Ex2 :
Standard,Key1,[email protected]
alternative,Key1,[email protected]
or Ex3:
Standard,Key1,[email protected]
Standard,Key1,[email protected]
which one of the above examples is ok and which one is not.
Cheers,
Aravind

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

Qualified Tables Problem

Similar Messages

Maybe you are looking for