1) What options are available for resending from MDM within XI or R/3 in case an update fails?
Ans. If the failure lies with XI or R/3, the same XML can be reprocessed (no resending is required). If there is a validation or data problem, the records needs to be identified and modified in MDM Data Manager Client and the Syndicator batch will resend them as they were updated since the last syndication.
2) How easy is it to maintain the front-end when the data model changes?
Ans. The effort depends on the number of fields required for the front-end. Fields that are added have no impact. Fields that are deleted (and maintained in the front-end), need to be removed. Fields that are renamed need to be updated.
3) Is it possible to develop web forms (outside of EP6) that link to standard Java MDM APIs and communicate with the MDM repository?
Ans.Yes it is possible as you are not limited to the use of iViews that exist. Your own application-specific iViews can be created. You can also access the server with direct calls to the API from the java environment. .
4) Is it possible to assign the saved search criteria to a role or person to restrict what he or she can view in the search?
Ans.The saved search option is client computer specific. That means that a user’s search criteria are available only to the user and not to other users. Therefore the saved search is not an option in this case. Using role constraints you may achieve the required results.
5) Are adapters/extensions available in MDM for integrating monitoring tools? (ie. does Tivoli register if an exception occurs in MDM?)
Ans. MDM currently does not trigger external processes on errors. The system uses logging capabilities to register errors and there are specific log files for the various components of the system. If the monitoring system/s can be triggered on changes to the log files then the system can be monitored. PREVNEXT>>
SAP MDM Online Training Materials
SAP MDM Online Training Materials
Most Frequently Asked Questions
1) Is it possible to hide certain fields and their values (depending on profile)?
Ans. The MDM security mechanism allows you to define constraints to be used for display and hide field values in MDM Data Manager Client. Currently the MDM capabilities do not allow you to entirely hide fields upon a constraint setting. However, you can use the APIs for building a User Interface to allow display/hide of fields and attributes as required
2) Is it possible to trigger external processes depending on type of errors raised, for example alert management functionality?
Ans. Currently an extended error handling with follow up processing is not on the roadmap. However, the usage of MDM Expression Language needs to be evaluated for this usage.
3) MDM stores change history in a separate database which can track the selected fields in any table, the before and after state of a record for that field and the user performing the change. As a result, if you activate too many fields or have frequent updates to the same field, you experience performance problems. How can I better manage this?
Ans : Limit the number of fields to be tracked to the minimum required. Establish an archive and purge procedure on the track changes log/database on daily basis to keep this database size to minimum, ensuring optimal performance.
