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

[Former Member]

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)

😎 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.

[Former Member]

Hi Shailesh,

Some corrections,

Tuple is replacement for qualified lookup, but its more restrictive than QL (validation are not allowed on multivalued tuple).

Validations can be written on multivalued tuples also.

Lookup main also has some limitations, performance issues.

Regards,

Pramod

[Former Member]

Hello Pramod,

Thanks for your response...

Well, there may be performance issue with Main table lookup...

But, I think SAP Developer team will fix performance issue prior to fixing all the qualified lookup issues.

Most of the people were waiting for qualified lookup solution from SAP for long time....

And 7.1 is a disappointment in that respect.

Again I don't know about how to write validations on multivalued tuple (well I will start new thread for this).

But, other than validations there are two more things with Tuple (correct me if I am wrong).

1. Role level constraints are not applicable for Tuple.

2. Tuple cannot be reference from Qualified Lookup and Visa Versa.

Also I doubt about assignment on Multivalued Tuple fields!

Thanks,

- Shailesh.

[Former Member]

Dear Experts,

Any idea about when Qualified Lookup & Tuple assignments will be available in MDM 7.1

Regards,

Shaailesh.

[michael_theis]

Hi Shaailesh,

there are some tuple enhancements, especially for multi-valued tuples planned for MDM 7.3. I don't know if these feature will be downported to MDM 7.1. Additionálly you should note, that tuples intend to replace the qualified lookup. Do not expect that new features for tuples are usable for qualified lookups, too.

As of the basic idea of using multiple main tables instead of tuples, this is not really a good one. You'll increase import and syndication tasks as both import and syndication can handle only one main table at a time.

[Former Member]

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.

[Former Member]

Dear Michael,

Do you have any idea about...

When the MDM 7.3 will be available for use?

Regards,

Shaailesh.

[michael_theis]

Hi Shaailesh,

as far as I know, the release is planned for later this year, Q3 or Q4. But I don't know a fixed date yet.

Best regards

Michael

[Former Member]

Dear Michael,

Thanks for the information...

Happy to see that MDM is growing in feature richness, and will be a great technology for mastering...

Thanks & Regards,

Shaailesh.

[Former Member]

Dear Michael,

Having mentioned by you that qualified table would be replaced by tuple going forward, but would tuple have a feature similar to "Filter qualified links" feature for syndication as it is there for Qualified table now. Because presently I am using tuple for mantaining company code data for mulitiple SAP systems and I cannot set filter in while syndication on company code specific to a SAP as this was possible if I had used qualified lookup table(Filter qualified links) for syndication. So we have to filter this at PI .

Will this feature be brought into Tuple going forward so that it can be handled in SAP MDM itself.

Best Regards

Manoj