Loading main tables or Qualified tables first recommended??

Hi All,
Is the loading data for Qualified tables first recommended before we load the main table data??
Could I find any SAP recommeded quotes regarding this??
thanks

Hi Arvind,
First Qualified Table data is uploaded and the Main Table data .
FOLLOW THE LINKS.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1012f58f-a6e6-2a10-7caf-a46b7ad0f299
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/abe914fa-0301-0010-7bb1-d25c2a4bb655
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30380d0e-2f23-2a10-8f9d-da55511adbd8
Reward if Useful.
Regards,
Vinay Yadav

Similar Messages

How to import data into taxonomy tables and qualified tables

Hi ALL,
Can anybody suggest to import data into taxonomy tables and qualified tables, when is value mapping neccessary and what is partitioning? and what is the use of that partioning?

Hello rehman
even i am facing same issue regading import of data in taxonomy table
. can we do it through import manager.
please provide me some details i will be very very thankful to u
my email - [email protected]
Thanks & regards
Himanshu

Loading data : Creation of entries in the Qualified Table

Hi,
I was wondering if anyone has succesfully achieved the following...
I'm looking at the standard materials repository.
- Main Table : Product
- Qualified Table: Location Data. This qualified table single non-qualifier field is a look-up to a flat look-up table, called Plants
The flat table is populated with the valid list of plants, using the check table synchronisation. The Main Table is empty, so is the Location Table.
In order to load products into this repository using the import manager it seems that it is required to "create" entries in the qualified table (Location), one for each plant-code.
Is this true ? I actually would expect the SAP MDM Import Manager client to be able to create the records in both the main table and if needed, the qualified table. As long as my plant code exists in the "Plants" look-up table, that should be sufficient. It seems not the case..
Thx,
Dirk

The sequence of Import
- Load the Flat Lookup tables. ( in your case Plants)
- Load the Qualified Tables ( in your case load the non qualifiers of the Location Data)
- Load the Main table (in your case Products)
Though MDM allows you to create Lookup values on the fly, I would rather go with this approach.
If you are using Import Manager, you can add the Qualified Table Records in the fly.
But if you are using Import Server, you will NOT be able to add Qualified table records in the fly. I tested this, and I see the files in the ImportX error directory.

Qualified Table - Validations

Hi ALL,
I have field in the Main table, where I need to run a assignment on this field, based on the validation results from qualified table (qualifier).
Lets say field in Main table is " Global Status " ; Qualified table ( qualifier field - plant status).
if plant status = Z3 then Global Status is Active --> i can have more than one qualified links and may the Plant status= Z3 is first qualified link or last qualified link.
Is this possible?? to writie a validation for the same.
please revert to me asap.
thanks,
Alexander

Hi Alexander,
As per my understanding, I think this is possible to run a validation if plant status = Z3 then Global Status is Active.
This validation is true if any of the qualified links has Plant Status = Z3, either this is 1st Qualifed link or last and fails only if none of qualifed links has plant status = Z3.
As you are running Validations this should run as expected. Further on the based of Validation result you can run assignment.
I also feel that you can also run Assignment directly if any of the qulified link has plant status = Z3 then populate Global status = Active as Global status field belongs to main table not qualified table.
Just check and revert with result as I dont have MDM installed on my PC so would able to check it tomorrow from my end.
Regards,
Mandeep Saini

QUALIFIED table import at single step

Hi all if any one can tell me hoe to import qualified table and hierarchy table.
Qualified table has 3 yes qualifiers and one 2 no qualifiers.
Thanks in advance
Nm

Hi New Man,
For the hierarchy import, there are two cases 1) you already have the source data which you need to import 2) you need to create the hierarchy from the fields given.
If you already have the source data you can first go in the hierarchy table select the source field and add the field on the destination field side by right clicking on the hierarchy value in the source side in the value mapping tab and selcting the option "Add As Sibling/ As Child" you can choose any of the option as per your need.
After doing this you can choose the main table and import the hierarchy field from the source side to the destination side.
In the first step, we get the records in the hierarchy table on the destination side and in the second step you get to see those hierarchy records in the main table's hierarchy field.
If you dont have the hierarchy and you need to create it before importing with the help of the fields on the source side you can follow this link.......
Hierarchy Import
Reward points if found helpfull
Hope this helps you ......
Prasad.................

Expression logic for qualified tables

