I am not “all-in” on SAP S/4HANA Migration Cockpit.
Analysts warn that 83% of all data migration projects either fail or significantly exceed budgets. Like a poker table full of serious faces in a swanky casino, the stakes in data migration are sky high. Before going all-in on a single bet of such consequence, you’d better consider the big picture.
Yes, I understand that it’s the recommended tool for loading data into SAP S/4HANA, and has been for 5 years. And — for as many years — it’s been touted as the successor to Legacy System Migration Workbench (LSMW), which is no longer considered strategic. It’s not that SAP S/4HANA Migration Cockpit isn’t usable. After five years of steady revision, it’s achieved that mark, albeit with constraints. And it introduces important innovation, such as Direct Transfer, to transfer data directly from an SAP system. That’s all super-good news, but it’s insufficient information.
Data and business process owners: What numbers should we use for Products, Locations, Suppliers, Customers … and so on? A seemingly simple question, but the consequences of your answer are many and without end. Tread carefully!
Implementing SAP S/4HANA illustrates the universal subject, but with nuances that require your attention to stay clear of trouble.
As usual, observing a few experience-based principles can promote good outcomes for Master Data and business processes, now and in future.
The short answer to the question of WHAT — to plagiarize a phrase — is that your customizing golden client should contain no unnecessary master data, “for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts.”