Qualified table search in MDM

Hello All,
I am trying to do drill down search in Data manager on qualified table.
when in search critieria i am selecting qualified table ,I am not getting all qualifiers in search tab.(we have 6 qualifiers and i am only getting 3 of them )
and in values as well when i am selecting say for
qualifier Value
country USA
if i am selecting this combination i am not getting any records whereas there are more than 1000 records of country USA .
any suggestions.!
Kunal

Hi Kunal,
Check the below statements from MDM Reference Guide and check whether you have designed the repository in the same way or not.
It permits drilldown search by qualifier lookup values even before you have selected a single qualified table record in the qualified lookup field search tab.
It permits free-form search by qualifiers (both lookup and non-lookup) when Sort Index is enabled.
In above statements "It" is nothing but when you enable the Cache property of qualifiers.
Kindly update us on your issue.
Regards,
Jitesh Talreja

Similar Messages

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

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 <b>IT IS NOT POSSIBLE TO GENERATE TABLE MAINTANENCE</b> 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.
<b>Reward all helpful answers.</b>
Regards,
V.Raghavender.

Search on a Qualify Table using MDM Webservices

Hello
I´m trying to use the standard MDM 7 webservice to search records in a Qualify Table and I´m having some problems.
When I try to search records in a non-qualify table, it works perfectly, but when I search on a qualify table, I get the following result:
repository_3001-Error executing Search Records on repository MY_REPOSITORY, error code , caused by Qualifier values are not part of a qualified lookup record
I´m filling the following fields:
parameters/query/criteria/manufacturer/LogicalOperation: AND
parameters/query/criteria/manufacturer/constraint/element1/value: (blank to return all records)
parameters/query/criteria/manufacturer/constraint/element1/expression Operation: CONTAINS
parameters/resultDefinition/fieldListType: ALL
..and the repository information...
Thanks.
Vitor Zaninotto

Solved..
I cannot use parameters/resultDefinition/fieldListType: ALL, I must set the non-qualifier fields only.

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

SRM MDM - Multiple hyperlinks import into qualified table

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

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

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

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

Qualified table - Text Normalized field

Hi all,
I have to create one field in qualified table as text normalized. But then once i select the option as text normalized in field type, the qualifier properties gets disabled. So how can i make a text normalised to be yes qualifier.
Also i want to search a record according to the text as well as text normalized. It means when the user will search a record it can do with text as well as with special characters. But the recorde found should be same.
Can anyone give the solution for this ASAP.
Thanks

Hi,
I have to create one field in qualified table as text normalized. But then once i select the option as text normalized in field type, the qualifier properties gets disabled. So how can i make a text normalised to be yes qualifier.
I am on MDM 5.5 SP6 Patch1 (Build: 5.561.48)
I tried it we cant Create Qualifier field of Type Text Normalized. So we can make use of it as only non-qualifier field only in Qualified Table.
We may hope this functionality in New MDM Releases.
For e.g if the record exist 121 and 1-2-1 should give the same result for the search.
For this Create field of type Text Normalized as Keyword Property = None always in Field Property of MDM Console so only Text Normalizied search give the same result for the search. i mean it will find both these two records 121 and 1-2-1 even if you write 121,1-2-1 or 1#2#1 for your Text Normalized field in free-form search of your Data Manager.
Hope it will help you,
Rewards if Useful....
Mandeep Saini

Expression with qualified table fields

Hi all!
I have 2 doubts concerning the free-form search and expressions using qualified table.
We're implementing SRM-MDM Catalog. Here is the scenario
The search is done in the Main Table (Products). The qualified table (Contract) has the following fields:
Contract ID: Non-Qualifier
Contract Item: Non-Qualifier
Contract Category: Non-Qualifier
Lower Bound: Non-Qualifier
Amount: Qualifier
Currency: Qualifier
Obsolete: Qualifier
There are 2 records in the Contract table assigned to the Product in main table:
123-1-Normal-1-100-BRL-False
456-1-Normal-1-250-BRL-True
1st doubt:
Using the free-form search, if I set the field Contract-Amount to be less than 150, only the record 123-1-Normal-1-100-BRL is listed in the result, which is ok. But if I enter in the expression option the formula Contract.AMOUNT<150, both records are listed:
123-1-Normal-1-100-BRL
456-1-Normal-1-250-BRL ???
Is this formula wrong?
2nd doubt:
The Contract info isn't a mandatory information. It's ok to have a product in the main table without a contract assigned to it. This can happen for example if all contracts for a product are obsolete. In the named search, if I select all products where obsolete equals to 'FALSE', only the records of the main table that have at least one valid contract are listed. As the contract info isn't mandatory, I was expecting a different behavior. Also the records that don't have a valid contract should be listed, but the contract information should be blank. Is there a way to do that?
Thanks!

check out these tables,
VBAK Header Data
VBAP Item Data
VBAG Release Data by Schedule Line in Sch.Agrmt.
VBUK Header Status and Administrative Data
VBUP Item Status
VBRL SD Document: Invoice List
VBPA Partner
VBKD Business Data
VBKA Sales activities
VBEP Schedule Line Data
VBRK Billing: Header Data (invoice)
VBRP Billing: Item Data (invoice)
VBFA Sales Document Flow
VTTP Shipment item
regards,
seenu

Issues dealing with the Qualified tables

Hi,
I am facing below issues while dealing with the Qualified tables.
Issue # 1. Trying to get the data from the Qualified table through the Main table. Qualified table is set as supporting ResultDefinition. I am able to get the value for only the non-qualifier fields but not the qualifier fields.
Exception: com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Qualifier values are not part of a qualified lookup record
Issue # 2. Need to define the search on the fields of a Qualified table with Main table in the ResultDefinition. I am able to define the search on qualifier fields but not the non-qualifier fields.
Exception:com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Field not found
I would like to know the standard ways to address these issues.
Thanks,
Surendra

Hello,
I was wondering if this issue is solved now. I'm still facing the problem when executing the RetrieveLimitedQualifierValuesCommand:
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Field not found
Are there other ways to manipulate qualifier field values? Workarounds... alternatives...
Is it related to the MDM Java API version? If yes, is there a fix?
Thanks a lot for your input!
Regards,
Pedro

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

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

Qualified table search in MDM

Similar Messages

Maybe you are looking for