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

Similar Messages

Source file structure when importing a qualified table

Hello MDM:ers
I need to import a qualified table into the following repository
(it is simplified to illustrate the problem):
Main table: Products
Fields: ID (int), Name (Text), Part number (Qualified)
Qualified Table: Part Numbers
Fields: Manufacturer (Lookup), Part Number (Text)
Lookup table: Manufacturers
Fields: Name (Text)
The source file is a very large text file that has the following structure:
Part ID          Name     Part no. Manuf 1     Part no. Manuf2
123          Nut     ABC               XYZ
456          Bolt     DEF               QWV
The result Im looking for Is to map a file structured a above so that two main table records are created (Nut and Bolt) which both have two qualified table records for each manufacturer. I have not been able to create such a map. I have tried to partitioning and combining fields without success.
I have no problem creating the map if I manually restructure the file to look like:
Part ID          Name     Manufacturer           Part Number
123          Nut     Manufacturer 1          ABC
123          Nut     Manufacturer 2          XYZ
456          Bolt     Manufacturer 1          DEF
456          Bolt     Manufacturer 2          QWV
It where a way to import the file directly in MDM without restructuring it?

Hi Alexander,
MDIS will not work fine if you have multiple tables as the mapping is saved only for 1 table. If you have multiple tables then after performing the process of Pivoting/Reverse pivoting, you will have to use joins.
Join the other tables as Lookup in the Main Table
Save all your configuration in a map. And then configure the map in the port.
It should then work with the MDIS also.
hope it helps.
Thanks and Regards
Niitn Jain

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

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

How to find table for structure field ???

Hi..
i need your expert help on this.
i am working on printing of terms of payment description. here there are explanation fields. it is coming from structure R052. and field name is TXT 02. here as per my understanding structure is coming from multiple tables so how i can find that from which table this field is coming??
thanks
h shah

Dear,
Well I cant say this is the solution for your issue, but have a look.
http://it.toolbox.com/wiki/index.php/Find_data_in_your_SAP_system_and_know_which_tables_do_what
DD02L - table properties
DD02T - table texts
DD03L - field properties
DD03T - field texts
How to find data related to a structure? With GREAT difficulty, but here are some ways (which will NOT work sometimes) to find specific fields if you know the structure's fieldname.
1) First, goto SE11, and enter your structure name. Goto the field that holds your data, and double-click on the element name. Once inside the element, do a where-used list for that element, searching tables only. Then go into each table, and see if you can find the one holding your data. There may sometimes be a huge number of tables displayed, but a lot of them will be empty.
2) Get the name of the program behind your transaction, goto SE80, and enter the program name. 99% of the time it will be part of a module-pool and bring up the pool. Goto the dictionary structures, and search each table there for the one holding your data.
3) Open a new session with transaction ST05, select SQL Trace, click on the Trace On button, and go back to your transaction (while leaving the session with ST05 open). Submit your transaction, and go back to the ST05 session. Click on the Trace Off button, then select the List Trace button. Continue with standard selections, and a BASIC TRACE LIST will appear. search thru the tables displayed under ObjectName.
and have a look at below.
You do know any transaction in which (related) data is used: 1) start the transaction 2) position the cursor on the field you want to have info about 3) press F1, then F9 4) now you see the technical information of the data element, such as table name and field name. 5) if the table mentioned is what you're looking for, you're done. It is also possible that the data element is in a structure and not in a table. Now you can either analyze the structure via trx SE11, or you can double click on the 'data element' field. In the next screen, use the 'Where used' button to find the tables in which this data element is used.
Additional tip: if you have found the table name, you can use trx SE36 to see the relationships of this table to other tables. You can use these relationships when defining queries, designing custom ABAP programs, etc. If you're lucky, one or more standard SAP logical database exist which contain the table you found in the previous steps. Proceed as follows: 1) start trx SE36 2) use the search help for the logical database name 3) enter the name of the table in the search help 4) press enter and, if you're lucky, you'll see a list of logical databases. Select one, press enter, select the radio button 'Structure' and press the view button. Now you'll see how this table is related to other tables.
And finally, I prefer, the simpliest way to contact the ABAP consultant for help.
Regards,
Syed Hussain.

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.

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

Expression with qualified table fields

Hi all!
I have 2 doubts concerning the free-form search and expressions using qualified table.
We're implementing SRM-MDM Catalog. Here is the scenario
The search is done in the Main Table (Products). The qualified table (Contract) has the following fields:
Contract ID: Non-Qualifier
Contract Item: Non-Qualifier
Contract Category: Non-Qualifier
Lower Bound: Non-Qualifier
Amount: Qualifier
Currency: Qualifier
Obsolete: Qualifier
There are 2 records in the Contract table assigned to the Product in main table:
123-1-Normal-1-100-BRL-False
456-1-Normal-1-250-BRL-True
1st doubt:
Using the free-form search, if I set the field Contract-Amount to be less than 150, only the record 123-1-Normal-1-100-BRL is listed in the result, which is ok. But if I enter in the expression option the formula Contract.AMOUNT<150, both records are listed:
123-1-Normal-1-100-BRL
456-1-Normal-1-250-BRL ???
Is this formula wrong?
2nd doubt:
The Contract info isn't a mandatory information. It's ok to have a product in the main table without a contract assigned to it. This can happen for example if all contracts for a product are obsolete. In the named search, if I select all products where obsolete equals to 'FALSE', only the records of the main table that have at least one valid contract are listed. As the contract info isn't mandatory, I was expecting a different behavior. Also the records that don't have a valid contract should be listed, but the contract information should be blank. Is there a way to do that?
Thanks!

