Category: Data Migration

Load Inventory Balance in S/4HANA with LSMW

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.

3 Paths to S/4HANA, not 2!

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.

Simple eCATT Data Migration Example

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.”

You don’t have to be a techno-wizard to take advantage of eCATT basics.

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.

Site Master Data Migration: What, When, and How To.

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.