Error in Import to Qualified lookup table

A qualified look up table has 1 Non qualifier and 8 qualifiers.Non qualifier values are X and Y.Records were imported from excel sheet to QLT.
In the first trial, for a NQ 'X' all the qualified values of Y have got imported and vice versa .
Now, I need to replace , Value X with Y in non qualifier and retain all Qualifier values. While doing this, a new record is getting appended in the QLT with NQ 'Y'.
How can record appending in QLT be avoided by replacing only Non Qualifier values?
Need very quick help on this please.
Regards,
Vinay M.S

Hi Vinay,
Set the qualified update to Replace for the non qualifier in the destination fields in Map Fields/
Values pane.
Best Regards,
Silpa Chillakuru

Similar Messages

Qualified lookup table

Hi Guys,
Can you tell me the steps to be followed for importing and syndicating qualified lookup table .
Thanks,
MS Reddy

Hi,
1. Import all the lookup tables used in Qualified table.
2. Import qualified table data along with main table data only. For more than one qualified table record you should have repeated main table record.
E.g.
Qualified Table - Price Information
Lower Bound
Purchasing Info Record ID
Purchasing Organization
Amount
Currency
First three fields are the non-qualifiers amongst which Purchasing Organization is the lookup field. So you need to first populate this field.
Now your main table record is
Supplier     Supplier Part Number     Short Description     Product ID     Service Item     Lower Bound Purchasing Info Record ID     Purchasing Organization     Currency     Amount
AGENCY01          1000               metal processing     IBG-100               False     1     5300000018     Mumbai Purchase Org     Indian Rupee     100.00
1. Map all the main table fields
2. Identify the Display fields of your Qualified table, if your qualified table has more than one Display field then map the fields with the fields marked as D in destination structure e.g. in above given table all the three non-qualifiers are the display fields then mark Lower Bound with the D   Lower Bound field, similarly map the other display fields
3. Select all the Display fields at source side, right click and select Create Compound field. This will combine your input fields and automatically map them with Qualified field.
4. Map the qualifiers
5. Select the unique fields in Matching fields tab and execute the import.
When you syndicate data containing qualified links, it will create the number of output records depending on the number of qualified links.
Regards,
Jitesh Talreja

When to use qualified lookup table?

Hi all,
I am confused with the qualified lookup table and lookup table, for the situation that a company has more than one contact person, I created a table "contact person", which has following fields: first name, last name, phone number, email address.
Questions:
1. should I set "contact person" as a lookup table or qualified lookup table?
2. if to be set as qualified lookup table, which field should be qualifier field? what is the difference between qualifier field and non-qualifier field?
your reply will be very appreciable
Bin

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.
Check the foll links
/people/pooja.khandelwal2/blog/2006/03/29/taming-the-animal--qualified-tables
/people/avi.rokach/blog/2006/11/14/using-mdm-55-for-data-quality-analysis
MDM data modelling guide
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d4211fa-0301-0010-9fb1-ef1fd91719b6
How to import Qualified tables.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/abe914fa-0301-0010-7bb1-d25c2a4bb655
Also this one.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/792f57b7-0a01-0010-f3b6-881269136a83
Please reward for the same.

Insert a record in Qualified Lookup Table

Hello everyone,
I need code to insert a record in Qualified Lookup Table where the non-qualifier is a record of type Country. Other fields are qualifiers.
I tried using QualifiedLookupValue.createQualifiedLink(). However, this only helps to insert in the qualifier values, how can I insert the non-qualifier (Country) value?
Any idea?
Many thanks in advance,
Baez

