Conclusion
The heterogeneous (and proprietory) nature of MDM's components and modules makes training and prototyping the first priority for an IT shop that has just embarked on a MDM implementation.

DBAs, System Administrators and Basis professionals should look very closely at MDM for opportunities to implement best practices learned on other application suites.

Solution Architects, Developers and Data Modelers should attempt to apply and scale their existing SDLC discipline for design, development, documentation and production-support, to MDM.

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.


A QuickStart Guide to SAP MDM 5.5

 Introduction
 Part 1: Select and Install MDM Components
 Part 2: MDM Components and Modules
 Part 3: MDM architecture: How components fit into the MDM eco-system
 Part 4: The OS/DB Product Availability Matrix for MDM 5.5 SP4
 Part 5: MDM for the Java Developer
 Part 6: Tips and Tools for the MDM Administrator
 Part 7: Migrating MDM Configuration
 Conclusion

This was first published in November 2006