If you’re an SAP Retail functional person, it helps to be familiar with relevant IDocs. And if you’re a Master Data Aficionado, it’s kind of expected. This article explains the most common mistake made when attempting to create Generic/Variant Articles in data migration. It’s all about understanding the functional use of ARTMAS IDoc segments.
Data Migration doesn’t fit well into project tracking schemes. Unsurprisingly, the frustration of stakeholders eventually becomes palpable on every project.
The universal question I hear is: “When will the data migration deliverables be “done?”
If you ask me — the functional master data guy — when data migration will be “done” then the honest answer is clear: “The day before go-live.” When will the data migration functional specification be done? Same answer. Go ahead and ask the technical team when the data load program will be finished. “That depends on the functional specification. Oh, and you’re not going to change anything over time, are you?” For some reason, replies like these reliably produce eye rolls.
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.
You can load inventory quantity and value for materials in S/4HANA 2020 using IDoc Type MBGMCR04.
Yes, SAP S/4HANA Migration Cockpit is the “recommended by SAP” tool for loading data in S/4HANA. But there are exceptions to its efficacy. For example, IDoc type MBGMCR is exactly how it’s done in SAP Rapid Data Migration with SAP Data Services (On Premise), Migration Inventory Balances (W38).
If you’re not using SAP Data Services then Legacy System Migration Workbench (LSMW) is also relevant, using exactly the same IDoc approach that SAP delivers with Rapid Data Migration. What’s more, LSMW (more precisely, IDocs) remains essential for data migration in SAP Retail. For confirmation of necessity, see SAP Note 2538170 – Migration of Retail Objects to SAP S/4HANA on-premise.
MDA Workbench is a free and simple tool for creating such LSMW projects, and for creating a comprehensive kit of deliverables for data migration.
You’ll hear “greenfield” and “brownfield” used in common conversation about transitioning from ECC 6.0 ERP to S/4HANA. These two words — and too few words — cause more confusion than clarity.
To be clear, there are three scenarios for moving to SAP S/4HANA:
- New Implementation
- System Conversion
- Selective Data Transition
The first two receive wide attention, but the last is thought provoking.
My first experience with Extended Computer Aided Test Tool (eCATT) wasn’t much fun. In fact, I still cringe when I hear or say “eCATT.”
It would be fair to say that I still dislike eCATT. But the best SAP Functional folks are the best, in part, because they’re aware of every tool in their kit. And sometimes eCATT is the right tool for the job. In rare cases, it’s the only tool for the job.
You should know a bit about eCATT, even if you plan to avoid it, as I do.
This post captures a few quick notes about supporting multiple languages in your SAP implementation, and perhaps a surprise or two if you haven’t been down this road before.
Creating master data (and customizing, without customizing requests!) is a serious matter. Your data migration process better be executed properly and accurately. For one thing, it’s a tedious mess to clean up (archive) if things goes awry. Of course, as a Master Data Aficionado reading this article, you now have a plan for success.
Let’s begin by recognizing that your Site Master business process design dictates where and when you’ll be executing Site Master data migration.
Site Master Distribution is Best Practice in S/4HANA. If you’ve adopted that architecture then plan to execute Site Master data migration only in your Development Customizing Golden client. Then use Site Master Distribution to distribute those Site Masters to downstream systems-clients that require Site Masters.
Watch an end-to-end demonstration of using MDA Workbench to create a full set of data migration deliverables, including an LSMW object.
This 23-minute video is a good tour of the basic functionality of MDA Workbench.