Qualifier and non qualifier fields

Hi,
What is the diff b/w Qualifier and non qualifier fields
Regards,
Ganga

Hi,
You can get a lot of information on Qualifier & Non- Qualifiers.
Please follow the link below for info:
http://help.sap.com/saphelp_mdm550/helpdata/en/8e/9f9c427055c66ae10000000a155106/frameset.htm
Go to->Repository Maintenence->Designing an MDM Repository-> Qualified Tables.
How to Consolidate Data in Qualified Tables (NW7.0) :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30380d0e-2f23-2a10-8f9d-da55511adbd8
SAP Network Blog: Taming the animal - Qualified Tables:
Taming the animal - Qualified Tables
Here is a link to the thread where you can understand the concept to Qualified tables:
Qualified table concept
After basic understanding, you can follow the links below for importing the data into Qualified Tables:
Importing Qualified Tables in MDM:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
Importing Qualified Tables and Main Table Data in a Single Step:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e319a6e
Hope this info helps.
Thanks and Regards
Nitin jain

Similar Messages

Key fields and non-key field of condition table

Hello Gurus,
what is key fields and non-key field of condition table?
thanks very much!

Key field
Each condition table contains keys that can be used for creating dependent condition records.
for example let take condition type PR00.
PR00 uses access sequence PR02 .
Access sequence PR02 has following tables associated with it namely 304, 305 & 306
When you create a conditon record for PR00 with transaction VK11 or VK31, you have a button 'key combination' which is nothing but fields associated with tables 304, 305 & 306.
In brief, Condition records are always created using specific keys. Condition tables are used to define the structure of the keys of a condition record.
Non key field
For example take condition table 144 - sales deal basic data.
Table 144 is associated with access sequence PBUD.
If you check the fields associated with this table (click technical view button), there are three fields at bottom which do not have 'key' check mark -KDATU, PLTYP, KSTAF
So, when you create a condition record for PBUD, system does not propose these 3 fields in 'key combination' and hence are non key fields.
Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme.

Mandatory and non-mandatory fields

Hi all,
Is it possible to have certain fields in VD01 mandatory for one user and the same fields are non mandatory for another user.If so, can anyone please explain it.
Thanks in advance
Sandeep

Hi,
In the customizing you can set up mandatory based on the account groups..But not for each user..Instead you can do it through user exit..
Check this user exit EXIT_SAPMF02D_001.
Thanks,
Naren

Updating and Loading a Matrix Row with Mix of DB and Non DB fields

Hi
I'm using SAPB1 2005 SP1 PL14 with B1DE 1.3
I have a matrix on a form that was generated by the UDO Form Generator. The Matrix contains data associated from a Document Lines table.
The underlying table and (therefor the matrix as well) only had 1 user field (column)
I've added a set of additional (read only) columns to the matrix together with supporting non db user datasources for each column. I've bound the new columns to the user datasources.
The new columns are only informational and should display data associated with the actual db field (column) in the matrix.
I require assistance / advice with 2 requirements:
Requirement 1.
When loading the matrix, I'd like the non DB columns to be populated with data associated with the actual DB field.
Requirement 2.
When Adding / Updating the actual DB field in the matrix, I'd like the Non DB columns to be populated with the assocaited data.
I've managed to get requirement 2 working by using a matrix onValidate Event. (not sure if this is the best approach?)
Any idea how I can achieve requirement 1 ?
Cheers,
Ben

Hi Trinidad,
Putting the additaional columns in the table will result in me storing redundant info in the specific table.
The values are already stored in other related tables and I'd just like to display them as additional info fields.
.Ben

Reserved and non reserved fields.

Hi team,
Im a XI consultant . Can you tell me the field names and tables for ....(retaled to material).
Reserved amount----
Non reserved amount----
Plant site code----
Material number -
MATNR
Batch -
CHARG from MSEG
Status----
PSTAT
Material Description----
MAKTX
Old Material Number -
BISMT
Storage Bin----
LGPBE from MARD
UOM----
meins
--Drumi

