Multple Actions on single Qualified table??

Hi Experts,
I have a QT with 1 Non qualifier and 2 qualifiers..
My requirement is
Main table
CC Code (Unique key)
CC Contact info (LK QUAL)
Qual Table
Type (Non Qualifier)
Telephone (Qualifier)
Fax (Qualifier)
Value in Type Field is
General
In data manager i have the following..
COde :99
type : General
Telephone: 43
Fax: 11
There are 2 requirments for this table..
if my second file has inputs as..
Code: 99
Type: general
Telephone: 3342424242
fax: 222342
Code: 99
Type: External
Telephone: 24224567
fax: 3432342
Now My record after import should look like..
Code: 99
Type: general
Telephone: 3342424242
fax: 222342
Code: 99
Type: External
Telephone: 24224567
fax: 3432342
So here New External is added(Which is not available in DM in prior) and Old 'General' is replace with new values..
Is this possible???
i tried with Qualified update in Import manager
If i set Update then new values(External) is created but the 'General' is added as a new Entry instead of Updating the old 'General' entry..
If i set Replace/Append then the External values are not being added..
Can any one say whether this is possible & What is ONLY possible??
Please Help..
KR
John

Hi,
In the mapping tab..
I selected the Type Filed -> Right click-> set qualified update - > here i selected update-> i can see the telephone and fax moved to the selected qualifiers -> New links Create -> existing link update (all mapped fields).
If i do the above the New entry (Type: External, Tele and fax ) is added, But there is a new entry for Genral(Which should be actually updated with the Old entry of general)
Can anyone help!!
Kind Regards
Venkat

Similar Messages

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

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

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

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

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

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.

Import Server - Multiple Qualified Table - Map Crash

Hello,
Requirement: I need to update multiple qualified table using single source file.
Preparation: I have created a map where mapping to multiple qualified table fields maually.
Have created a Inbound Port using the above map.
Problem: Import server throws an exception; while opening the Import Manager using the Port Option and corresponding Exception; Lot of fields were un-mapped. Looks like Import map crashed.
Please feel free to throw some light reg the same!
Thanks
Alexander

Hi Alexander,
If you are performing multiple qualifier table mapping and importing then you will hav eto create differnt map for each table importing.In that case you will rrquire multiple inbound ports and in each ports deatils you will give the map name pertaining to which qualified lookup table you wish to import.
Actually using automatic importing for lookups is not desirable as the lookups always need to be prepopulated before your main table importing.
The exception taht you are receiving could be due to the reason that the map you are saving is using only one table mapping and so most of the fields are left unmapped.
try not to use automatic importing for Lookup qualifier tables and use manual importing and see if the the exception still comes.
Hope it helps
Kindly reaward points if found useful
Thanks
Simona

Qualified Tables Problem

hi,
    I would like to know if possible to avoid duplicates in a Qualified table. When you create a qualified table you can set several things. firstly you can set if fields inside the qualified table are Non Qualifiers or Qualifiers and furtheremore you can set some field properties like display field...and unique field.
I realized that you can put 2 iqual records inside of a qualified table.
I would like to know how i can make so that there are not duplicate records inside the qualified table.

Hello Jose,
   Here is the example how you can eliminate the duplicates by using a qualified table
first the main table of product records shown in the figure below that contains sparse quantity pricing data for each product.
SKU     Name     1-9     1-24     1-49     10-24     25-49     50-99
113     Widget     $3.51                 $3.48     $3.44     $3.40
114     Wrench           $8.75                 $8.30     $7.99
115     Bearing                 $5.12                 $4.80
Using a qualifier to store the quantity pricing data, the qualified table would have a single field Quantity and a single qualifier Price, and would contain the quantity records shown in the figure below.
Pricing:
Quantity     [Price]
1-9
1-24
1-49
10-24
25-49
50-99
A qualified lookup field in the main table would replace all of the quantity price fields, and the pricing data would be stored as qualifier values associated with main table/qualified table links, as shown in figure below.
SKU     Name     Lookup [Pricing]
113     Widget     1-9; $3.51
          10-24; $3.48
          25-49; $.344
          50-99; $3.40
