Qualified table issue

My excel sheet has 3 coloumns taxcategory taxclassification taxclassificationdesc
my main table come with fields countrycode classification and others
i need to model this in my repository
I have metioned taxclassification as my lookup qualified table with fileds
1 tax classification   qualifier    lookup         flat     taxtypes table
2 country code          noqualifier lookup      flat     countries table
taxtype table fields taxcategory taxclassification taxclassificationdesc
when i load the values and see    i find that this has been modelled incorrectly
because it should have the below relations ship
countrycode taxcategory taxclassification taxclassdesc
IN MWST 0 NO TAX
IN MWST 1 FULL TAX
IN GST 0 TAXABLE
IN GST 1 50 PERCENT TAX
IN GST 2 low TAX
US IST 0 NON TAXABLE
US IST 1 FULL TAXABLE
MX PGT 1 FULLTAX
MX CST 1 FULLTAX
etc
so under MWST should have look up values 0 no tax
                                                                        1 full tax
          gst       0 taxable
                    1 50
                    2 low tax
          IST      0
                   1
urg pls
regds
ve

Hi Veena,
follow the step
1. First import data for Tax Category table as it's lookup table
2. then import tuple data example as follow
Material Number->Country->Tax_Category--->Tax_Class>Tax_Class_Desc
000000000010001-> IN-----> MWST -
> 0 -
> No Tax
000000000010001-> IN-----> MWST -
> 1 -
> Full Tax
000000000010001-> IN-----> GST -
> 0 -
> Taxable
000000000010001-> IN-----> GST -
> 2 -
> Low Tax
000000000010001-> US-----> IST -
> 0 -
> NON Taxable
000000000010001-> US-----> IST -
> 1 -
> Full Taxable
000000000010002-> US-----> IST -
> 0 -
> NON Taxable
000000000010002-> US-----> IST -
> 1 -
> Full Taxable
in above example Material Number is field of main table and all other are tuple fields map one to one field at destination side and select Material Number as Matching field in Match Records tab and import the data
Note : tuple records data can not import directly it require atleast one main table field and it should be display field then select this main fileds as matching field in match records tab then only it will allow to import tuple data
Thanks,
Jignesh Patel

Similar Messages

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

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

Import issue with Auto-id in Qualifier table

Hi,
I am trying to load Customer_contact table in MDM5.5 sp4 from R3.
Since SAP-Id is generated in R3, initially portal will send all data to R3 w/o SAP-id but with the MDM-Auto-id.
In return from R3,MDM receives the SAP-id and Contact-id against this MDM-id for update.
In conversion,I am getting "Error in Look uptable" "Internal Error" message to load this file in Main table.
Is there any workaround to map qualifier table with a auto-id in Main table?
This auto-id needs to be non-qual for portal to create the initial record in MDM.But since this is a non-qual fld and we are not able to map it in main table giving "Internal error" . It is my guess.
Appreciate your idea and help
-reo

The issue was fixed after dropping the calculated fld as Non-qual one which was giving problem since required to be mapped in Main table.

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

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

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.

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

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

Unique key for Qualified tables

Hello Experts,
We are currently facing an issue with qualified tables. We need to retain existing system keys as below:
Item (Main table)
Item_Id, Item_Number
Item_Price (Qualified Table)
Item_Price_Id, Item_Id, Price_Type_Id, Price
E.g.
1, Pencil
2, Pen
3, Notepad
1, 1, Retail_Price, $10
2, 1, Wholesale_Price, $5
3, 2, Retail_Price, $15
4, 2, Wholesale_Price, $10
We need to migrate the existing ids (Item_Price_Id) in MDM qualified table and need to maintain the same as max(Item_Price_Id) + 1 for all future records.
Is there a way we can achieve this?
Your help is greatly appreciated.
Thanks in advance,
Vinay

Hi Karol,
The Interface Iprinciple has this function as it:
Gets the unique identifier which unambiguously identifies the object's principal type and principal's data record(s) in the data store (e.g. a relational database).
Note: the unique ID is a case sensitive string
Use this identifier to keep and persist references to principals. As this identifier contains internal information and is usually not readable, it should not be displayed in user interfaces.
UME implementation guarantees to return Strings which are not longer than 255 characters.
Returns:
a non-null String identifying this principal
I hope this helps you.
Regards
Pravesh

Qualified table entry

Hi Experts!
I am trying to create a design in which there is one Independent field and 7 dependent field using Qualified tablein MDM.
In ECC though,Only valid entries are allowed for one corresponding selection of NQ.
But in MDM i can create any value without any issue.SO my question is how will my system know that for one entry of NQ only particular entries of other fields are allowed.
Pls guide!
Thanks,
Ravz

Hi,
As validation is not possible on qualified tables.
If you really want to put validation entries then use table for qualifiers so that you can put onlt that valkue that defined in that table.
Thanks,
sudhanshu

Qualified table issue

Similar Messages

Maybe you are looking for