Hi guys,
Maybe the answer comes late but i'm recently working on this and the API works for me to create and update qualifier values.
Suppose recordMain is the main record, fldQFT is the qualified lookup field in main table, fldQualifier is the qualifier field in QFT table.
To add qualifier value you can use:
QualifiedLookupValue qualifiedLookupValue = new QualifiedLookupValue();
int index = qualifiedLookupValue.createQualifiedLink(recordMain.getId());
qualifiedLookupValue.setQualifierFieldValue(index, fldQualifier, MdmValue);
recordMain.setFieldValue(fldQFT, qualifiedLookupValue);
To update qualifier value, use:
QualifiedLookupValue qualifiedLookupValue = (QualifiedLookupValue) recordMain.getFieldValue(fldQFT);
qualifiedLookupValue.setQualifierFieldValue(index, fldQualifier, MdmValue);
recordMain.setFieldValue(fldQFT, qualifiedLookupValue);
Regards,
James

Qualified Lookup Table in Webdynpro Content Generator

I am trying to build a user interface with the webynpro component generators from the business content deployed on the portal. The problem I face is with qualified lookup tables. From the main table, there is an embedded table which contains the qualified lookup table. I can press the "edit" button to open a pop-up window which shows the details of the qualified link. Unfortunately, on MDM 7.1 SP05, the pop-up window contains a table at the top of the screen that forces the entire window to span the width of the table, which will go on quite far because I have about 20 fields in my qualified lookup table. Below I can enter the values for the individual fields, but it is difficult to use because you have to scroll all the way to the right to select drop down values. Is there a way to remove the summary table from the pop-up window for qualified lookup tables? I havent seen an option in the UI config.

Apparently you can configure the fields that are shown in the pop-up window, but it also limits the fields that are displayed on the iView of the main table.

Updating a qualifier value of qualified lookup table failed

