SAP NetWeaver MDM [EOL] Review

We can deploy cross-client front ends to allow visibility and data maintenance across multiple offices and clients, but core components requires the removal of limitations that SAP has implemented.


Valuable Features

  • Data Synchronisation
  • Comparison

Improvements to My Organization

With the ability to deploy cross-client front ends to allow visibility and data maintenance across multiple offices and clients, this has allowed the data accuracy to excel and produce much better results instead of bottleneck execution of updates.

Room for Improvement

The core portal components of NetWeaver MDM requires the removal of limitations that SAP have implemented, i.e. only allowing single selection of an export method to closer mimic the Main GUI “Data Manager.”

Use of Solution

I've used it for seven years, since v5.5.

Stability Issues

The core stability of NetWeaver MDM has been in question over the last 12 to 16 months with releases containing fatal flaws that should not have passed simple quality testing, or the introduction of old errors that had been fixed in prior releases.

Customer Service and Technical Support

It's less than manageable, as since the closure of SAP offices which included the original development team of NetWeaver MDM, the support and stability of the product is no longer on par. With SAP not being able to determine the EOL date, which is either 2020 or 2025, the future of a once excellent product no longer looks promising.

Previous Solutions

We were the first client in Australia to Implement NetWeaver MDM as SAP ECC. It was decided to introduce NetWeaver MDM over others that where presented to us due to how the product was defined/pitched and the results that could be gained.

Initial Setup

Unfortunately as a retail environment, the initial concept of NetWeaver MDM v5.5 was not viable for the retail sector, and took 18 months to release to the business as a concept. This was due to the product being more focused on the manufacturing and publishing sectors.

Implementation Team

The implementation was carried out between in-house team and a third party. For implementation, a business needs to use the full features of a product as for the time/money we spent, we cannot provide an expected return. If a system that is being implemented or looked at can replace/enhance a current process, then spend the time to understand this properly before implementation.

ROI

Our ROI is the access to data and maintenance that was not possible through standard SAP at the time.

Pricing, Setup Cost and Licensing

The pricing/licensing model differs between vendorsIf looking to implement NW MDM ensure that the business is ready for change from process to execution. This is a fundamental requirement for implementing a Master Data Management platform. If the business is not you will not be able to see the full realisation of what NW MDM can provide and the enhancement it can bring to multiple sectors of the business.

Other Advice

If you are looking to implement NetWeaver MDM you shsould ensure that the business is ready for a change from process to execution. This is a fundamental requirement for implementing any Master Data Management platform. If the business is not ready, you will not be able to see the full realisation of what NetWeaver MDM can provide and the enhancement it can bring to multiple sectors of the business.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email