hi.,
in which transaction did u find these " Reserved amount----
Non reserved amount----
Plant site code----
provide the t-code if u can..
regards

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

Unique Field as Non-Qualifier in Qualified Flat Table

Hi experts,
I have the requirement to store the customer data regarding company code in the qualified flat:
customer have different data related on company code. It's important that this company code have to be unique in this qualified flat. (e. g. one customer have data with company code 3850, 3860 and 3870, its not allowed to store further data with the same company code 3850).
In the console I set the company code as unique and non-qualifierer field. But afterwards I was able to put two records with the same company code in this lookup qualified flat table.
What did I wrong? ( I use MDM 5.5 SP 6 Patch 3).
Best regards,
Nico

Hello,
the behaviour depend of the settings for qualified upadate.
(Set Qualified Update sub-menu when define mapping in import manager)
Settings can be:
- Append
- Replace
- Update
In your, case looks to be "Update". be sure the Set Matching Qualifier is righly set for the qualifier which indentify the relation to the flat data. (sometimes have to clean this point)
Check New links are : Create and Existing Links are : Update (All Mapped Qualifiers)
Hope helps you
best regards
Vincent

Internal table with Dynamic and Non dynamic fileds

Hi Experts,
How to get the internal table with Dynamic and Non-Dynamic Fields.
Could u please help me.
Thanks,
Varun

Hi,
Execute the below sample code or analyze it there is appropriate description provided.
*& Report ZTEST_PRM_DYN_ALV
REPORT ZTEST_PRM_DYN_ALV.
type-pools: slis.
field-symbols: <dyn_table> type standard table,
<dyn_wa>.
data: alv_fldcat type slis_t_fieldcat_alv,
it_fldcat type lvc_t_fcat.
selection-screen begin of block b1 with frame title text-001.
parameters: p_flds(5) type c.
selection-screen end of block b1.
start-of-selection.
*build the dynamic internal table
perform build_dyn_itab.
*write 5 records to the alv grid
do 5 times.
perform build_report.
enddo.
*call the alv grid.
perform call_alv.
*Build_dyn_itab
form build_dyn_itab.
data: new_table type ref to data,
new_line type ref to data,
wa_it_fldcat type lvc_s_fcat.
*Create fields .
clear wa_it_fldcat.
wa_it_fldcat-fieldname = 'name1'.
wa_it_fldcat-datatype = 'mara-matnr'.
wa_it_fldcat-intlen = 5.
append wa_it_fldcat to it_fldcat .
*clear wa_it_fldcat.
wa_it_fldcat-fieldname = sy-index.
wa_it_fldcat-datatype = 'CHAR'.
wa_it_fldcat-intlen = 5.
append wa_it_fldcat to it_fldcat .
do p_flds times.
clear wa_it_fldcat.
wa_it_fldcat-fieldname = sy-index.
wa_it_fldcat-datatype = 'CHAR'.
wa_it_fldcat-intlen = 6.
append wa_it_fldcat to it_fldcat .
enddo.
*Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
exporting
it_fieldcatalog = it_fldcat
importing
ep_table = new_table.
assign new_table->* to <dyn_table>.
*Create dynamic work area and assign to FS
create data new_line like line of <dyn_table>.
assign new_line->* to <dyn_wa>.
endform.
*Form build_report
form build_report.
data: fieldname(20) type c.
data: fieldvalue(5) type c.
data: index(3) type c.
field-symbols: <fs1>.
do p_flds times.
index = sy-index.
*Set up fieldvalue
concatenate 'FLD' index into
fieldvalue.
condense fieldvalue no-gaps.
assign component index of structure <dyn_wa> to <fs1>.
<fs1> = fieldvalue.
enddo.
*Append to the dynamic internal table
append <dyn_wa> to <dyn_table>.
endform.
*CALL_ALV
form call_alv.
data: wa_cat like line of alv_fldcat.
*clear wa_cat.
wa_cat-fieldname = 'matnr'.
wa_cat-seltext_s = sy-index.
wa_cat-outputlen = '10'.
append wa_cat to alv_fldcat.
do p_flds times.
clear wa_cat.
wa_cat-fieldname = sy-index.
wa_cat-seltext_s = sy-index.
wa_cat-outputlen = '6'.
append wa_cat to alv_fldcat.
enddo.
*Call ABAP List Viewer (ALV)
call function 'REUSE_ALV_GRID_DISPLAY'
exporting
it_fieldcat = alv_fldcat
tables
t_outtab = <dyn_table>.
endform.
Hope this will help, reward if found usefull.
Cheers,
Ram.

