How do you imagine the team who are deciding the product names in SAP?

[HuseyinBilgen]

Do you need details?

Ok.

Lets say, SAP Portal naming progress: SAP EP > SAP NetWeaver Portal > SAP Portal

ERP: SAP R/3 > SAP mySAP ERP 2005 > SAP ECC 6.0 > SAP ERP 6.0

SCM: SAP APO > SAP SCM

SAP PI: XI > PI > PO

So, how do you imagine the team who are inventing the product names?

Are they someone thinking alone and then crying out: Eureka!

Or a group of people thinking about it?

Any idea?

[Florian · Accepted solution]

The next product name?

DATA: gv_string type string.

PARAMETERS: pa_leng type i DEFAULT 4.


CALL FUNCTION 'GENERAL_GET_RANDOM_STRING' "Creates a random strings
  EXPORTING
    number_chars = pa_leng           " i             Specifies the number of generated chars
  IMPORTING
    random_string = gv_string        " string        Generated string
    .  "  GENERAL_GET_RANDOM_STRING


write😕 gv_string.

~Florian

[Former Member]

I don't know exactly how, but they should endly tell they use a cat jumping on a keyboard. Everybody loves cats and all that cats do.

[JL23]

It might be freshers in the team who had only misheard the original term....

There are already discussions about Wetweaver in SCN

[Former Member]

Bunch of Marketing guys in a circle...

"Dude... what do you want to call this release?"

"Dude, I got it...  NetWeaver."

"Wait, WHAT do you want to call Netweaver?"

"ALLLLL OFFFFF ITTTTT"

All - "That's beautiful, maaan."

[Jelena]

Makes  ren *Netweaver* *HANA*  a breeze now!

[ChrisSolomon]

But back to the original question posed...."How do you imagine the team who are deciding the product names in SAP?"

Well, ever hear the saying "Could a million monkeys with typewriters produce the works of Shakespeare?".....THIS is how I imagine them EXACTLY!

[HuseyinBilgen]

I also forgot the below ones:

NW ACC > NW LVM

Sybase Afaria > SAP Sybase Afaria > SAP Afaria > SAP Mobile Secure

Sybase Unwired Platform (SUP) > SAP SUP > SAP Mobile Platform

[Colleen]

I think GRC was

Virsa > SAP GRC > SAP Business Objects GRC Access Control > SAP Access Control

People still using Firefighter which became SUPM (Super User Management) and then became EAM (Emergency Management)

That whole product suit has been flicking back and forth. I remember attending training a few years back and we all attempted to white-board the names.

My internals controls friend renamed them to Firestarter (must do fake guitar rock n roll call out) and RARA (Risk Remediations and Analysis which was also Compliance Calibrator). He had a few other names based on tv shows that his children would watch. They were just as informative and accurate as the product names SAP came up with. My only issue was accidentally putting his names in formal documents.

[Former Member]

I don't care what SAP call them now - they will always be Virsa & Firefighter to me.

[Colleen]

interestingly enough - the one name SAP didn't get to give the products

[Former Member]

From my and VA03's perspective, the whole thing is still R/2 and all this renaming is not needed.

I am also surprised that no one has mentioned BW yet..  🙂

Another renaming relocation flight series is transaction WUSL -> GTDIS -> WUSLTABL -> SE16N -> N -> TABLE_SCANNER -> V -> UASE16N -> TSRUN -> SE16H.

Cheers

Julius

[HuseyinBilgen]

Hi Julius

kishan P did mentioned BW. Here is another one.

