Security and Controls in Development Systems

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.

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 (one 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.

SAP Number Range Shenanigans

The shenanigans of alphanumeric SAP Number Ranges are a surprise even to seasoned experts.

You’re likely well aquatinted with the mundane task of maintaining numeric number ranges for most business objects. The behavior is easily understood because the SAP system straightforwardly considers them as, well … numbers. Adding alpha characters to the mix is less common, and the resultant behavior is significantly less intuitive.

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.

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.