Latest Posts

Latest Comments


What you need to consider when migrating SAP data


Posted by |

I’ve come across a lot of different scenarios over the past five years working on SAP Master Data Migrations. Unfortunately it’s not quite as simple as taking the data from the legacy system, modifying it in some way and loading it into SAP, the reality can be more complex. Here are five areas to focus on to ensure a smooth transition for all companies considering a SAP master data migration.

1. Business Processes
While it sounds obvious, it’s critical to identify the business processes that the data will support from the outset. This will in turn make identifying the right data to load easier. In some cases however, the SAP project team members may not be the people who really understand the business processes. Find out who does understand them and engage them as part of the project team. Make sure all processes are considered, even those that only happen once-a-year.

2. Identify the right data
It’s just as important to know what data isn’t required for loading, as is it to know what data is required, and to ensure that you get the balance right.  Get it wrong and data may be loaded that isn’t useful to anyone, slowing down the new system.  Don’t load enough data however and the live system may be missing data that is critical to support the business. To help assess what data is required check stock lists, check with your purchasing department, check with your customer services department, check with the finance department. Check what was bought and sold in the past, as well as who from and to. And check what history is required for reporting as this can also influence which data is loaded.

3. Quality, quality, quality
The data loaded will reflect the amount of time spent preparing it. Establish data quality standards if they don’t currently exist or if they do exist make sure that they’re enforced.  Data load files should have a consistent format and be kept simple. A simple format makes mistakes easier to spot. Load files should be quality checked at least twice before loading in an effort to reduce errors.

4. Start with clean data
The preparation of the data load is the best chance you’ll have to perform a cleanup during the lifetime of your new system.  Remove old data, correct inaccurate data fields, ensure rules are adhered to, and populate missing fields.  Yes, it will take additional time, but it will remove inconsistencies and improve your data quality, underpinning the new system from day one.

5. Use proven tools
If the data loading activities are to be repeated as part of a larger SAP software rollout, then it’s important to be consistent in the approach taken to writing LSMWs.  Even better, if possible, reuse the same LSMWs to load data.  This will help to ensure the consistency of your data loads.



Post a comment

Comment submitted! Comments needs approval before being displayed.