Hello Experts.
I am searching for an expression that can manage the following requirements:
Different records of a qualified table belong to one record of the main table. One value that belongs to a certain combination in the qualified table should be automatically transferred to a field in the main table. For example there is one main table (MAIN) and a qualified table (QT) with at least two fields.
Main table (MAIN) with some fields
Qualified table (QT) with Field 1 and Field 2
I tried following expression: IF(QT.Field 1 = NAME, QT.Field 2). But the expression doesn'tt work.
How can an expression work with a certain combination of a qualified table? Has anybody an idea how to solve such a mystery?
Thank you in advanced,
Anja

Hi Anita.
I have the answer: You need an additional field in qualified table. This field is filled during import with the concatenation of all field values of the QT record.
Qualified table with field 1 and field 2 look then like this
Field 1: Name
Field 2: Anita
Field Conca:Name.Anita
Now it is possible to build expression that can evaluate the string of the concatenation field.
Thanks for your help,
Anja

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

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

Can we run an assignment on a qualified table from a main table?

Can I run an assignment on a qualified table from a main table.
For example: My main table Vendor and Qualified Table is Company Qualified .
Company Qualified - VendorNr (Non- Qualifier),Company(Qualifier,lookupFlat - Company)
Company - Name,Description (It has valid values in it already).
How to add a default value into the Company Qualified table.
When i add a assignment like
If(is_null(Company Qualified [Record],default lookup value from Company) ...it says invalid.
Any help greatly appreciated thanks

This is not possible currently in MDM. I've tried many times to find a good way to do this and so far have been unsuccessful. I also have tried to have a workflow on the main table call an assignment in a lookup / qualified table, and that doesn't work either. The biggest reason is because you have to select a table field when you create an assignment, and it doesn't give you the option to choose fields within a table.
Hopefully they will address this in a future release.
Edited by: Harrison Holland on Jun 3, 2008 2:33 PM

Qualified Tables Working

Hi All,
How to Map the qualified fields in the qualified tables if the qualifier for that field is set to YES, because such fields are not reflected in the import manager for mapping only the fields whose qualifier is set to NO are visible.Thee problem is wen the qualifier for a field is set to YES you can feed the data only in the DATA MANAGER as these fields are only visible therewhich become so much of a lengthy process if data is large.
Can any one please explain the importance of the qualifier in the qualified table in layman terms, how to make the best use of it and please if possible give a short and sweet example for it.
HELP NEEDED URGENTLY
Thanxs in Advance.

Hi Prasad,
Where do we use the Qualified tables:
At times data is stored in such a way that duplication is unavoidable due to the storing mechanism and other factors. It may also happen that the data is sparse. The efficient way of storing data in such scenarios is the use of Qualified tables as it reduces the size of the main table and removes the unnecessarily created duplicates.
Difference between Qualified lookup table and Flat lookup table:Flat lookup tables normally work on only a single field. It contains the set of legal values to which corresponding lookup field in the main table is assigned.
E.g. suppose we have a flat lookup table for Material Group for an automobile manufacturing company. Here we have a fixed set of legal values that can be looked up into the main table (for example Cars, Bikes, SUVs, etc.)
Qualified tables work on the combination of two types of fields where value of one or more fields (qualifiers) changes depending on the values of one or more other fields (non-qualifiers).
E.g. suppose we have a field Price whose values varies with the region for the same product. Here we have a fixed set of related legal values (combination of fields) that can be looked up into the main table. (For example Product A has a price of $30 in Southern region whereas $40 in Central region, then we get a set like Product A | Southern | $30, Product A | Central | $40 in the Lookup Qualified table)
Watch out for the definition of Qualifiers and non-Qualifiers:
This was something which took a long time for me to hunt down.
Qualifiers are those fields whose values change based on the value of some other field(s) and whose value is different for each main table record
Non Qualifiers These fields are only the part of qualified lookup table, but they apply not only to the qualified table but also to each association of the qualified table record to the main table record. Simply speaking, they are the fields that will decide the values in the Qualifier (main table)fields.
Our Scenario:
Suppose we have been provided with the following source data
Manufacturer Name of Drug Region Price Storage Temp
A Crocin North 280 27 Celsius
A Crocin South 300 14 Celsius
A Crocin Central 260 30 Celsius
A Disprin North 380 30 Celsius
A Disprin South 360 27 Celsius
A Disprin Central 320 14 Celsius
Observation:
Values of Price and the Storage Temp field change based upon the Name of Drug and Region field values and also their values are different for each main table record; hence these should be madequalifiers in the qualified lookup table
Since Name of Drug and Region fields are deciding the qualifier values hence these should be kept as non qualifiers in the qualified lookup table. Manufacturer and Price will be part of the main table.
Design of repository:
We will discuss only the design of the main table Products and the Qualified lookup table Prices as they are of our immediate concern.
Products
Field Field Detail
Manufacturer Name- Manufacturer
Type - Text
Required Yes
Display Yes
Lookup[Price] Name- Lookup[Price]
Type - Lookup[Qualified Flat] (multi-valued)
Required None
Display No
Multi-Valued - Yes
Lookup Table Prices
Prices
Field Field Detail
Name of Drug Name- Name of Drug
Type - Text
Required No
Display Yes
Qualifier - No
Region Name- Region
Type - Text
Required No
Display Yes
Qualifier - No
Price Name- Price
Type - Currency
Required No
Display Yes
Symbol - $
Decimal Place - 0
Qualifier - Yes
Cache - Yes
Storage Temp Name- Storage Temp
Type - Measurement
Required No
Display Yes
Dimension Temperature
Default Unit Celsius
Qualifier - Yes
Cache - Yes
Note: Caching of qualifiers is strongly recommended as it dramatically improves search performance.
Once the design of the repository is through, we now move on to the trickiest area the one of the Import Manager
Importing records:
As per the standard practice, we load the lookup table first, here Prices and then the main table Products.
Step1:
Loading the Qualified lookup table data:
Select the corresponding tables in the source and destination hierarchy in the Import manager.
Go to Map Fields/Values tab and Map the corresponding fields in the field mapping grid.
Note: Here only two fields (non qualifiers)can b seen in the destination field grid, however in the repository design we have created four fields.
The qualifiers (fields) never appear in the destination field of the qualified lookup table in the Import Manager.
Go to Match Records tab and select the non-qualifiers as matching field and Add it as Combination.
Select Import Action as Create as it is an Initial load of data.

Step2:
Loading the Main table data:
Map all the source fields to corresponding fields in the repository.
Notes: Here many fields in destination (including qualifiers (Q) which are defined in the qualified table and not in the main table of the repository structure in Console).
Minimum required field mapping: All non-qualifier fields of the qualified lookup table should be mapped. Qualifier field (Q) is optional.
Now we are left with one field (Lookup [Price]) in destination which is still unmapped and we have no corresponding field left in the source to map it with. For this, go to source field tab and right click to create compound field
Lookup [Price] will be available in the source field and will get automatically mapped to the corresponding destination field.
Note: If any one of the non-qualifier fields of the qualified lookup table is not yet mapped, we are not allowed to create the compound field.
Do the Record Matching and Import the data into Data Manager Client by selecting the appropriate Import action.
Final Qualified data in main table:
The data is available in the Data Manager.
P.S. If there is only one non-qualifier in a scenario, then the Compound field is not created and direct one to one mappings suffice.
Please award me points if u find trhis blog as a value addition.
Thanks & Regards ,
Deepankar

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 (Bank Details) Import Question

I am using MDM 5.5 SP6
I am using the Standard SAP delivered Vendor Master Repository and trying to load the Qualified Bank Details table. Bank Details qualified table we have 9 non-qualified fields and 6 qualified fields.
Do we need to load the non-qualified fields in the bank detail table first?
Anyone help me with details about how to load this table including linking this to the main table?. If anyone has any document explain the steps in detail then could you send it?
Thanks in Advance
Steve

First thanks to all who contributed.
I am able to load the qualified table but these non- qualified fields (Street, City, Swift Code, Bank Group, Bank number and Bank branch), I am not able to map it so after loading it was blank.
Out of the 9 non-qualified fields in the Bank Details Qualified table, Country, Bank Key and Bank name are DISPLAY fields and I am able to map and load these fields.
Other non-qualified fields such as Street, City, Swift Code, Bank Group, Bank number and Bank branch are NOT DISPLAY fields. While using the import manager and doing field mapping, for these 6 fields there is NO destination fields displayed. So I couldnu2019t map it.
When I made the above 6 non-qualified fields as DISPLAY fields, then try to map it, I am able to see these fields in the destination side and did the mapping. After import still those 6 fields are blank.
What I am missing here?. Is there any limit that only 3 non-qualified fields we can map it?
Steve.

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

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

Loading main tables or Qualified tables first recommended??

Similar Messages

Maybe you are looking for