Converting a standard Plant into an SAP Retail Site Master is a niche topic. But it’s also a window through which to view the differences between these two business objects.
What’s more, SAP S/4HANA’s Industry to Core and the trend of Manufacturers with Retail operations combine to make the topic of Plants versus Retail Sites increasingly relevant.
What was true about Generic Article and Variants in SAP ECC 6.0 has changed from top-to-bottom.
With SAP S/4HANA, in keeping with SAP’s movement of Industry to Core, the implementation of the SAP Retail concept of Generic Article and Variants dramatically changed to align with concepts found in standard Variant Configuration (LO-VC). The result is significant technical change, but also significant business process change, as one would reasonably expect when master data concepts are rearranged.
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.
Excluding production, I’m regularly astonished by lax Security and Controls in SAP Landscapes. With S/4HANA, astonishment becomes concern.
I’m not talking about the blatantly obvious; no, we don’t regularly see SAP_ALL granted in Development systems as in days of yore. It’s more subtle than that, but perhaps not by much.
Is this Product authorized for business processes at this Location on this date?
In SAP Retail, Listing Conditions answer this simple question, but the complexity of producing the answer is massively underappreciated.
There are three main parts to the story: Data Management (business process), Execution (system process), and Listing Conditions (the result). And then there are common exception scenarios to be handled.
We use the words Reference Sites imprecisely. It’s a problem because there are many kinds of Reference Sites. Two, in particular, are often conflated and thus misunderstood.
Archiving is a tedious task! And so infrequently done, who can remember the steps? I’ve carefully documented it here so that you and I never forget again!
The steps for archiving Site Business Partner also apply to plain old Business Partners and dependent objects. So now you’ve got that in your bag of tricks too!.
Archiving is a seldom-executed process in the course of implementing SAP Retail. And archiving of Site Master is even less likely to occur, unless as a necessary corrective for mistakenly created data. That’s a less-than-ideal occasion for dusting off old or never-practiced archiving skills.
Worry not! You’ll be prepared for success with this detailed guide to archiving Retail Site, Business Partner, and dependent objects.
The SAP lexicon is fun. Similar or same words commonly describe different things, and different words describe the same or similar thing. As such, speaking precisely requires effort, if not blind faith.
This is particularly true in SAP Retail, where a so-called “Retail Text” was historically applied to rename business objects. Materials became Articles, Plants became Sites, and more.
With S/4HANA, Retail Text is no more. The standard labels Material and Plant appear on screens, not Article and Site. But not consistently.