Category: MDA Magazine

The Essence of SAP Retail Master Data

The essence of SAP Retail Master Data is manifested at the intersection of Products and Locations. We also call them Articles and Sites, or Materials and Plants. Take your pick; the SAP lexicon is forever morphing for your enjoyment 🙂

Whatever you call them, the number of Products times the number of Locations is a big number in SAP Retail. It quantifies the Retail Master Data challenge, and billions is the typical unit of measure.

You’ve got to massively create and maintain product data, location data, and product data that’s location specific. Yes, please, and with least effort.

A central concept permeates SAP Retail Master Data to enable master data creation: using master data to create master data. If you get your head around this idea — even at a high level — then you’ll begin to grasp the elegance and uniqueness of SAP Retail Master Data.

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.

Peeking Behind the Curtain of S/4HANA Business Partner

Of all that you’ve likely read on the topic of S/4HANA Business Partner, it’s typically not clear – or simply said – that Customer and Vendor Masters fully exist in S/4HANA, exactly as they did in ECC 6.0. They’re just hidden behind Business Partner.

What’s more, and to the point, SAP S/4HANA Sales and Distribution (SD) and Materials Management (MM) modules — and many others — remain blissfully unaware of Business Partner. They continue to use only plain old Customer and Vendor Masters.

Full stop! What does that mean for your Business Partner master data design in SAP S/4HANA ERP? It means that you’re more responsible than ever for the maintenance and outcome of Customer and Vendor.

Years after introduction, plain statements such as these about the S/4HANA implementation of Business Partner – practical implementation advice for SAP Architects and SAP Master Data practitioners – remain in short supply. Written hot on the heels of surviving the crucible of multiple implementations of S/4HANA ERP in 1709 and 1809, this document aims to mitigate that deficiency.

Let’s take a good, long peek behind the curtain, shall we?

Profit Center Number Complexity

Profit Center number decisions that add complexity.

Your decision for Profit Center numbers can add ongoing operation costs and complexity, especially in SAP Retail.

We’re talking strictly about Profit Centers in Material Master that are assigned for each Plant (MARC-PRCTR).

The Best Practice in SAP Retail is that only one Profit Center per Plant (Site) is relevant for all Materials (Articles), and that the Profit Center number is the same as the Plant number.   

Profit Center number = Plant number. Simple. But why is this Best Practice? What pitfalls await those who deviate? And how is Best Practice implemented? Spoiler alert: it isn’t standard, and that’s standard!