Consolidating sap systems
We’ve done some of the largest, most successful SAP implementations around the globe.What we’ve found is that — unless you first do a data assessment — you spend a year getting all this design work done, but when you go to load your data, it won’t load into the system. Because the design doesn’t match up to the reality.
And yet, it’s this anecdotal information that steers the target configuration.Another hundred were used so infrequently (typically, just once) that it became clear that the business should not maintain them.We discovered that just eight terms codes could support 95% of this company’s customers without making any changes to their business.As a result, the new setup is almost always over-configured, under-configured, or ill-devised, and the data load, which takes place just eight weeks prior to go-live (per established ASAP doctrine), fails.Ask the financial controller of a large corporation how many different terms codes they use. Ask a CMO about the total number of active customers and vendors.), and some that raise questions about the way you want to do business.
There are upwards of 50,000 tables and five million fields in an SAP system.
Every SAP implementation, upgrade, or systems consolidation project is predicated on the idea that you will transform your business for the better. The project hurdles down the ASAP roadmap or a systems integrator’s variation of that roadmap.
But a data assessment is not done, and a real-world picture of how your business operates is never established.
Depending on the complexity of the landscape, the remaining 10% can take another week or so.
Once you’ve concluded the data audit, you’ll want to map your data to SAP.
This provides a holistic view of your business, your data, and your processes; by loading 100% of the data in raw form, you Let the Data Speak for Itself™ One large customer with multiple instances of SAP had paid for the configuration and testing of more than 1,000 terms codes globally.