Do know that you have a data problem, before it bites you


How good is your data?  How well it meets the requirements of your new ERP system?  How much of the cleaning/migration efforts is automatically can and how much the business is going to have to do manually?  Unless you know the answer to these questions it is really hard to plan a data migration project well.

Therefore is the first phase of a data migration methodology it should be the data profile.  The tools that I prefer to use to do this are usually SAP BusinessObjects data insight and data services.

With these tools, together with basic knowledge of the requirements the development of a snapshot which can provide data in the legacy system can fit “Inside” how well it into the new system, what issues come and be available to set up an idea, whether the problems can be fixed programmatically, or if you need a human touch.

All too often at the last minute, the business is told that data is missing and the new system is not without it work.  You then run around frantically trying to get good accurate data or just your hands in the air cast and make ‘Default’-data only, to get something in the system.  Neither option is best.  This profiling as the first phase of the project to many of these types of situations at an early stage be identified and avoided.  The business get plenty of time, in order to collect the necessary data and to ensure that it meets the intended business must in the new system.

Paynsl Peter Aynsley Hartwell is Vice President – solutions consulting for Utopia Inc.

View the original article here

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
www.pdf24.org    Send article as PDF   
Posted in SAP MDM Tutorials | Tagged , , | Leave a comment

No rush at the end of the data – plan ahead!

One of the things I see all too often is that the data stream of a project to the last moment is left.  This makes it difficult to do system to test you, that you will find no real data to test with all kinds of problems – if the people concerned and stressed.  Get made up data, a few records, which bears no resemblance to the actual data that will see users in the system of production – and means nothing to you in connection with your legacy system.

It is any wonder then, that the user verify problems have, whether the system works not you can say how that should be it, because the data that was used to mean not everything for you.  It’s hard to say whether it is right or wrong.

The best way to overcome this problem is early for planning data migration and cleaning tasks, set up this with the ERP implementation plan and plan the first study data conversion (TDC) shortly before the first round of system testing done. In this way the user have to use real data to test and can relate to the functionality that you get from their brand new system, rather than complain about the bad data in the system, which all mean to you didn’t.

Paynsl Peter Aynsley Hartwell is Vice President – solutions consulting for Utopia Inc. Comment on this articleyou agree? What are your thoughts, after reading my experience?
Comment on this weblog

View the original article here

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
www.pdf24.org    Send article as PDF   
Posted in SAP MDM Tutorials | Tagged | Leave a comment