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.

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.

How to separate non metric fields in Fact tables

Hi All,
I am having metric fields along with some non metric fields in fact tables(All the fields has to be present in fact table only). Is it possible to group all non aggregated fields and aggregated fields in the same fact tables. Please advise.
regards,
Guru

check this
OBIEE, Endeca and ODI: Fact and Dimension from single source Table
Thanks,
Saichand

It is possible to assign value range to non key fields in the table?

Hi,
I want to give some range of values to the fields which are non key fields in the table.
is it possible?
can anybody tell me the procedure.
Thanks in Advance,
venkat

HI,
It is higjly possible in case of Z-table. but in standard table you can't make any modification.
You assign the value range to the domain of field.
go to SE11 and open the database table.
Select the Data Element of the fieldto which you want assign the range.
Click on its domain .
click on Value Range tab.
Set the range.
Regards,
anirban

How to create a unique group field in Qualifier table

Hi,
I am trying to use a qualified table in Product maintable like "Site items".
However I would like to have two non-qual field in that like 'Plant' and 'item#' which should be an unique combination.
I have tried to create a table(X) with the above two fields with display and another table (Y)that uses the table X for lookup (site-item) so as to make it dispaly and unique both. However when i am using this Y table as a lookup for the qualified table(site items) , not able to load data.
Error message:
"Import failed. Unable to find source column index for 'Site Item ID' field"
Another issue also not able to populate data for the qualified flds even if when able to load data without making a group unique field for this qualified table.
In MDM 5.5 sp4. Thanks in advance for any tips.
-reo

Hi Beena,
In the above post of mine I suggested you to use STRING data type.
As you are telling that when creating TABLE MAINTANENCE GENERATOR you are
getting an error saying that " Datatype STRING is not supported ". I tried this, what you said is right.
After your reply I did research on this and I also met my heads,
The conclusion is <b>IT IS NOT POSSIBLE TO GENERATE TABLE MAINTANENCE</b> for the table which is using STRING type. At last I can give you one suggestion, i.e., In the short text of that field write STANDARD TEXT name.So that whenever you want, go to this standard text, but the problem is you have to maintain it manually.
<b>Reward all helpful answers.</b>
Regards,
V.Raghavender.

Calculated field in qualified table

Hello
I have created three very simple calculations i qualified tables. The calculated field as well as the fields that make up the calculation are qualifiers.
None of the calculated fields are updated!
I have tried to hit the recalculate button and calculated fields in the main table work without problems.
Is this a known limitation? What can I do to trigger the update?
BR
/Alexander

Hi,
This is not the case.
Suppose in Qualified table, you have 4 fields one Non-Qualifier and three Qualifiers say FNAME, LNAME and FULLNAME all of type text.
Now for Qualifier Field FULLNAME i define Property Calculated = Yes and In Calculation Expression I write as:
CONCAT(FNAME,LNAME)
So on updating Qualifiers Value value of Qualifier Calculated field FULLNAME get updated.
Suppose intially for a record i have qualifiers value as
FNAME LNAME
Mandeep Saini
FULLNAME = Mandeep;Saini
when i update value for these two qualifiers for the same record
FNAME LNAME
Alexander Isacson
then value in for Qualifier field FULLNAME get updated to Alexander;Isacson
i tried this and it is working fine.
Hope it will Help you,
Rewards if found Useful....
Mandeep Saini

Updating non alphabatic field in a table

Hi,
1) I am using Release 10.2.0.1.0
2) I have a table with phone number field which has some data issues..... the data i get is like
with data_Set as
(select '1-212-344-3453 (cell)' phone_no from dual union all
select 'pager 212-221-2211' from dual
) select * from data_setI want to update this column so that appropriate phone number gets updated to the table.
any suggestions?
Thanks

Hi,
This is a great example of the problems you can run into with poor database design. In this case you have overloaded the phone number field to also include the phone type. You should have split this data across two fields, one for the phone number and one for the phone number type. This would make it much easier to search for phone numbers or phone number types as well as make validaion of the phone number type much easier.
Also, you shouldn't store the dashes (-) with the numbers. These can be inserted on presentation with the use format strings. The actual format string you would use for each type of phone number could be stored in the phone number type lookup table.
Regards
Andre

Qualified table - Text Normalized field

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

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

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

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

Assignments in qualified tables

Hello I have managed to create some assignments formulas for some of the fields in the main table of the customers repository, however now we would like to use this same functionality or similar to assign values for fields in qualified tables.
is this possible at all? or is there any workaround?
Thank you!

You can assign values to the Qualified tables linked to Main table.
You will need to add the non qualified fields to the Qualified table and the qualified fields to the main table record.
Look at the API and you will find the ways to create/update qualifier values.
Hope it helps.
Avinash.

Import Manager and Display Fields

