on 06-16-2010 3:55 PM
Hi
I need to have unique values in tuple.Please suggest way to achieve this
Regards
Aruna
Hi All
GDS doesnt support tuple and now we moved to Qualified Lookup tables. But in Qualified multivalued lookup needs to have unique values .Any suggestions?
Regards
Aruna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mandeep,
This is not possible as by making non-qualifier unique field you will achieve only uniques records in qualified looup table but when you create field atht is lookup to this field then that filed iwll allow to select same record more tahn one time as
for each record we can main different value for qualifiers.
LIke
vendor is my unique non qualifier
and
currency and price is qualifier
now this is possible that same vendor can provide same product in different price currency.
Please check at your end .
Thanks,
Sudhanshu
Hi Sudhanshu,
1stly, I also mean here that you can have Non-Qualifier Field Unique in Qualified table.
now this is possible that same vendor can provide same product in different price currency.
Like vendor is my unique non qualifier and currency and price is qualifier. For a field in main table which is look up this qualified table can have unique value for one Qualifed link(Non-Qualifier).
e.g. VendorID LQF(NQ) Currency Price
1 Vendor1 USD 2
Vendor2 IND 100
Here in above example Vendor1(NQ(qualifedOLink)) has unique values. It depends on your import Action in Import Manager, how do you want to maintian Quailified data. whether do you want to Append same Non-Qualifer(Qualified link) for same record of Main table. I mean you can have data also in this form if required.
e.g. VendorID LQF(NQ) Currency Price
1 Vendor1 USD 2
Vendor1 IND 100
It's again depend whether for same Qualified link do you want repeatable Qualifiers or unique Qualifiers
As above for a record Vendor ID which has same Quailified link Vendor1 has distinct Qualifiers. This is what i meant to maintain records for Qualifed table.
Obviously, across records of main table (different Vendor ID's) we cant validate whether it has Unique Qualifiers as we do have for simple text field of main table but for a single record (e.g Vendor Id=1) which has linkage to Qualified table, Its upto us whether there is need to maintain same 2 non-Qualifiers(apppend) value for same record(e.g. Venordor1) more than once or not.
Hope you got my point !!
Regards,
Mandeep Saini
Hi Aruna,
By looking all the possibilities, this is true that you can not apply unique field property to TUPLE.
more over as one of the post says validation can't solve this as it at record level.
So probally you can again check/review into Data Modelling. It may help.
Deep
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aruna,
Member fields of Tuple table does not support this Unique Field Property in MDM Console.
Why do you need Tuple field values as unique. Tuple is altogether separate concept unlike lookup Flat tables, Hierarchy tables etc, Tuple does not store data separately as we don't have this as a table, i mean as you can select main table and other flat tables to see the records in Record mode of MDM Data Manager, we do not have this for Tuple.
Tuple stores data while filling main table data only. So i don't think Unique key makes here much difference. Thats why SAP has provided Tuple member fields without Property Unique Field.
I agree with Ravi that using Validation you can not achieve this as it runs on record level not on Table level.
Regards,
Mandeep Saini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey,
As far as i know, we can not have Unique field in Tuples.
You might want to explore a little about Validations and see if that can help you achieve this.
Thanks
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.