Hello,
I am trying to update a qualifier value of qualified lookup table.
I have written the method attached to this email.
I am not able to modify a qualifier field, that "Installation instructions DAR Update" field of "Vendor Details" table with this method call. Is there anything I am missing or not doing correctly?
Also, I noticed that in SP6 API documentation, this line in section of ModifyRecordsCommand:
Note: Qualifier values is currently not supported by this command. This command simply ignore qualifier values passed in.
First I have used this method failed. After I saw this, I tried to use ModifyRecordCommand but no success still.
I am copying my method content here. qlv1 and qlv2 is geeting new value after setQualifierFieldValue.
It will be highly appreciated if you can help me.
                boolean isUpdated = false;
          final MdmValue mval = record.getFieldValue(qualFieldID);
          qlv = (QualifiedLookupValue) mval;
          QualifiedLinkValue[] qlinkvals = qlv.getQualifiedLinks();
          for (int j = 0; j < qlinkvals.length; j++) {
               qlinkval = qlinkvals[j];
               qrec = qlinkval.getQualifiedLookupRecord();
               tabId = qrec.getTable();
               qfields = qlinkval.getQualifierFields();
               vdrec = getTSVal(tsVals, qrec);
               for (int k = 0; k < qfields.length; k++) {
                    fieldId = qfields[k];
                    fieldValue = qlinkval.getQualifierValue(fieldId).toString();
                    mstr = mdmHandle.getSchema().getField(tabId, fieldId).getName();
                    fieldName = mstr.get(MDMBase.LANG);
                    if (!(vdrec.containsKey(fieldName)))
                         continue;
                    String curTSVal = fieldValue;
                    String darTSval = vdrec.get(fieldName);
                    // If the dar updated value has different timestamp value,
                    // then it means MDM have changed the value after we sent the
                    // last export to DAR.For this case, we won't change status flag
                    if (!(darTSval.equalsIgnoreCase(curTSVal)))
                         continue;
                    FieldId updateFieldID = tsUpdateFields.get(fieldName);
                    //test
                    FieldId iid = tsUpdateFields.get("Parts Breakdown Timestamp");
                    //test
                    try {
                         MdmValue mvalTrue = MdmValueFactory
                                   .createBooleanValue(true);
                         qlv.setQualifierFieldValue(j, updateFieldID, mvalTrue);
                         //test
                         qlv.setQualifierFieldValue(j, iid, mvalTrue);
                         String qlv1 = qlv.getQualifierFieldValue(j,updateFieldID).toString();
                         String qlv2 = qlv.getQualifierFieldValue(j,iid).toString();
                         QualifiedLinkValue qlv11 = qlv.getQualifiedLinks()[1];
                         logger.info(qlv1":"qlv2);
                         //test
                    } catch (IllegalArgumentException e) {
                         // TODO Auto-generated catch block
                         e.printStackTrace();
                    isUpdated = true;
               if (isUpdated){
                    qlv.setCompleteSet(true);
                    mdmHandle.modifyRecord(record,true);
                    mdmHandle.modifyRecord(qrec,true);
Regards

Apparently you can configure the fields that are shown in the pop-up window, but it also limits the fields that are displayed on the iView of the main table.

Create key mapping using import manager for lookup table FROM EXCEL file

hello,
i would like create key mapping while importing the values via excel file.
the source file containing the key, but how do i map it to the lookup table?
the properties of the table has enable the creation of mapping key. but during the mapping in import manager, i cant find any way to map the key mapping..
eg
lookup table contains:
Material Group
Code
excel file contain
MatGroup1 Code System
Thanks!
Shanti

Hi Shanti,
Assuming you have already defined below listed points
1) Key Mapping "Yes" to your lookup table in MDM Console
2) Created a New Remote System in MDM console
3) proper rights for your account for updating the remote key values in to data manager through import manager.
Your sample file can have Material Group and Code alone which can be exported from Data Manager by File-> Export To -> Excel, if you have data already in Data Manager.
Open your sample file through Import Manager by selecting the remote system for which you want to import the Key mapping.
(Do Not select MDM as Remote System, which do not allows you to maintain key mapping values) and also the file type as Excel
Now select your Soruce and Destination tables, under the destination fields you will be seeing a new field called [Remote Key]
Map you source and destination fields correspondingly and Clone your source field code by right clicking on code in the source hierarchy and map it to Remote Key if you want the code to be in the remote key values.
And in the matching criteria select destination field code as a Matching field and change the default import action to Update NULL fields or UPDATED MAPPED FIELDS as required,
After sucessfull import you can check the Remote Key values in Data Manager.
Hope this helps
Thanks
Sowseel

Java error when importing info into a table

Hi I am trying to import data into a table from a csv file. I Log into the Database via Oracle Enterprise Manager 10G. I then goto Administration and Import user file. I then give the username and password of the user on the Server. I choose my csv file and click next. I then Choose my Table and click next, this is when I get an error..
500 Internal Server Error
java.lang.ArrayIndexOutOfBoundsException: -128
     at oracle.sysman.emo.util.UIXDataSource.initialize(UIXDataSource.java:322)
     at oracle.sysman.emo.util.UIXDataSource.<init>(UIXDataSource.java:188)
     at oracle.sysman.emo.util.data.LoadPreviewDataDS.<init>(LoadPreviewDataDS.java:58)
     at oracle.sysman.emo.util.data.LoadBean.initPreviewDataTable(LoadBean.java:3002)
     at oracle.sysman.emo.util.data.LoadBean.validateFileFormatPage(LoadBean.java:1920)
     at oracle.sysman.db.util.data.LoadController.validatePage(LoadController.java:757)
     at oracle.sysman.db.util.data.LoadController.onSubmitForm(LoadController.java:707)
     at oracle.sysman.db.util.data.LoadController.handleGoto(LoadController.java:779)
     at oracle.sysman.db.util.DBJobController.handleEvent(DBJobController.java:821)
     at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:376)
     at oracle.sysman.db.adm.RootController.handleRequest(RootController.java:169)
     at oracle.sysman.db.util.UtilControllerResolver.handleRequest(UtilControllerResolver.java:128)
     at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:688)
     at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:291)
     at oracle.sysman.eml.app.Console.doGet(Console.java:285)
     at oracle.cabo.servlet.UIXServlet.doPost(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.sysman.emSDK.svlt.EMRedirectFilter.doFilter(EMRedirectFilter.java:101)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
     at oracle.sysman.db.adm.inst.HandleRepDownFilter.doFilter(HandleRepDownFilter.java:138)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
     at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:269)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:600)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
