Qualified/Tuple

Hi All,
I have two remote systems R1 and R2, I am modelling a scnrio for materail master.
I have replaced all my qualified tables with tuples.
Main table
matNo Unit length width desc
mat01 BUn 10 20 TESTMAT - R1
mat02 BUn 15 30 TESTMAT - R2
Tuple
BUn Nr Dr AUn length width
EA 1 2 BX   10     20 - R1
EA 1 2 CT   10     20 - R1
EA 1 2 CR   10     20 - R2
EA 1 2 BAG   10     20 - R2
EA 1 2 BT   10     20 - R2
EA 1 2 CT   10     20 - R2
can a tuple have a remote key, i dont see any option, how can i check the with edit key mappings?
then how can i model this scnrio.......should i take this in a qualified table...... pls suggest me.
thnx,
ve

sravan, thanks for the reply
So, when I want to syndicate my data to remote systems, how will my data in tuples be segregated
mat01 BUn 10 20 TESTMAT - R1
EA 1 2 BX 10 20 - R1
EA 1 2 CT 10 20 - R1
mat02 BUn 15 30 TESTMAT - R2
EA 1 2 CR 10 20 - R2
EA 1 2 BAG 10 20 - R2
EA 1 2 BT 10 20 - R2
EA 1 2 CT 10 20 - R2
lets say I merge my above records, then I have a single record with ref to remote systems R1, R2.
mat02 BUn 15 30 TESTMAT - R2/R1
EA 1 2 BX 10 20 - R1
EA 1 2 CT 10 20 - R1
EA 1 2 CR 10 20 - R2
EA 1 2 BAG 10 20 - R2
EA 1 2 BT 10 20 - R2
EA 1 2 CT 10 20 - R2
So, How will my syndicaion work if I dont give a remote key for the data in tuple,
Is tuple right option for me or should I got with qualified table.
pls suggest.
rgards,
ve

Similar Messages

Qualified/Tuple work around

Hi,
I have a Qualified table with 3 Fields.
A,B,C.
A and B are poplualted automatically by incoming file.
Now i need to popluate C by comparing with main table field and A!!!!!!!
I have seen some Forum saying to create an internal interface, Which means create some dummy fieds in Main table and Populate result over there and Syndicate it back to MDM.
If i create a dummy field called Dummy C in main table, How does it populate values for each Qualified link.
i.e Lets say my record has 3 Qualified links.
If i write an assignment (Assignment result field ''DUmmy c'') and place this validation in Work flow,as soon as record arrived this WF triggers and the Dummy C should hold 3 values because there are 3 Qualified links to validate with!!!
But the Dummy field is a normal text fiedl which holds only one value at a time...
So this work around will not work for Qualified tables ???
Also i have the following assumptions..Please correct me if i am wrong!!
Assignments:
First thing i observed is WE CANNOT WRITE ASSIGNMENT RESULTS on Tuple/Qualified Fields.
Validations:
I can write validations across main table and Qualified table Fields
I cannot write validations across main table field and Multi valued Tuple
I can write validation across Main table field and SIngle value Tuple
I can write validations with in Multi valued tuple and not across main table.
KR
John

Hi,
Create a new Main Table (say main table 2) having below fields.
1. Main Table 1 Lookup of Type Main Table Lookup
2. A
3. B
4. C
Ok, So I have a maintable 1 with all the fields in the repository.
and Maintable 2 with the following fields.
F1 (Lookup to maintable 1) (Display Field)
A (Display Field)
B
C
i am a bit confused with your suggestion.
My key field for a record is material number.
This is located in maintable 1.
1 ) and when you said F1 is lookup main table 1 then does this mean that i will have material number in maintable 1 as display field.
2) also i will not have any qualified table in maintable 1.
3) and when i first time import the Qualified data to MDM i need to map the Incoming file to Maintable 2.
4) the incoming file should have material number, A and B.
5) Once loaded there will be a workflow which triggers assignments which will write the values in C.
6) But this second main table will have material number repeating in all the qualified multiple entries per site.
7) what will happen if the Main table one has more than one Display field init??
Is my understanding correct!!!
KR
John

BO XI issues with properties from BPC

Hi all,
I post again my message (it was not in the good forum) and I complete with answers to Andrey.
We created an universe on a BPC cube, after creation, we see all the properties of the dimension, but this is impossible to see the values of the properties, only their names.
Andrey asked "What do you mean by "to see the values of the properties""
What I mean is that if we make a request with WEBI on the universe, then we cannot see the values of the properties, ie I cannot see the value of the property "EVDESCRIPTION" in my request for example.
My colleague is trying to make a request that displays some accounts in line with the description of the account for example, and we can only see the ID of the account, but the EVDESCRIPTION property is empty each time, and this is the same with all properties of all dimensions.
Did someone already encounter this issue ?
Thanks