114     Wrench     1-24; $8.75
          25-49; $8.30
          50-99; $7.99
115     Bearing     1-49; $5.12
     50-99; $4.80
A main table/qualified table link is created only for those product/quantity combinations for which a price value actually exists.
So!, finally we can conculde this as ONLY THING THAT NEEDS TO TAKE CARE IS THAT THERE SHOULD BE NO COMMON DATA INVOVLED IN ANY OF THE COLUMN, IF THERE IS ANY COMMON DATA - THAT NEEDS TO BE CREATED CREATE IT WITH A NEW COLUMN.
Thanks,
Suresh

Uniqueness in Qualified tables

Dear MDM experts,
I have this requirement wherein we have a qualified table wherein the user shouldnt enter duplicate entries.
e.g. in the case of customer master data,the user may have only 1 qualified table record per company code. (can have differnt company codes)
I have set Company code as an NON QUALIFIER but it does not enforce any kind of uniqueness.
<h5>Is it possible using qualified tables to have such an enforcement ?
</h5>
Also as an alternate can I write a validation rule such that it will allow me to enter data in the qualified table only once per company code.
Thanks.

yes this will work in the case only, if you have your customer name as a master table field. Try this:
1. Customer Name and qualified are two fields in Main table.
2. In QT you have Comp_Code as unique Field as non qualifier and other data like company_name, Loc as non Qualifier or what ever you want.
then DM allow you to enter same company code for two different records.
now this is also possible that a person may have worked in 2 different organizations then you can put 2 records in QT and you can select them for a single customer.
Rewards if found helpful.
BR,
Alok Sharma

Qualified table

Dear all,
I have a requirement, for a single vendor record need to maintain multiple License details.
ie., main table 'Vendor' will hold Vendor record and each vendor record may have multiple License's. Do i maintain the license table as 'multivalued' Qualified flat. If yes how do i link vendor and License tables and what field properties do i need to set.
ex: a field as qualified/non-qualifier ?
Sonali

Hi Sonali,
Vendor ID, Vendor Name, Description can be placed in the main table Vendor.
License Number, Date, Description can be placed in the Qualified table with the License number as NQ and the determining fields ie Date and Description as Qualifiers.
Now When you do mapping of the Qualified table you will be bale to see only the non qualifier fields there.Map those fields with the main table fields and import in the Qualified table.
Now when you perform the main table mapping you will be able to see the Qualifiers as well as the non qualifiers fields and the lookup qualified field as well.
Firstly map all the main table fields such as Vendor ID, Vendor Name and Description then map the qualified tabel fields this will establish the mapping between the main table nad the qualified tabel records.
Follow this below link which will explain you better on qualified atbel mapping:
Taming the animal - Qualified Tables
Hope It Helped
Thanks & Regards
Simona Pinto

Mass Update of date in Qualified table

I having problem in updating End availability date in Partner Specific Data (which is a qualified table). How can do a mass update of selected records. I have written an assignment expression which has no error but it is not doing the update.
Regards,
Marcel

Hi Marcel
Assignment and validation does not work well for qualified table. It will work for only first qualified linked record and not all.
for mass update you can use import manager map the date qualifier field and select replcae action for qualified update in the destination item.
best regards
ravi

Difference between Qualified tables and tuples.

What is he difference between Qualified tables and tuples.
Does MDM 7.1 also support qualified tables? which is better out of 2.

Hi Shekhar
Qualified tables are special tables which have Non qualifiers and Qualifiers and for a single record we can have multiple values based on NQ. To explain further- Material can have different prices based on Region of sale, Lot size. This can be modeled using a qualified table where Price varies based on combination of Sales Area and Lot size(NQs).
To read more please refer to link- https://weblogs.sdn.sap.com/pub/wlg/3417?page=last&x-showcontent=off&x-maxdepth=0 [original link is broken] [original link is broken] [original link is broken]
Tuple is new data type introduced in MDM 7.1, it has many plus points over Qualified table. It supports multiple nesting and can contain many different data type fields. To read more please read- Difference between TUPLE and a look up table
Thanks
Ravi

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

Multple Actions on single Qualified table??

Similar Messages

Maybe you are looking for