SAP BCM (Business Communication Management  > SAP Contact Center

[Former Member]

!! Perhaps I did not believe my eyes...  😉

Hello there PK! 

[Lukas_Weigelt]

"WUSLTABL" sounds cute and hilarious from German Language perspective 🙂

I imagine it also involves exception messages like "WUSLTABL has stopped wuseling!"

http://www.dict.cc/?s=wuseln

[Jelena]

Whaaaat, they renamed Firefighter too? That's the only one that was at least descriptive...

[Former Member]

You mean SAP GRC EAM doesn't make sense to you? Really?

Anyway, that is the perfect name - a combination of three TLAs. How can anyone have a problem with that?

[Former Member]

The problem with EAM is that it is a TLA which has been used for two different solutions.

SAP GRC EAM refers to SAP Governance Risk and Compliance Emergency Access Management

SAP EAM refers to SAP Enterprise Asset Management, unless that, too, has  a new name which I have not heard yet.

SAP GRC EAM used to be SAP GRC SPM, GRC Superuser Privilege Management, but since that was its name in the 5.x releases, it got rebranded to a new name for the 10.x releases. Out here in customer land, many people still call it Firefighter, which was an even older name. Perhaps it is a misguided effort to get the customers to call it by a new name to definitely identify a new release, but old habits die hard.

Gretchen

[Former Member]

Like I said up above, and to mangle a Billy Joel song, it will always be firefighter to me...

[former_member184657]

What's up JB? Still keeping the Guestoblaster warm?

pk

[Matt_Fraser]

The first time I heard about "Firefighter," I thought it was a new Industry Solution add-on... you know, for fire departments.

[HuseyinBilgen]

It always reminds me the movie Fahrenheit 451.

A good quote from it:

"Is it true that a long time ago, firemen used to put out fires and not burn books?"

[Colleen]

Gretchen

what makes it worse is that it then became a debate on client sites as to when you should and should not use FF. I had the security and basis teams saying daily operations shouldn't be logged when that would be one of the key benefits. It came back to them say "but it's not an emergency". Further to that, "Super Users aren't support and SUPM is only for support"

I could imagine a branding chat going like.

So, this whole SUPM/EAM/FF needs a bit of a fix up

Yeah mate, what we you thinking

Let me process it a bit, throw some ideas together.

....returns later

I got it! This will solve all the confusion. We can call it Justified Access Management. JAM for short

I like it. Got a good ring. I'm in a JAM. Need help. We better socialise it first before we bring the media and art department into reviewing the visual aspect

Sure, no problemo! I'll go chat around the water cooler

.... return a few minutes later

$#@%! It turns out there's already a SAP product out there called JAM. Some thing to do with SF that no-one seems like but it's all about interaction and I guess the Jam with each other like a music session

Would the #### would have come up with a name like that? **rolls eyes** Okay, what's your other option?

[Former Member]

I know a number of customers who dont care what you call it. If they see it, then they dont want to process any tickets for it because it is a massive watchamacallit from a support perspective.

Some applications need to change their colours more often than others so that they cannot be googled easily...  🙂

Cheers,

Julius

[Lukas_Weigelt]

^ - POWL, probably

[Jelena]

Oh, great question! I don't believe thinking is actually involved there at all.

P.S. Did you not get the memo SAP PO is now SAP PRO?

[Former Member]

But PO and PRO still stand for the same thing, right?

[ChrisSolomon]

haha of course! How can you expect to confuse anyone if it is not truly confusing!??!

And next we will be calling it PRIOX so we can pull all previous acronyms together in one buzzword filled product!

*PRocess Integration Orchestration eXchange

[former_member184657]

Lets say, SAP Portal naming progress: SAP EP > SAP NetWeaver Portal > SAP Portal
ERP: SAP R/3 > SAP mySAP ERP 2005 > SAP ECC 6.0 > SAP ERP 6.0
SCM: SAP APO > SAP SCM
SAP PI: XI > PI > PO 

May I add SAP BIW > SAP BW > SAP BI > SAP BW, SAP BW powered by HANA... ?

pk

[Lukas_Weigelt]

[Matt_Fraser]

They are a small cabal of obscure conspirators who sit in a smoke-filled windowless back room and chuckle to each other, "Hehehehe, I know how we can screw with everyone.... let's change the product names again! Oh, and just to keep everyone guessing, we'll restart the version numbering as well, except instead of going back to 1.0, because obviously we don't want to be selling a 1.0 product, we'll make it 3.5..."

[SimoneMilesi]

Wait!

The uber alles tool isn't this?

[ChrisSolomon]

Let's further cloud it up with fixes and "mini release" bundles all bearing the name "pack" (like a package you get on Christmas!) with any number of names...service pack....support pack....feature pack....enhancement pack....pick any that suits you...just make sure their numbering is independent of the product versioning and as far from "common sense" as possible! And to further confuse everyone....let's throw in words like "role" into places where nothing security related actually applies but will drag as many additional people into "experiencing" our products!....oh and we would be remiss if we did not add the final cherry on top!.....make all initial documentation incomplete at best and full of errors....further solidifying the need for either "professional services" to complete the tasks or a Sherlock Holmes-esque problem solving brain to piece together the "mystery of the missing guide"...I mean, who needs documentation, right?...they can just contact support for immediate help (*chuckles so hard I fall out of my chair*).....then about two years or so later, let's finish up the documentation right about in time to announce the "new" version coming in 6 months which will make pretty much all of the existing documentation worthless.

Whoa...do I sound jaded?