Post from thread: Re: BO reporting on top of BPC NW
Problem during Query development:
1. If we put unverse's dimension (in terms of BO) to Query and then execute query we can see the data from the dimension.
2. BUT
when we add an object "Measure" (for example YTD) to "Dimension" and run query - we have no data returned back. (even just Dimension data).
I found this issue documented in SAP note 1495455
It says:
Symptom
Business Objects Enterprise report has been created using the ODBO provider delivered with BPC 7.5 NW.
Report works well with only dimensions retrieved.
Same report using measures, gives error:
" The 'No data to retrieve. Query 1' "
Environment
BPC 7.5 NW.
Cause
This is because of the default behavior of ODBO provider.
If no restriction on any dimension, the ODBO provider takes the default member of a dimension to build the query.
The default member is the first member along a hierarchy.
The original ODBO comment is:
"We loop through our contexts and for each context, we create a
fully-qualified tuple consisting of the member as specified in the
context followed by the default member(s) of the
hierarchy(s) on the slicer axis as derived above."
Resolution
So the cube does not have transaction data and the WebI reports the no data message.
This is not a bug.
I took this to mean that you need to set a filter on each dimension (class in the Universe). Once I did this, I was able to get data.

How to replace a qualified table with Tuple

Hi Experts!
I have a Qualified table woth 2 non qualifiers,which refer to 2 lookup flat table and one text field which is Qualifier.
Now I want to replace this design with tuple.Please give me steps to do so and also how is the linking of field relation maintained in Tuple.
Thanks
Ravz

Hi Ravz,
Please refer the complete section 5. Migrating from Qualified Lookup Table to Tuple
Here, must check Page No 48/58 example for converting Qualified tbale to Tuple. It will solve your problem.
Sample: Manufacturer Part Number (MPN) in standard Products repository
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80765a21-78f3-2b10-74a2-dc2ab57a1bd2?quicklink=index&overridelayout=true
Regards,
Mandeep Saini

Workaround on all the limitations of Qualified Lookups, Multivalued Tuples.

Dear Experts,
As we all know, there are lots of limitations on Qualified Lookups in MDM 5.5 and also in MDM 7.1....
1) Can't write Assignments...
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
5) Role level constraints not applicable for Qualified lookup and tables referencing from QL directly or indirectly.
6) Qualified link level check-in check-out operations are not possible.
7) Qualified link level unique constraints are not possible (this becomes pain if links get duplicated by mistake)
8) Duplication of QL link is not allowed in data manager (for copying Qualifier values in new Qualified link).
9) Tuple is replacement for qualified lookup, but its more restrictive than QL (validation are not allowed on multivalued tuple).
10) ....... many more (which might have discovered by you all)
What if we make all the qualified lookups as main table and link those table to actual main table using Lookup [ Main] field type?
Well it will restrict the data analysis objective which is one of goal of Master Data Management...
But this will solve all the problems and limitations due to Qualified Lookup or Multivalued Tuple!
I think its feasible and technically possible (But only in MDM 7.1 onward)
How is the IDEA !!!
Thanks & Regards,
- Shailesh.

Dear Michael,
Thanks for your valuable replay...
Well out of 9 pain points I listed above...
Some of them may be fixed in future releases...
But there are some points which (I feel) may not be on the feature list of future releases like....
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
6) Qualified link level check-in check-out operations are not possible.
(all these points are applicable for tuples also)
Above points can be ignored at the time of fresh implementation
But its become blocker in new scenarios which are taken-up after go-live! (i.e expansion of already live repository)
Most of the people in MDM might not be aware of that import works on a single main table at a time.
Well you are an expert, what you said is something new and useful... Thanks for that !
Thanks & Regards,
Shaailesh.

Filter Qualified Link Checkbox set for tuples, But syndicated all Recs

Hello MDM Gurus,
With Reference to the answer below.. we have tuples and we are doing the same, but still we are getting all three links in the syndicated file.
I have tested this using flat syndication file.
Original Thread
Hello all!
Here is an issue we are working on. We would like to syndicate entries from a qualified lookup table for a particular customer, but only those where a certain qualifier has a specific value. For example:
Qual Table:
Non-Qual1; Non-Qual2; Qualifier.
Entries:
"AA", "123", "Yes"
"BB", "123", "No"
"CC", "456", "Yes"
So, when I syndicate this customer record, I would only like to syndicate those entries where the Qualifer = "Yes".
"Supress Unchanged Records" only works on the whole customer record and if the Search Criteria is set for "Qualifer = "YES", then it chooses the record (correctly), but syndicates all entries from the table.
Answer
Try using
Filter Qualified Links in the Map Properties of the Syndicator.
If activated, syndication results contain only the data selected in the Selection Pane.
Tick the check box under the Value Column for that property. By default that check box is not selected. You have to check it.
This works similar to the 'Filter' check box of the MDM Data Manger.
Limitation as of SP04
- One Global setting per map for qualified links plus one global setting per map for multi-valued lookups.
Please help us to resolve this issue. your input will be highly appreciated.
Thanks in Advance.

