on 04-07-2010 6:24 AM
Dear Experts,
Does anyone know about Limitations in SAP MDM!!
Could you please let me know in detail??
Kind Regards
Eva M
Dear Aditya Dhurandhar - DHUA,
Spread your own DHUA, dont take credit of others...
Rather than copying others content, you should provide a link like below one...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eva,
What type of limitations are you refering to.
One of the major limitations that we have faced in our implementation is if the file size is too big, may be cause of the number of records and the fields mapped out it gets very difficult to manually syndicate the file. If you have any other specific issues could help on that.
In addition some general issue are
Sharing of Lookup tables (e.g. country) across repositories not supported. Linking of objects residing in 2 repositories is not supported with SAP NetWeaverMDM 5.5, natively.Workarounds via the integration into SAP NetWeaver Portal
Use of u201Ceventing technologyu201D mapping of key fields and match of respective values Not sufficient for each and every use case
There is no Migration options. One needs to manually make the changes right from development through to the production environment.
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).
One Major limitation that was there in 5.5 was we could only maintain a single Maintable. 7.1 solves that problem.
The following link gives some good examples:
http://www.it-director.com/technology/data_mgmt/content.php?cid=10837
Do let me know in case you need more help or if i was able to help answer your question
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Eva
If you are interested in knowing the limitations of SAP MDM the list will be huge. But there are ways and workarounds to overcome most of these limitations.
Adding to the list-
Change tracking for Qualified table not supported.
Matching performance issues when using tokens.
Fuzzy matching not supported.
Limited functionalities offered in MDM native workflows.
Roles/Authorisation for working on matching rules/strategy
Reporting from MDM
Deriving number ranges- ex: Achieving alpha numeric numbering in MDM
Complex calculations
..........
Best of luck!!
Ravi
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.