SAP Retail Site Master Distribution is a monster of complexity. But in about 15 minutes, you’re going to be prepared to tame the monster.
This isn’t just a demonstration. In this short video, you’re going to learn the functional details of how this process works. With that foundation, you’ll be prepared to diagnose process failures.
Commodity Code data in SAP S/4HANA are completely different than in ECC 6.0; what you knew to be true in ECC 6.0 is no longer true.
There’s a new data model and new Fiori apps for managing Commodity Codes. The upshot is that your master data processes for Commodity Code require redesign, and master data processes for Material Master require redesign, including inbound interfaces that assign Commodity Codes.
Commodity codes in S/4HANA are now time-dependent, and valid for a material and a country or multiple countries.
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.
The Essence of SAP Retail Master Data — my recent blog post — was all about massively creating product data, location data, and product data that’s location specific. This video goes to the next level.
After you’ve brilliantly orchestrated master data to create master data — perhaps billion of rows — how do you maintain this over time … with least effort?
For that, you need to understand a concept called Reference Handling.
One of my seven granddaughters — Charlotte, the three-year-old — cheerfully reminded me of this truth. As they say, out of the mouths of babes!
Through example and repetition, her mother — my daughter — is teaching her daughter a foundational lesson. One that most humans learn to their unending profit. But, oddly, without an explanation rooted in self-interest (We never explained it quite that way to our children).
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.
This subject is like jumping out of an airplane. If you’re not afraid then maybe you haven’t sufficiently considered the scope, risk, and potential consequences.
The question: If master data is important then how much business importance should you assign to the master data used to create master data?
“Foundation” is an unsatisfying metaphor. Master data used to create master data — I’ll call this Reference Master Data — is more like a super-structure upon which master data is created.
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.”