I need to synidate all customer records regardless of contacts linked to the customer.
A customer can have one to many contacts. There are several contact functions such as Primary, Sold To, Owner, etc.
When I syndicate the customer, I need to syndicate all Customer main table data and include Contact data only if the Contacts function = Primary, otherwise the contact data should be null in the syndiation.
A customer may have no contacts --> Syndicate Customer main table data, contact data is null
A customer may have theee contacts: 1 = primary, 2 = ship to, 3 = owner --> Syndicate Customer main table data and Primary contact data
A customer may have two contacts: 1 = ship to, 2 = owner --> Syndicate Customer main table data, contact data is null (since no Primary contact exists)
I hope this clarifies the requirement.
thanks
Tammi

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

QUALIFIED RANGE MAPPING/PI-MDM CONFIGURATION FOR AUTOMATIC SYNDICATION

Hi Experts,
I am setting up automatic import and syndication using an xml schema to a qualified lookup, will this be able to work? I made tuple to work but not with a qualified lookup even the mappings are all corrent, the import doesnt work.
We are using the MDM-PI Adapter instead of the File Adapter to automatically syndicate, Is it possible to create multiple channel? As when we configure the message starts to branch to the other channel since they have existing mapping but different remote port. Other port was configured as Manual while the new one was automatically to syndicate? Is there a workaround to this?
Many thanks!

Hi Elizabeth,
This is true that it uses only Numeric values while defining Qualified Range using Remote System of MDM Console.
But it doesn't allows to key the remote system details all alone for the internal number range as its using a qualified range.
I didn't get you exactly here, if you mean that you want to syndicate records on the basis of account number and want to generate customer number which is numeric then its possible. For this the Qualified field which is look-up to some sub-table, for this sub-table Key mapping Property should also be Yes.
Please refer step by step guide to make use of qualified range:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807ce1ba-94c0-2a10-a398-afdfd8135ebd?quicklink=index&overridelayout=true
Kindly let me know if you are looking for something else
Regards,
Mandeep Saini

Qualified table issue

My excel sheet has 3 coloumns taxcategory taxclassification taxclassificationdesc
my main table come with fields countrycode classification and others
i need to model this in my repository
I have metioned taxclassification as my lookup qualified table with fileds
1 tax classification   qualifier    lookup         flat     taxtypes table
2 country code          noqualifier lookup      flat     countries table
taxtype table fields taxcategory taxclassification taxclassificationdesc
when i load the values and see    i find that this has been modelled incorrectly
because it should have the below relations ship
countrycode taxcategory taxclassification taxclassdesc
IN MWST 0 NO TAX
IN MWST 1 FULL TAX
IN GST 0 TAXABLE
IN GST 1 50 PERCENT TAX
IN GST 2 low TAX
US IST 0 NON TAXABLE
US IST 1 FULL TAXABLE
MX PGT 1 FULLTAX
MX CST 1 FULLTAX
etc
so under MWST should have look up values 0 no tax
                                                                        1 full tax
          gst       0 taxable
                    1 50
                    2 low tax
          IST      0
                   1
urg pls
regds
ve

Hi Veena,
follow the step
1. First import data for Tax Category table as it's lookup table
2. then import tuple data example as follow
Material Number->Country->Tax_Category--->Tax_Class>Tax_Class_Desc
000000000010001-> IN-----> MWST -
> 0 -
> No Tax
000000000010001-> IN-----> MWST -
> 1 -
> Full Tax
000000000010001-> IN-----> GST -
> 0 -
> Taxable
000000000010001-> IN-----> GST -
> 2 -
> Low Tax
000000000010001-> US-----> IST -
> 0 -
> NON Taxable
000000000010001-> US-----> IST -
> 1 -
> Full Taxable
000000000010002-> US-----> IST -
> 0 -
> NON Taxable
000000000010002-> US-----> IST -
> 1 -
> Full Taxable
in above example Material Number is field of main table and all other are tuple fields map one to one field at destination side and select Material Number as Matching field in Match Records tab and import the data
Note : tuple records data can not import directly it require atleast one main table field and it should be display field then select this main fileds as matching field in match records tab then only it will allow to import tuple data
Thanks,
Jignesh Patel

