Qualified table concept

Hi,
I want to discuss, the concept of Qualified table in MDM 5.5.
Now, in my repository I have main table Business Partner which has a Lookup field Tax Number which is Lookup(Qualified-Flat) (multi-valued).
There are 2 fields in this table which are both Display field.
Tax Number is a Qualifier and Tax Number Type is Non-qualifier.
Now, for a record in Business Partner in Qualified Lookup field Tax Number, there are 4 values.
Tax Number Type| Tax Number
Permanent | 840987
Temporary | 432
Temporary | 432
Permanent | 5432
Now, according to Qualified table concept: For each association of Business Partner Record with Tax Number Type: Permanent or Temporary.
There should be a Tax Number as Qualifier. But it need not be unique. Then, the significance is, it as an association with the Tax number type.
Now, if we see from MDM point of view: The non-qualified value need not be duplicate.
So, my data is wrong but the values are Ok.
Regards
Kaushik Banerjee
Edited by: Kaushik Banerjee on Oct 14, 2008 12:46 PM

Hi Kaushik,
Tax Number Type| Tax Number
Permanent | 840987
Temporary | 432
Temporary | 432
Permanent | 5432
Two things I would like to share:
- When you select any data to be fit for saving in a qualifier table,you need to understand it very well.As given in your above example,Tax no type is the non-qualifier determing the Qualifier tax num.As far as i understand this data,it would not be absolutely correct to say that the Tax num type alone can determine the tax num.You can have all tax numbers either Permanent or temporary,but this alone cannot determine the tax number values.what i mean is that by jsut classifying the number as permanaent or temporary you cannot say the num to be so and so.In thsi case if you are saving this kind of data in a qualified table you may need another field to detrrmine the Tax num and the combination of the two of non qualifier field will decide the qualifier for all incoming records.
- When you import the qualified tabe,you will map the non qualifier.In this case out of your 4 non qualifier values only 2 will enter MDM as the matching field is tax num type and there are only two distinct values in this field.So in that case you will have two unique non qualifier values which will determine the qualifiers accordingly for all main table records
Hope It Helped
Thanks & Regards
Simona Pinto

Similar Messages

What is qualifier table and where exactly we will use that

Hi experts,
I have one query regarding qualifier table. where exactly we use qualifier table. can u give me any realtime situation where we use qualifier table.
Regards
Ravikumar

Hi Ravikumar,
A qualified table is a special kind of lookup table. It can be used to efficiently store complex relationships between a main table record and one or more lookup table records that contain various types of additional information.
Go Through Important Links
/people/pooja.khandelwal2/blog/2006/03/29/taming-the-animal--qualified-tables
/people/community.user/blog/2006/12/20/so-is-that-the-qualifier-or-the-non-qualifier
A qualified table stores a set of lookup records, and also supports qualifiers, database u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record.
Qualified lookup tables are used to store the values of Two types of fields Qualifiers and non Qualifiers.
Qualifiers are the fields whoes values changes based on the values of other fields called Non Qualifiers.And are associated with the main Table Records.
Non Qualifiers are only part of Qualified lookup Tables.
In Data Manager QualifiedLookUp Tables appear in the lower right Part.
For example in your main table supoose you have an Employee Repository that maintains employee information (Name,Telephone,Address etc).One employee can have sitting arrangement on different office locations.
Then if Location is your main table field in that case for 10 places you have to make 10 seperate entries of One Employee name with different locations,that will unnecessarily increase the records of your main table and also duplicate for Employee name field as well.
To resolve this make a look up field location in main table for qualified lookUp Table Locations.
In Locations table create a Non Qualifier field OfficeADD(lookup flat )for Officelocation table .
And create two more fields DeskNo. and Telephone No.(both as qualifiers)for every location the desk no. and telephone no. will be different.
In Officelocation table has one field Name which contains address of diffrent locations.
Now according to the Qualifier and Non Qualifier concept
In main table for an Employee say Ravindra you can go qualifiedLookUp table and select a value for OfficeADD(a non qualifier) and set valus for Desk no. and telephone no.(Qualifiers) as well.
Reward if Helpful.
Vinay Yadav
Edited by: Vinay Yadav on Jun 23, 2008 12:54 PM
Edited by: Vinay Yadav on Jun 23, 2008 12:58 PM

Not able to see data in the qualifier table of the main tbl , Data Manager

