by Jodee Hale-Schmid
November 11, 2010
Authored by Peter Aynsley-Hartwell, VP of Solutions Consulting, Utopia, Inc.
Users don't like the new system - why? Because they see the same information they had in the old system – but in a new format.How many companies have spent millions of dollars on a new ERP system, then added a few more for a BI system, then added Balanced Score Cards and very pretty dashboards, then the CEO still gets reports from an Excel spreadsheet. Ever wonder why? There are many reasons; however one we find common is that when the new shiny ERP system was implemented no one cleaned the data from the old system(s) BEFORE it was loaded into the new system.As a result all the reports that had wrong information before – still have wrong information – but they do look really pretty. :)Why does this happen? Often time it is because the data migration/conversion stream of the ERP project did not receive the attention that it deserved. It was left to the business – you know the old story – here is the file format we need – provide the data in this format and we’ll load it for you – but the responsibility for the quality of the data is with you.It doesn’t have to be this way. There are tools and processes available that help organizations structure the data migration stream of an ERP implementation project to minimize the risk of poor data getting into the new ERP system. These methodologies have been developed based on the experience of professionals that have been doing data migrations for many years and have used that to ensure the methodology is practical and proven to result in business ready data loaded into the new ERP system.
An email has been sent to:
In a digital economy that runs on speed, agility, interconnectedness, and massive amounts of data, organizations are increasingly looking to the SAP HANA platform to provide the capabilities they need...
As the volume of data collected by organizations continues to increase, so too do regulations designed to protect data from misuse, particularly when it comes to personal data. One of...
SAP HANA is here to stay — it is the default, in-memory database underlying every new analytic and transaction system of record delivered by SAP, including SAP S/4HANA. This means...
Please log in to post a comment.
No comments have been submitted on this article. Be the first to comment!
How to Create a Profitability Report Based on Custom Characteristics in SAP S/4HANA
Part 3: Implementing Security in BusinessObjects Universes with Security Tables
ChaRM Changes in Solution Manager 7.2: How to Transition Your Existing ChaRM Configuration Risk Free
See more »
SAPinsider is published by WIS Publishing, a division of Wellesley Information Services.
20 Carematrix Drive, Dedham, MA 02026 USA
Sales and Customer Service: 1(781)751-8799; firstname.lastname@example.org
© 2017 Wellesley Information Services. All rights reserved.
Online ISSN #2155-2444, Print ISSN #1537-145X
SAP and the SAP logo are trademarks or registered trademarks of SAP SE in Germany and other countries.