Can MDM web service search results be filtered by tuple values?

We are currently working with MDM 7.1 SP03 and Netweaver 7.0. Right now, there is a requirement to return a material record from MDM to a Web Dynpro form using the MDM search web service. The other requirement is that the form user can search for a material using material number, sales org and dist channel. Currently, the results include all sales org/dist channel combinations in the material record. Is there a way to filter the results so that only the specified sales org and dist channel are returned to the form by using the web service? For example, if a material record has 2 sales orgs with different dist channels and the user is only interested in one, is it possible for the web service to return the material record and only the one sales org? Or, does this need to be handled by the form? Thanks for any input.

Hello Steven,
currently there is no filter functionality in MDM Web services 7.1 for tuple values or qualified
lookup values.
For the next MDM release we are planning to have a new operation for retrieving multi tuple
values as standalone operation, by which the user will be able to filter the
tuple values by member field's criteria.
Regards,
Matthias

Filtering Tuples at Syndicator

Hi,
I want to syndicate only the specific tuple values at syndicatorbased on the remote system
Example : I have 2 remote systems R1, R2 and tuple with 5 fileds .
Key tuple field contains 2 values T1- Specific to R1, T2 - Specific to R2
The record contains both the tuple values and it is available for both Remote systems
When i syndicate for R1, the record syndicates with both T1 and T2 values, ideally it should syndicate only T1
I have tried the following to filter the Tuple values :
1. Provided key mapping for these Tuple value - Not solving the issue
2. Tried to write expression, but unfortunately the tuple lookup values are not available in the expression lookup
Can you please help me to resolve this issue
We are able to filter it at PI level, but i would want to filter it at the syndicator side itself
Regards,
Antony

Hi Antony,
We cannot filter the tuple records based on the remote system.
This can be achieved using the qualified lookup table instead of tuple.
Regards,
Sravan

Syndicate only certain Tuple Records

Hi Experts,
We are using MDM 7.1 SP03. Is there any way that I can syndicate only certain tuple records?
Example:
Customer Master has two Purchase Organization records inside a multi-valued Purchase Organization Tuple. One record uses Purchase Org code = 4100 and the other record uses Purchase Org = 4005. Is there any way to syndicate out only the Purchase org record with code 4100?
I have tried to use the filtering options in the syndicator: Filter Qualified Links and Filter Multi-valued Lookup fields. This does not work.
I have the search parameters set to Customer records with Purchase org = 4100, and the customer record has two tuple records (4100 and 4005) the syndicator will push out both records. I only want the 4100 record to push out. Please help!
Edited by: Matthew Winchester on Feb 3, 2011 5:01 PM

-These records are not Remote System specific.-
-The search criteria using expressions do not work-
Example XML Structure:
<Account_Group>Z001</Account_Group>
<Name_1>Test, Inc</Name_1>
<Search_Term_1>HQ</Search_Term_1>
<Search_Term_2>Serach One</Search_Term_2>
<Street>Main Rd</Street>
<House_Number>300</House_Number>
<City_Postal_Code>12345</City_Postal_Code>
<City>Cumming</City>
<Country>US</Country>
<Region>GA</Region>
<Address_Time_Zone>EST</Address_Time_Zone>
<Transportation_Zone>XXX3432</Transportation_Zone>
<Language>E</Language>
<Remote_Key />
<Tax_Number_2>5464654654654</Tax_Number_2>
- <Vendor_Company_Code_Data>
<Company_Code>4005</Company_Code>
<Reconciliation_Account>4100000</Reconciliation_Account>
<Sort_Key>009</Sort_Key>
<Payment_Term>ZD22</Payment_Term>
<Double_Invoice>X</Double_Invoice>
<Payment_Term_Credit_Memos>ZD22</Payment_Term_Credit_Memos>
<Payment_Method>F</Payment_Method>
<Vendor_Withholding_Tax_Data />
</Vendor_Company_Code_Data>
- <Vendor_Company_Code_Data>
<Company_Code>1700</Company_Code>
<Reconciliation_Account>4100000</Reconciliation_Account>
<Sort_Key>009</Sort_Key>
<Payment_Term>ZD22</Payment_Term>
<Double_Invoice>X</Double_Invoice>
<Payment_Term_Credit_Memos>ZD22</Payment_Term_Credit_Memos>
<Payment_Method>F</Payment_Method>
<Vendor_Withholding_Tax_Data />
</Vendor_Company_Code_Data>
Senario: I export this entire record out using the syndicator. When importing into a different repository is there a way that i can ignore the segment with Company Code 4005, and only create the segment for company code 4100? It would be great to be able to handle this automatically....any sugestions? I need to be able to filter out certain company code records from importing, since there is no way to filter out during syndication, can this be handled using the Import Manager?
Edited by: Matthew Winchester on Feb 3, 2011 10:27 PM