I do not get this error with other tables and this file only with this table. Any help would be greatly appreciated, let me know if more info is needed.

Thanks that did work out for me. However, I am still curious why I am getting that message in the Enterprise Manager. Well I was able to upload my info into the database and it was a better solution too.

Searching for Duplicates records in Qualified Lookup tables

Hi SDNers,
I would like to know,
How to find out how many records having duplicate records in Qualified Look Tables.
In Free form search or Drill down Serach.. I am select the particular Qualified Look up Table. After how can I find Duplicated reocrds.
Any Solution?
Thanks
Ravi

Hi,
If you want to find the duplicates present in qualified table then, you can go to qualified table in data manager and get to know the duplicates....else if you want to find the duplicate links to a record in main table, then you can write an expression in free form search to get the value of duplicate links. but that would be specific to a link value only..e.g. Country is your no qualifier, then in free form search, you can write an expression to get how many links are for USA.
Hope this clarifies your doubt...if not, please elaborate on the requirement.
Regards,
Arafat.

Error while importing LSMW (Errro in Table /SAPDMC/LSMCUST)

Hi Experts,
I was trying to Export and import a LSMW in quality system and came across with the below error. Any idea why it is happening. The recording, field mapping and conversion rules are not getting copied properly.
Errro in table /SAPDMC/LSMCUST
Br/Manas

Hi,
When you are exporting the LSMW click the recording name for the including the exporting. Field mapping you have to do after importing.
Regards
Sabu

Error while import objects:view or table

Action: Right click on views under the module tree. select import menu. select view checkbox. Click on view (trying to import view)
API2206:Connection to source failed.
ORA-02019:Connection descriptor for remote database not found.
The error is so obvious, but I can not figured out what's run on my setup. Can anyone help? Did I miss anything else? Thanks.
This project runs OK in owb 9i. I imported the mdl to owb client 10g.
Create location, connector, deploy and register to runtime on 10g instance OK. Create a runtime and connection through deployment manager is OK.
Property of this module is updated with the new location.Source for metadata import is through dictionary.

Hi,
Do you know what's the "connection descriptor" the error msg is referring to? I thought it may be the connector. But it's set OK.
Under the "connection" tab from the module property, I check the first checkbox, Oracle Data Dictionary, for Source for Metadata Import. It's working OK before.
Thanks.

Error while Importing Vendor Master records

I get the following error when importing vendor Master records into the MDM repositorry
Cannot import qualifiers because the qualified lookup field is not mapped.
I noticed that the file I'm importing contains 1000 vendors. However the qualified lookup table "PHONE" for the vendors contain only 388 records.
After I imported the records I found that there was only 389 records in the repository.
I'm using standard map provided by SAP.
I ran the import again but this time I unmapped all fields for the qualified update.
Now the Import Manager uploaded the remaining 613 records.
I would like to know whether how I can load 1000 records in one load rather than having to go through the file twice.
This is important since I want to use the import manager server for my loads.
Thanks
manoj

Hi Manoj,
Try the following options.
1. In the Import Manager, Select Configuration->Options
set <b>"Merge qualified links using matching qualifiers value to Off"</b>
2. In the Map Fields/Values tab in Import manager, select the qualified field in which you are trying to import, right clik on the field->select Set Qualified Update -> Update -> Select All available qualifiers into Matching qualifiers->
New Links- Create
Existing Links -> Update (All Mapped Qualifiers).
Hope this should solve your problem.
Thanks and Regards
Subbu.