I've been using SRM-MDM 3.0 for a couple of months and 1 fundamental MDM design has always bothered me and I was hoping to get some resolve on this.
The purpose of Display Field is 2 folds:
1. Display the field in the Catalog Search UI for a lookup table: i.e. if both Supplier Name and ID are Display Fields, then in the Search UI, both fields are displayed to the end-user. If only Supplier ID was the display field, then in the UI only the ID is displayed.
- From a usability pov, tables such as Supplier and Product Group should have the name or description fields displayed in the Search UI as the numeric values are meaningless to the end-users.
2. Display field ALSO affect what is the key used to import data into a table. So if Supplier ID is the display field for Supplier table, then in Import Manager, the Supplier ID values are displayed and must be mapped to the source values.
- From an importing pov, mapping values should always be an index-like field, such as Supplier ID or Product Group ID, or ISO, and usually never the actual name or description field.
But SAP has tied the two together. So in order to display the name/description to the end-user, we must enable the name/description field as a Display Field. But we also want to map based on the index/ID field, so we also enable the index/ID field as a Display Field. Now in Import Manager, we have two Display Fields for a table (i.e. Supplier ID and Supplier Name for Supplier table) and I've noticed some issues with this:
1. You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible. What is funny is that standard SAP extract program only extracts the ID fields, BUT the standard SAP repository has the name/description fields as the Display Field. Automap is a must for tables like Product Group where hundreds of lines can make manual mapping a pain.
2. I also noticed you cannot Add values to a table that has 2 Display Fields, you can only map to existing values. The Add button is grayed out.
With all that said, when you're replication ECC Contract Data using MECCM, for tables like Supplier and Product Group, what fields should be set as Display Fields, and if there are multiple Display Fields, what special setting needs to be done in Import Manager to enable automapping? Even standard SAP Import Map (_MDMContractDataTransmission_ProductID) throws errors when multiple fields are set as Display Fields.
I'm not familiar with the partitioning function, and I've seen PDF's about it, but don't really see how it could be helpful. I've also read someone suggesting changing the DF's before import, which I think is unacceptable, as this requires unloading/loading repositories everytime an import happens.
Thanks for reading my paragraph and any input is greatly appreciated.
Edited by: Derek Xu on Apr 30, 2009 6:50 PM

Hi Derek,
Thanks for writing your thoughts. I would like to provide some information on one of your points where in you have mentioned that :
You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible.
I completely agree that if you have 2 fields in MDM repository and you are only importing only one of them, then you cannot use the Automap feature of Import Manager. So in your case, the description is not getting importing, so you cannot use Automap in that case.
I had a very similar requirement in one of my project and we went with creation of a Import Value template. We created a template with all the possible values for all the look up tables in that and mapped it once in the Map. Hence, next time, the Map was used to automatically Map the source and Destination values for all the look up tables.
SAP-MDM Automatic Import Requirement u2013 Creation of a Value Mapping Template:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
Please read the above article and hope its useful. You can go for this approach in your case if suitable.
I have mentioned examples of descriptions and their respective fields in the article.
Hope it helps.
Thanks and Regards
Nitin jain

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

SAP MDM DISPLAY FIELD AND UNIQUE FIELD DIFFERENCE

Hi All
I am new in MDM, can any body please help me understand...
What is the difference between display field and unique field?
Besides to consider one field to be a key in a lookup table, how should we declare that field in the table, as a display field or as an unique field?
It would be helpful if someone kindly explain this to me.
Thanks in advance.
Santanu Ghosh

Hi Santanu,
To explain you the difference in Display field and Unique filed as in MDM in a prescise manner:
Display field:
Every field you create under your main table ie Product atbel will be a displayed field in MDM data manger irrespective of you making it as display or not in Console.
It means two things
1) That this field will be visible in MDM data manger.
2) This field will be visible in Import Manager for Mapping.
But in case of lookup field you need to make the fields as dispaly or not,if you wish to see them in import manger.
If you do not make the fields in a lookup table as dsipaly then even though you can see them in MDM data manger you will not be able to see them in Import amnger as a result not be able to map them.
Unique Field:
When you make any field as unique it maens taht MDM will not allow you to add two values under this field with the same value.
Eg:You acnnot add two materials with material no 100.
Hope it helped
Kindly reward points if found useful
Thanks
Simona

Validation upon qualified tables

Hi,
Can anybody help me in writing one validation for comparing the field X of two qualified tables A and B.
The X values comes from two different client systems. The need is to check and compare the two values.
BR SK

Hi Susil,
Create new Validation in the main table only
Select the Field X from qualified table1 and another field from qualified table 2.
i.e. say Qualified1 and Qualified2 are the two main table fields of type Lookup Qualified then the validation expression would be
Qualified1.FieldX = Qualified2.FieldX
But the above validation will be helpful when you assign the value of FieldX in both the Qualified tables for same record.
If I interpreted your question wrongly then please let me know.
Regards,
Jitesh Talreja

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

Similar Messages

Maybe you are looking for