check out these tables,
VBAK Header Data
VBAP Item Data
VBAG Release Data by Schedule Line in Sch.Agrmt.
VBUK Header Status and Administrative Data
VBUP Item Status
VBRL SD Document: Invoice List
VBPA Partner
VBKD Business Data
VBKA Sales activities
VBEP Schedule Line Data
VBRK Billing: Header Data (invoice)
VBRP Billing: Item Data (invoice)
VBFA Sales Document Flow
VTTP Shipment item
regards,
seenu

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 Text/Integer Field required in Flat Lookup table?

Hi,
I have a flat look up table.
In that i want to create 4 Flat lookup fields....... one of them will be a display field.
But when i Verify Repository with this structure then it gives me Fatal Error:
$$$ Fatal error(1323): Table 'Product Hierarchy'(A2i_24) does not have valid display field(s): 1:79;.
$$$ Invalid display fields are 79.
$$$ Table Product Hierarchy must have one or more display fields.
When i repair the repository......... it adds 1 Text Display field in my table.
Does is mandatory to have 1 text/integer field in lookup table?
If NO what i m doing wrong & if YES then Why?
Thanks,
Mahi

Sorry.......... Posted in Wrong forum.
Thanks,
Mahi

Qualified table field

Hi all
Can we able to enter the data in Qualified table field while creating the record in portal thru iView??
if posssible please let me know how to do the same in portal, i mean which type of iview we need to use to achieve the same??
Regards
Sunil

Hi Sunil,
As mentioned above you need to use Item details iView and select the desired Qualified table fields which are part of your main table. Now select the Relationship and Qualifed Display Fields radio button. Here a seperate entry will be made for each lookup Qualified field (which is part of main table) which you have selected in the item details view.
Now select a particular Qualified field radio button and select the EDIT button.
Now you will be able to select all the desired Qualifiers and Non-qualifiers from the Available Columns.
I have tried this scenerio at my end and its working fine.
Regards,
Kaushik Koli.

Updateble table with HTMLDB_ITEM.TEXTAREA not save text area field?

I use
updateble table with HTMLDB_ITEM.TEXTAREA that does not save text area field?
select a,b,
case when cond1 then APEX_ITEM.TEXTAREA(3, A_COLUMN,4,50)
recards
Edited by: sak on Dec 21, 2009 4:24 PM

Sak,
Unless I'm misunderstanding your situation, you've wandered outside the abilities of the automatic DML process to update your table. As soon as you use APEX_ITEM objects in your SELECT, you need to write your own table insert/update/delete processes to handle the updated values. The Advanced Apex documentation gives some basic examples for this, but I struggled with it the first time (because I was using a checkbox, which is handled differently than the other types).
For more assistance, try searching this forum for "APEX_ITEM".
Good luck,
Stew

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.

Qualifier Field Not Shown in Qualified Table

Hi All,
Can anybody tell me why the values of qualifier fields are not shown in the qualified tables? And where are those qualifier values stored, in the main table or in the qualified table itself?
Best Regards
Jerome

Hi Jerome,
Before starting, I am assuming there is no confusion relating to Qualifiers & Non-Qualifiers.
Non-Qualifiers --> Decidors/Fields whose value changes
Qualifiers --> Fields which get decided/whose value changes based on the Non-Qualifers.
You said - "Can anybody tell me why the values of qualifier fields are not shown in the qualified tables? "
1. )What I understood from your question is that; when you select your Qualified Table in the Record Mode of the Data Manager, the qualifiers appear to be locked/non-editable. Is that right?
All the qualifiers are locked because they have no context in the Qualified table.
For e.g.: If your Qualified table is "Addresses" consisting of
Non-Qualifiers --> Address Type(say Home(can be more than 1), Office,etc)
Qualifiers --> HouseNo,Street, City, Country,etc.
What would it mean if we put the street name "XYZ Street" for the record selected. Nothing -- the street must be connected to a main table record, a Customer(Cust_Id) and and an address-type(Home) to have meaning.
2.) If the above interpretation of your Q is not correct, then 2nd case could be --> when you select your main table in DM (Record Mode)and try to add a Qualified Lookup value to a record you are unable to see the qualifiers. Right?
In the main table Double-click on the quailfied lookup field. An screen pops-up. Here we see the available lookup records -- these are in fact the records we saw when we switched to view the Addresses qualified lookup fields, which means these are the values stored in the non-qualifiers. You have to select & add them (Selected Lookup Records). The qualifiers become enabled. Now you an add values to them.
You can either use an existing Address type or add a record to the Qualified-Lookup Table from here. We can add and remove types of addresses -- a main table record may have any number of any type of address. When we add a type, for example "Favourite Restaurant Address"(say), we can enter information for the qualifiers, those field which make sense only when connected to a main table record and a non-qualifier. If we add two "Home" addresses each can have it's own values for the City, Street, Country, State and Postal Code qualifier fields
To answer 2nd part of your Q - "And where are those qualifier values stored, in the main table or in the qualified table itself?"
Qualifiers are database subfields that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record.
Hope this helped your cause. Please mark helpful answers.
Regards,
Siddharth Sharma.

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

Qualified table - Text Normalized field

Similar Messages

Maybe you are looking for