Strange Errors from Import Server on Schema-based maps for repeating nodes

I have already posted one thread about this, but perhaps some more in-depth information is required:
We have uploaded our schema into the console, and have mapped the following multi-node file to it:
CUSTOMER <repeating node>
MDM_CUST (new Customer number returned)
CUSTOMER(mapped back from XI for RECORD MATCHING)
CREATE_DATE (text field)
CONTACT<repeating node>
    CONTACT_NO (RECORD MATCHING : NON-QUALIFIER)
    CONTACT_SAP_NO (QUALIFIER)
     [NOTE: There are other qualifers for CONTACT, but only this one
qualifier is being returned and is the only field that would and should be updated.
The other fields should be left alone. However, it appears to overwrite EVERYthing
with NULL other than these two fields. The CONTACT_NO is the sole qualifer on
the table. It is a calculated field that equals the Auto-ID that is also produced on
the table - but obviously not mapped.]
PARTNER<repeating node>
    CUSTOMER_NO (RECORD MATCHING : NON-QUALIFER)
    PARTNER_FUNC (NON-QUALIFIER - Code given to lookup from PARTNER_FUNCTION table which has Code and Desc)
    PARTNER_NO     (NON-QUALIFIER)
    DEFAULT_PARTNER_FLAG (QUALIFIER)
<CLOSE CUSTOMER NODE>
In the Customer main table, all records are matched on CUSTOMER. The CONTACT_NO non-qualifer is matched to the CONTACT qualified lookup table directly since it is the only available non-qualifier. For the PARTNER table, the three qualifiers are mapped and then a compound field is created to map to the PARTNER table entry.
We have the Configurations set at:
Default Multi-Valued Update: Replace
Default Qualified Update: Replace
Default Matching Qualifiers: None
Our record matching is: Create / Update(ALL MAPPED FIELDS) / Update(ALL MAPPED FIELDS)
When the map is reused, the repeating nodes are all recognized, be it one node or many. However, when the map is reused, it does not automatically map the values for many of the Partner fields (nor the compound field) though the fields are correctly mapped.
Also, when we attempt to use Import Server to automate the mapping, we use the mdis.ini set to
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
We get a very strange error saying that :
[code]Encountered a pre-SP4 map. The map needs to be upgraded to SP4.
Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map.[code]
Could it be that our MDM 5.5 SP4 is not compatible with schemas generated with XI v.7 SP9?
All of our MDM is 5.5 SP4. It makes no sense that we would get THIS kind of error. Also, I am questioning our combination of these and other configurations since it doesn't always seem to do what it should

Hi Donald,
this sounds good so far. Just a short hint: you've set "Default Qualified Update: Replace". This explains why Import server "appears to overwrite EVERYthing
with NULL other than these two fields.". The reason is the replace. A replace means that the old values are completely deleted and only the new incoming ones are stored. I'd suggest to use any of the Update possibilities.
Note: the definitions you set in in the record matching step are mainly for the new records in the main table! Records in qualified look ups are handled differently! If you open your map in Import Manager, switch to tab "Map Fields/Values". Select a field that is your non qualifier. Right-Click on it and choose "Set qualified update" from the context menu. Now you can define which qualifiers can be used for the qualified look up matching. And you can define as well what should happen with new and/or existing records.
Regarding the value mapping: do you use keymapping? Or do you use simple values only? Do you save the map everytime you add a new value mapping?
Regarding the issue "Encountered a pre-SP4 map. The map needs to be upgraded to SP4. Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map". This sounds very likely like a bug in MDIS and should be reported to SAP!
Hope that helps
Michael

Values of Non-Qualifiers (lookups) not auto-converting.