Hi,
I have an issue of not able to see the data of two qualified table after populating them.
It is in mdm-5.5 ps4.
When populating data first time ,it shows up in those two table slots in the right side of the Data Manager.
However subsequently it does not show up in those slots , only by right click on the table and selecting "View/edit", the window pops up where those data shows up.
However unlike other qualified tables the data does not showup automatically for these two tables.
Appreciate any suggestion or feedback on this.
regards,
-reo

You may have checked the Filter Check Box next to the Qualified Lookup cell in Data Manager, when the current table is the Main Table.
You use the Filter Checkbox to limit the qualified table records by the current search selections.
Secondly, you have see if there are any Qualified Links to the main table record you are viewing.
If not, create the Qualified links in Data manager, for the main table record and the Qualified Table Record.
Once this is done, you will see the Display fields of the Qualified table for which the links exists for the given main table record.
Message was edited by:
Adhappan Thiagarajan

Get Qualifier value from Qualified table

Hi,
I am trying to get all the qualifier value for a qualified table. What is the best way to do it. Can I use QualifierSearchDimension to search for all the qualifier value.
Re: Lookup [Qualified Flat] type field how to use as a query condition? link gives us a way to do this , but it talk about getting the non - qualifiers only , so How can we get the qualifier values.
The link Search Qualifier Fields : MDM Java APIs gives us a way to this , but it is using old Java API , does anyone know how to do it using MDM API SP06.
Thanks and Regards,
Subhasis

