Category: SAP Retail

What is Listing in SAP Retail?

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.

Archive SAP Retail Site and Business Partner

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.

SAP Retail Text?

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.

Commodity Code Conundrum

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.

SAP Retail for SAP (non-Retail) Experts

SAP (non-Retail) experts often encounter skepticism when joining an SAP Retail project.

If that’s you, then you’re likely thinking:  Hey, I’m an expert in FI, IM, MM, SD, or whatever. How much different could “Retail” be?

You got this, right? Well, maybe. Maybe not.

This quick read is first aid for mitigating healthy skepticism.

And it applies for both SAP S/4HANA Retail for Merchandise Management and SAP S/4HANA for Fashion and Vertical Business. I use SAP Retail as shorthand to mean both applications. Activating either Business Function brings foundational master data differences into play, and that’s where the skepticism begins.

The Secret of SAP Retail Master Data

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.

Merchandise Category Hierarchy: WHY (Business View)

Merchandise Categories classify Products, but in SAP Retail that’s a small part of the story.

Merchandise Category Hierarchy is relevant both for SAP S/4HANA Retail for Merchandise Management and SAP S/4HANA for Fashion and Vertical Business. SAP Retail is used in this document as a shortcut to mean both applications.

As context, let’s first differentiate between the two main product hierarchies that you’ll find in SAP Retail:

Merchandise Category Hierarchy vs Article Hierarchy.