We've been trying to use Import Server to automatically import records (XML) that had data for qualified lookup tables. Apparently there is an issue with namespaces in both the schema that we mapped to and the source field.
After removing the namespaces, we now have an issue with the non-qualifier that uses a lookup table not automapping it's values and thus retaining the compound field at the Customer main level.
First, the Partner Function is mapped to the Partner Function flat lookup table. At this level, the value auto-converts and the green dot is visible to the left.
Second, at the Customer Partner qualified lookup, the Partner Function is again mapped to the Partner Function lookup. This time, however, the values do not automatically convert and the "AUTOMAP" button must be manually pushed for them to map. The other non-qualifiers (CustomerID, PartnerNum, PartnerSAP_ID) are also mapped and their values auto-convert (green dot).
Finally, at the Customer main level, all of the non-qualified field from the Customer Partner table are mapped and all auto-convert except for the Partner Function field. This requires us to manually push "Automap". Then, and only then, does it allow us to right click on one of the fields and create the compound field to map to the Customer Partner field. Again, the value mapping is not automatic but must be done manually.
This map is then saved and ImpMgr closed. When the IM is reopened with the same map, the compound field is not recreated due to the fact that the Partner Function values did not convert. Once these are redone manually, then and only then can the compound field be recreated and value mapped.
When this same map is used in the Import Server, the error is that the qualified fields cannot be mapped. This brings us back to the lookup fields not value mapping. Likewise, if this same file is opened in Import Manager mannually, and the map applied, it STILL does not convert the values and the Compound Field for the Qualified L/Up table is dropped.
We are using MDM 5.5 SP4 Patch 3.

Hello Christiane,
Yes, this is a very important point and I should have noted it in my original post. Yes, my Default Batch Handling settings are:
Yes - Automap unmapped values
Add - Unmapped Value Handling
Plus:
Replace - Default multi-valued update
Append - Deault qualified update
None - Default matching qualifiers
Also, in my mdis.ini file, my settings are:
Automap Unmapped Value = True
Unmapped Value Handling = Add
Always Use Unmapped Value Handling = True
It used to work when we were in SP4, Patch 2, but have since upgraded to Patch 3, Hotfix 2(?) and can't get it to work.
Thanks for helping!
Don

Inserting a record in qualified looup table

Hi All,
I am using MDM 5.5 SP6. I have table structure like this.
Table name:
Representative (main table)
Fields:
     Name          Text
     Age          Integer
     Voter ID     Text
     Gender          Lookup[flat]
     PostandLocation Lookup[Qualified](Multi-valued) --> It refers qualified table 'Post_and_Location'.
Post_and_Location (Qualified table)
Fields:
     Position     Lookup[flat]
     Location     Lookup[Hierarchy](multi-valued) --> It refers hierarchy table 'Locations'
Locations (Hierarchy table)
Fields:
     State          Lookup[flat]
     District     Lookup[flat]
     City          Text
Here, I need add representative details in main table 'representative' using Java API. In webdynpro UI, I will give Name, age,voterid,gender,position, city,district, state.
Here I am struggling that how to lookup hieararchy table value in qualified lookup table(Post_and_Location). How can I achieve this?.Please help me.
I am more happy to give more information regarding this, if anybody needs.
Thanks,
Venkatesh

Hi Bharti,
Thanks for your quick reply. Here I need more explanation on, how to lookup hierarchy table(Location) record in Qualified lookup table (Post_and_Location) using java API. I need more explanation in Java API regarding this.
Because, As per our scenario, Qualified table(Post_and_Location) have a field called 'Location'(type Lookup[Hierarchy](multi-valued)). It looks up Hieararchy table(Locations).
Here, while adding new representative in main table(representative), I need to lookup qualified table(Post_and_Location) record for the field 'PostandLocation' in main table(representative). And also, I need to lookup hierarchy table(Location) record for the field 'Location' in Qualified table.
If you get confuse, please check my table structure above in this thread. If you need more info, I will provide. Please help me to achive this.
Thanks,
Venkatesh

Error in Import to Qualified lookup table

Similar Messages

Maybe you are looking for