Restrict Tuples Records while syndicating

Hello Gurus,
We are trying to syndicate Main table values with tuple values, we have a issue restrcting/filtering some of the records in the tuples table by using search tab - filter qualified link option in syndicator. it still shows up all records in the tuples after syndicating. Would you please advice how to restrict some of the records in the tuples table using condition.
Thank you very much in advance.

Hi Smartsoft,
Please ensure you are doing these steps as indicated in this link:
http://help.sap.com/saphelp_mdmgds55/helpdata/en/34/956878c37448828904c02e46050d6f/content.htm
Also go through page 6 and beyond to recheck your configurations:
http://213.41.80.15/SAP_ELearning/OKEC/nav/content/011000358700005402292006e.pdf
Hope this helps!
Thanks,
Ravi

Issues with syndication of multi-valued tuple fields

I'm trying to create a syndication map (using a schema) for a main table in MDM which includes a multi-multivalued tuple. The map generates an internal error on execution when I have the tuple fields mapped but executes correctly when I leave them unmapped. Has anybody else experienced this issue?

Hi Lori,
The Tuple syndication in MDM 7.1 works slightly differently than a normal lookup or Qualified mapping.
While syndicating tuple fields we cannot map the lookup Tuple field which acts as the linking field in the main table.
However you can map the tuple member fields and MDM syndicator allows you to map and syndicate them.
I have tried mapping and viewing the same and it works fine with me.
Hope It Helped
Thanks & Regards
Simona Pinto

Multi-valued Tuple Validation from Main record

Hi All,
does somebody know how I can do a Validation from the Main Table against multivalues Tuple field?
The option for validation on the tuple table (dropdown list of all tuples) doesn't work for me as I am able to set the validation there only against the Tuple member fields, but not with reference to the Main Table record standard fields.
I try to do the validation against the Tuple[Record] field, but it doesn't work, even that it works on the Qualified field.
I need to achieve the following:
1. We have records in the main table containing one multivalued Tuple field. The tuple field has 1 Display field, which is lookup(text) field against lookup table. In this lookup table we have 2 display field: Source and Code (The source can be "W1" or "W2");
2. We want to check:
- if the field X of a record from the main table = "W1" - the choosen Tuple record should not contain W2;
- if the field X of a record from the main table = "W2" - the choosen Tuple record should not contain W1;
I tryed with this validation: IF(X=W1,HAS_ALL_VALUES(TUPLE.[RECORD],"W2")), but it always gives me FALSE.
I tryed also with FIND but the result is the same.
Did somebody found a way how to do it?
Thanks&Regards,
ILIN

Hi Ilin,
This is achievable.
Firstly select Main table in Validation tab and create Validation say XYZ, write Validation expression as:
X=W1
Select W1 from lookups tab under assignment expression.
Write click on this validation and go for Edit Validation Groups, right click on validation Groups and Add Child
say X=W1 then Tuple <> W2. Select in Validation XYZ Group Property as X=W1 then Tuple <> W2 from Available Group to Selected Group.
Now Select this Tuple from drop-down under validation tab (not Main table). Since here you can see and select all the Fields of your Tuple only. Create a validation say ABC. Select the field in this tuple which is look-up to field which has values W1 and W2 Say this field is XX. Write Validation Expression as
XX.(record) Not equal to operator "W2"
I am not able to write Not Equal operator, so please select this operator from Operators tab under Assignment Expression.
Here since you can't select value from lockups tab, i mean disabled then manually write W2 (Case Sensitive) within double quotes. Also make sure that here you too add Validation ABC Group propery as X=W1 then Tuple <> W2 from Available Group to Selected Group.
Now select any record in main table, right click on it Validations>Execute Group>X=W1 then Tuple <> W2
You will get your desired result. you would able to see two columns under Records with name XYZ and ABC, if both of this has tick mark Only then validation is considered to be successful. if any of this has cross mark, i mean if X = tick mark symbol and XX = cross mark Symbol then this validation considers to be failed and vice-versa.
You can similarly do for below too.
If the field X of a record from the main table = "W2" - the choosen Tuple record should not contain W1;
Just check it and revert with result. This is working fine at my end.
Regards,
Mandeep Saini

Qualified/Tuple

Similar Messages

Maybe you are looking for