Non key field in Maintainance View

Hi,
I have generated a maintainance view for a Z table. I want to sort data from SM30 by means of a selection screen, for that, in the 'View Flds' tab in the maintainance view, i have entered a 'S' for which ever fields i want to filter the data on.
When i execute the table maintainance, i am able to see only the key fields and not the non-key ones in the selection popup, though i have put a 'S' for both, the key and non-key fields.
Can anyone please let me know how to get the non-key fields on the selection popup when i execute the maintainance view?
Cheers,
Raghav.

Not possible via this functionality. A workaround was suggested by Raymond in this thread:
Transaction code for Table Maitainence for table
Thomas

Process data of none bound fields in Adobe Interactive Form (stack 13)

I use a Adobe interactive form (made in Designer 7.0)which is a combination of fields bound to Web Dynpro Context fields and fields which has no binding at all (in Designer: Default binding = Normal). The Adobe Document Services on the J2ee server is of stack 13.
When I save the Adobe Form (off-line scenario)from the Web Dynpro Application, only fields bounded to the Web Dynpro Context are saved in the Form on my local file system(no warning that data isn't saved).
When I open the Form for off-line editing, I can change bounded fields and none bounded fields. But when I save and re-open the form, the data in the none bounded fields is lost.
I used the same scenario in a stack 11 j2ee/portal system, but then all data (bounded or not) in the form was saved!
Could anyone explain the difference, but better tell me how to save both kind of fields in the off-line form (and bounding all fields is not a solution).
Thanks in advance,
Richard

Hi,
Check your ADS settings, I feel it's due to lack of some config in ADS only.
Regards
Raja Sekhar

Non-persistent fields

Hi,
I would like to use toplink with objects that contains both persistent and non-persistent fields (unmapped). When I insert such an object to the database using unit-of-work, and then try to query toplink for that same object elsewhere in my program I only get the persistent fields. I've tried using checkCacheThanDatabase() which resolved the problem but this method is only available for ReadObjectQuery not for ReadAllQuery (the javadoc is not consistent with the code).
My questions:
1. For ReadObjectQuery, can I trust the cache to always have my object, or is there a risk that the cache will drop it?
2. What to do with ReadAllQuery?
3. Any other approach that can work?

You can make non-persistent attributes remain with the object in a unit of work through using a clone policy and using the postMerge event.
Your class needs to implement Cloneable and in the descriptor use clone-copy-policy. This will ensure that when a cached object is registered into the unit of work the non-persistent attributes will be maintained.
When the unit of work merges a transactional object into the session cache you need to make sure you copy the non-persistent attributes from the clone to the cached object. You can do this through a DescriptorEventListener and the postMerge event.
Example:
postMerge(DescriptorEvent event) {
String tempProperty = ((MyClass) event.getObject()).getProperty();
((MyClass) event.getOringalObject()).setProperty(tempProperty);
Note that since the attribute is non-persistent it will not be guaranteed to persist indefinitely. The non-persistent attributes duration will be dependant on your caching policy, if it gets dropped from the cache, a new instance will be built from the database the next time it is accessed.
The checkCacheThanDatabase checkCacheOnly properties should not have any effect on what you get from the cache. Reads that access the database will still maintain object identity with the cache, and you should get back the correct object.

Non-display fields in Qualified Table to be displayed in ItemDetail iView

Hello expert,
Is it possible to display a non display field in Qualified Table in ItemDetailed iView?
It seems not possible by standard iView configuration.
Is it possible to achieve by some minor coding? If possible, such code is appreciated.
Thank you.
Dale

Hi Dale,
Yes, it is possible , and no need to do any custome coding. You can configure non-Display field of Qualified table to be displayed in Standard item detail iview.
You have to select Qualified look up field if you are creating Item iview on Main table and complete all steps.
once you complete all steps, open Item iview , select Reletionship and qualified display field option .
now you can see qualiied tables in table , click on Edit , now you can see all fields of qualified table.. you can select any field (dis/non-dis fields).
Hopw this helps you.
Thanks & Regards,
Veera.

Matching and Merging Qualified fields

Hi,
I want to match and merge fields in a qualified table.
Eg: Have to match the Street, City(Yes Qualifier) in the Qualified table Address.
Have created the transformation, rule and startegy on these fields.
When I execute the strategy, i'm able to see the scores and class.
But in the "Merge" tab only fields of Main table are visible. I'm not able to see the required Address table fields and hence not able to make the decision on which field should be merged.
How do i execute this scenario?

Hi ketan,
Basically you can perform matching and merging only on Main table and not on qualified tables; and if you have to match any qualified lookup field in the main table then it should be an qualifier field(i.e. the qualified option should be YES),
And while matching the records of a qualifier field when the values matches it shows only the display fields of the qualified table not the qualifier fields as already they have the same value you don't require them again.
I couldn't understand the structure you gave above, but i will take this example
Qualified table(Price)
       field_Name          Displayfiled       Qualifiedfield
         Price                      Yes                 No
         Quantity                 Yes                  No
         Currency               No                     YES
Main table(Products)
          field_Name         Type
          Product               Text
           Price                Look-up(Price)
now the values in main table
   Product          Price
cream            05 | 10 | Rs
Cloth             10 | 05 | $
Pen               20 | 02 | Rs
Pencil            02 | 02 | Rs
now you write a rule using the price lookup qualifier field.
it will show cream , pen and pencil as matching.
you can now merge as
___________       cream                 Pen         Pencil
___________        05 | 10               20 | 02      02 | 02
now you can select the product any one of those there and price any one of those three but as the currency qualifier field is same for all; its not displayed nor is it showed over here.
If the scenario is different form this which you require; please let me know, but the common scenario is the same.
Regards,
CHARAN

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

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

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

Lookup Flat Table and Lookup Qualifier Table

Hi,
Can any body confirm that if I will change the type of lookup-flat type field to lookup-qualifier type field. But the structure of Lookup Flat table and Lookup Qualifier table will be the same then the Java code written to populate the lookup-flat type field will work without any changes with its new type (lookup-qualifier).
Right now when I run the code after the above said changes, no error comes but no values is assigned to that field.
Another way to ask this question, can a simple Qualifier Lookup table(without having any qualifier type field) be used as like Lookup flat table.
I would appreciate if any body can help me in this regard ASAP.
Regards
Shahid Nadeem

Hi Alok,
I think this Qualifier importing after main table import is quite trickier that you estimate.
1)Map all the fields of qualified table with source fields whther they are qualifiers or non-qulaifiers.
- we will only be able to view the Non Qualifier field in the qualified table.
2)Now the main step is when you finish all field and value mapping there will be also a Target field name on your qualified table with values of display field. this field must be mapped to a source field to import qualified table. do value mapping also.
- This target field is the linkup field you are talking abot i feel, and it is viewed only in the main table and, as i have only on one non- qualifier this will not be a combination of any display fields.
3)I am not abl eto see the Non -Qualifier in my main table
So how do i proceed.
Kindly guide
Thanks
Simona

Qualifier and non qualifier fields

Similar Messages

Maybe you are looking for