Hi Subhasis,
The Search API's will only search for a particular value in the qualified tables. In order to read all the qualifier and non qualifier for a record, please follow the below mentioned steps.
Assuming 'rec' is the variable that holds the reference for the current record.
MdmValue lookUpVal = rec.getFieldValuel(<Field Id of the field>);
com.sap.mdm.valuetypes.QualifiedLookupValue val = (com.sap.mdm.valuetypes.QualifiedLookupValue) lookUpVal;
// Get the total number of qualified records present for that field
int size = val.getValuesCount();
// Iterate through each qualified record to fetch the details
for(int i=0;i<size;i++){
 MdmValue nqVal = val.getValue(i);
 if(nqVal != null){
 MdmValue incVal = val.getQualifierFieldValue(i,<Field Id of the qualifier field value>);
Regards,
Ponraj M
Edited by: Ponraj M on Jul 10, 2009 10:12 AM

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 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

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

Duplicate keys possible in qualified tables.

Dear experts,
In short; when defining a qualified table in a repository you can define one or more fields as key-fields. This only prevents you from adding a the reference twice to the pre-selection but still allows you create more than one instance of this key within the same main table record.
For instance, if you have a material repository with material as key for the main table and you define a qualified table to represent the plant level data, you can still maintain more than one record for plant X in relation to material Y.
This results in data duplication and is a serious risk when distributing the data to subscribing systems.
The issue was reported through OSS and was explained to be a feature to allow multiple telephone number. etc to be maintained. No solution was provided.
We found this issue in our MDM system (MDM 5.5 SP05). Can you help us find out whether or not this issue was encountered at other clients/projects and if there is a solution? If you have the same issue, can you please let me know what version and support pack youu2019re on?
We would appriciate any help on this.
Thanks in advance.

Hi,
You are right......... This how Qualified Table works.
Check this:
Re: Material master for same Sales Org
Thanks,
Maheshwari

Can we Sum the Values in the Qualified table Fields??

Hi All,
I have a requirement where..Each material has multiple UOM's, So designed it as Qualified Table.
UOM is a Qualified table.
UOM Type is NON Qualifier.
Weight Qualifier - Integer field
Length Qualifier - Integer Field
Now in main table there is a field called Net Weight.
I need to write a validation which checks Whether Sum of ''Weight'' in Qualfied table is Equal to ''Net Weight'' for that record.
So if there are 5 UOM for 1 material, then the validation should check whetehr the Sum of all 5 Weights in QT is equal to ''Net Weight'' Field in Main table!!!
Did anyone faced a similar issue, If yes How did you solve it!!
Please Help!!
KR
John

Hi John,
Try this:-
Net Weight = SUM(UOM.Weight)
Here SUM is the standard function thats u need to select from list of functions.
Please let us know if it works..
Thanks,
Mahi

Is it possible to change Overridden Qualified Table Name in code?

Hi,
Environment: Crystal Reports XI R2, 2008, Sql Server 2005
I had about 1000 reports to change. Several changes are the standard, so i had created several tools that i use to make that change in all reports.
However i can't find a way to change Overridden Qualified Table Name and remove the Catalog and Owner information, so it seems that the only way is using CR editor and make these changes one by one... not a good idea!
Does anyone managed to do this???
Thanks,
Carlos Crespo

Hi,
Thanks for your input.
I use CR in two ways: 
a) to develop reports to use in our projects - In this case we don't have major issues with this, and we chance the location of the database in code at runtime; 
b) to develop reports to use in ERP softwares from third parties - and here we are having some issues - not always but some times. 
We know that they change the location of the DB in code also (no specific info however). 
An example:
We change a report on my development PC, against a DB called TEST; 
We send the report to the customer, who runs it on its system, trying to read data from a db XYZ; 
If the customer also has a TEST db, in some reports the system reads some tables from XYZ, but others he gets the info from TEST db. In one example our customer has an invoice where all data was from the production DB, except the COUNTRY table that was read from a copy of the TEST db. After TEST was removed, the data was read from the production DB.... 
And to get you an idea: we're talking about hundreds of customers - some of them have 600 SQL DBs in the same server (small Dbs, around 70/500 MB in size) - so we can only hope that the user doesn't create a DB with the same name we used to develop the report... 
And what i don't understand is WHY we can define Overridden Qualified Table Name in same tables, and not in others. 
Example: 
One of the reports has 6 sub-reports. 
I can define Overridden Qualified Table Name in the main report (except for a View), and in 2 of the subreports - but not in the other 4... 
The zero in front of the table name shows a table where Overridden Qualified Table Name has been defined, and the original Catalog and Owner was removed - the 2 shows a table where Overridden Qualified Table Name has been defined, but the original catalog (PRITESTEDOC75) and owner (dbo) remains. 
I even tried to export the sub-reports, change this info in the sub-report, and then import it again (a suggestion from Business Object support), but it doesn't work... 
Main Report: 
Artigo 0 
CabecDoc 0 
LinhasDoc 0 
ModosExp 0 
Clientes 0 
CondPag 0 
DocumentosVenda 0 
Moedas 0 
MoradasAlternativasClientes 0 
OutrosTerceiros 0 
ArtigoIdioma 0 
Paises 0 
ArtigoLote 0 
TDU_CC_INFODOCVND 0 
Clientes_Fac 0 
Paises_Fac 0 
V_Entidades 2 PRITESTEDOC75 dbo (V_Entidades is a View, not a Table) 
Sub-Report 1: 
GCP_VND_CalculaTotaisDocumento 2 PRITESTEDOC75 dbo (GCP_VND_CalculaTotaisDocumento is a SP) 
Sub-Report 2: 
CnfTabLigCBL 2 PRITESTEDOC75 dbo 
Sub-Report 3: 
LinhasNumSerie 2 PRITESTEDOC75 dbo 
Sub-Report 4: 
ResumoRetencao 0 
Historico 0 
OutrosTerceiros 0 
EntidadesPublicas 0 
Clientes 0 
Sub-Report 5: 
1 ResumoRetencao 0 
2 Historico 0 
3 OutrosTerceiros 0 
4 EntidadesPublicas 0 
5 Clientes 0 
Sub-Report 6: 
1 ResumoIva 2 PRITESTEDOC75 dbo 
2 CabecDoc 2 PRITESTEDOC75 dbo 
3 Iva 2 PRITESTEDOC75 dbo 
Best Regards, 
Carlos Crespo

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

Qualified Table getting a blank row in MDM 7.1

Hi All,
We are implementing MDM 7.1 and have created custom repository with multiple main table. We have also few qualified tables.
There is only one non-qualifier in all the qualified tables. The values are u201CAu201D (Active) or u201CIu201D (Inactive).
For example:
We have a qualified table called company group, where we store the groups to which a company belongs.
The import is through import sever and xml file is the input.
When there are no values for the group at the source system, we will not receive the XML tags for the group and we will receive xml tags for other data. The non-qualifier value u201CAu201D will also be part of the company group values from source.
The expected functionality is import server should ignore the company group table in total while importing through import server, as there is no xml tags for group.
We are getting a qualified row with only non-qualifier value u201CAu201D and rest of the values as blank.
Kindly provide suggestion to resolve this.
Regards,
Arul Manickavel

Hi Arul
Try using "Update" or "Replace" in the Import Map for the Qualified field mapping's "Set Qualified Update" option.
Regards
Varun

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

Qualified table concept

Similar Messages

Maybe you are looking for