Académique Documents
Professionnel Documents
Culture Documents
com/pub/wlg/22981
Blogs
Context
I received feedback from a reader of one my previous blogs which I’m grateful for. He mentioned the topic of the
product naming and the fact that many community members seem to have difficulties understanding the frequent
product name changes.
Being part of a community means helping out fellow community members and getting help from other community
members. The benefit of being part of the community is that everyone can get added value out of it.
Introduction
I was convinced I would find a previous blog or sources with this topic as I also know a lot of persons are having trouble
to understand the naming of the SAP products. While I found some information on specific products and their naming
history I did not find any general overview.
There has already been tumult in the past because of the frequent name changes that occurred. Gartner recently
criticized SAP for the frequent name changes of SAP products.
Just last summer I performed an upgrade from 46D to ECC 6.0 at a customer. They were confused which SAP product
was going to be the target of the upgrade, was it ERP 6.0 or ECC 6.0 or ERP2005? What about SAP Netweaver, do we
need that?
I will be using ERP throughout this blog as an example. I cannot cover every single product as it would be too much,
this information can be used for lots of other SAP products in terms of understanding the naming and versioning. I
added some sources in the blog for other specific products I could find information on.
Idea place
I hope by now you have heard about idea place, a new initiative by SAP which fits into the new way of giving customers
and partners a bigger input into the SAP world. Why isn’t there a central spot in the SAP service marketplace or on SCN
where you get an overview of all the different product versions with the date/time the product was released and
information to get rid of the confusion?
I have no clue, but since the Idea place exists, I created an idea to have such an overview, you can vote the idea up or
down depending on whether you like the idea or not and if there are enough votes up it will be implemented by SAP,
sounds nice right.
Please read to idea text for a better view on what I would like to see and please add comments to the idea so they can
also pick up your feedback on the matter.
You can vote on the idea right here:
Product name overview page (historical, future).
Not all products have to be on one page (nearly impossible) but a dropdown so you can select one and see a historical
view (past and future)of what product offered the same kind of functionality in the past and which product will take
over the task in the future would be a good start point.
Along with information about the technology platform (Netweaver?), the release levels (SR1, SR2 and their respective
SP levels), available EHPs (enhancement packages and their respective SP levels).
SAP (Systems, Applications and Products) was founded in 1972 and the first product served the purpose to do financial
accounting and was called “R/1”. The “R” stands for real-time data processing. The “1” stands for the fact that the
product was residing on a mainframe (no separate layer for database, application or presentation) so only one layer.
At the end of the 1970s “R/2” was released. “1” was changed into “2” because now it used two layers, (a
database+application and a presentation layer). Mainframe (database+application) and a terminal (presentation layer)
1 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
Now we come to a point where SAP introduced something new, a technology platform in addition to the product name.
The first technology platform to be used in the naming was WebAS (Web Application Server). Perhaps this was already
the start point for frequent name changes, adding technology platform naming to the product line and getting everyone
confused.
Some of you who read my blog on Java garbage collection basics know I fancy cars so let’s take a look at what this
means by an example involving cars (yes here we go again).
Picture 1.1
You can see the Porsche Cayenne on the left and the Audi Q7 on the right in above picture 1.1. Now what both cars
have in common is their platform. Both are build on the same base (the chassis, the wheelbase and even lots of parts
are the same).
The cars don’t look exactly the same; they don’t both have the same option list nor the same price. Each car on its own
(Porsche Cayenne or Audi Q7) is a different product but they are both build on the same platform.
You can very much compare this with how the technology platform for SAP works.
As explained above, SAP build a platform, the first being WebAS to be included in product naming or referenced when
talking/writing about the product. They also gave the WebAS a version (first one to be released was 6.10 if I’m not
mistaken). So you have your R/3 (real-time 3 layer SAP system) 4.x (version of your R/3) on WebAS (base platform)
6.10 (version of your platform).
Translated into SAP components this means you have specific components which represent your platform and other
components which represent your functionality build on that platform.
Once R/3 Enterprise 4.x came out things became even more confusing (we are still miles away from what we have
today).
Now the above wasn’t enough really, the Enterprise part was added to the product name because now they had split up
some components.
You can read the following information on the facts of the split up, to what purpose and so on:
R3 Enterprise.
So now you have your R/3 (real-time 3 layer SAP system) Enterprise (components split and possibility to use
extensions) 4.x (version of your R/3) on WebAS (base platform) 6.20 (version of your platform).
Lets recap
Let’s take a look at where we are so far to try and not get confused:
1. 1972 – SAP R/1 (R for real-time, 1 for one layer)
2. Late 1970s – SAP R/2 (R for real-time, 2 for two layers)
2 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
All the above name changing, additions to the product names wasn’t really enough. SAP started to use years in the
product name, for example mySAP ERP2004 in 2004. This is where it really plummeted down to the ground and people
got more confused than ever.
People started asking questions on internet and writing articles on the products and the confusion that existed, if you
are interested you can read the following white-paper about the confusion whether to go for SAP R/3 Enterprise or
mySAP ERP because they also released a mySAP ERP (2003?) version in 2003.
A new technology platform was created, SAP Netweaver in 2004. The previous platform WebAS became part of SAP
Netweaver but continued to be referenced. The SAP Netweaver 2004 platform contains the WebAS 6.40 (also referred to
as BASIS 6.40). One of the big changes SAP Netweaver brought is the possibility to have a Java Application Server (no
longer only ABAP was available).
ERP or ECC?
The story continues when the naming was again disrupted by the most important component of ERP. The term ECC 5.0
was used instead of mySAP ERP2004 which caused a lot of confusion in the customer base. The ECC (Enterprise Central
Component) component is the most important SAP component of an ERP SAP system.
At that moment you could have a mySAP ERP2004 (successor of R/3 Enterprise) which is in fact an ECC 5.0 (synonym)
which is build on the SAP Netweaver 2004 (Web AS 6.40) platform.
If that wasn’t yet enough it also mySAP ERP2004, ECC 5.0 was also referenced as being ERP 5.0. I didn’t look up every
single name change of the product because seriously I need to write a book to keep up with every single change and
I’m just writing about one single product here.
Things got even worse in 2005 when mySAP ERP2005 came out, which was referenced as ECC 6.0, resided on SAP
Netweaver 2004s (Web AS 7.00) platform and was also called ERP 6.0. Explaining this mixture of terms, numbers and
years to a customer makes the customer look like a UFO just flew by the window.
Enhancement packages
By 2005 SAP had already received lots of comments and feedback on the product names and the confusion. Because
they wanted to avoid that customers had to perform major upgrades frequently, the enhancement packages were
invented.
Enhancement packages serve the purpose not to touch the core components but to provide the customer with
additional functionality. Those additional functionalities become active after activation.
The version of the enhancement package is referenced in the product name, for example ERP 6.0 EHP1 (enhancement
package level 1). The latest enhancement package version has all the enhancements (additional functionality) of the
previous ones.
An overview of enhancement packages released for ERP 6.0 so far:
1. EHP1 for SAP ERP 6.0 in 2006
3 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
The platform on which your product resides and the product itself influences the versioning of your SAP system
components. Once you are logged into a SAP system click on system – status in the upper navigation bar.
Picture 1.2
This opens the system status screen; there click on the magnifying glass icon as shown in picture 1.2.
Picture 1.3
You can see in picture 1.3 that components SAP_ABA and SAP_BASIS are part of the Netweaver 7.0 platform (701 first
two digits 7.0). The last digit represents the enhancement package level (701 so Netweaver EHP1).
Picture 1.4
In the same SAP system when you scroll down you can see the component in picture 1.4.
There you see SAP_HRCCH and SAP_HRCCL are part of ECC 6.0 (604 first two digits 6.0). The last digit represent the
enhancement package level (604 so ERP 6.0 EHP4).
So this SAP system is an ERP 6.0 EHP4 on a SAP Netweaver 7.0 EHP1 platform.
The SAP kernel versioning is based on the platform your product resides on. For the above example, ERP 6.0 EHP4 on a
SAP Netweaver 7.0 EHP1 platform the kernel level is 701 (platform version + enhancement package version of the
platform).
The newer platforms that come out receive a higher second digit; SAP Netweaver 7.1 without enhancement packages
installed on it would have Netweaver components with version 710 and a kernel with version 710. The changes made
can be checked in the release notes of the platform on help.sap.com.
Business Objects
Business Warehouse / Business Intelligence:
Business One
Overview on SAP history and versions
SAP R/3 overview
Conclusion
I hope SAP does some effort to keep the product naming simple and understandable as it changed so many times in
the past it started to get confusing for almost anyone.
A community can be as powerful as its members and their actions. I’m convinced a lot of people would like to see an
overview page to have a better understanding of the confusing product names and I hope the idea gets launched and
implemented. It’s always a serious task explaining customers where the product name came from and clearing out their
4 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
doubts.
Tom Cenens is a SAP Technical Consultant for CTAC (www.ctac.be)
Hopefully I have cleared out some questions of fellow community members regarding SAP product naming with
this blog, you are free to leave comments (good and/or bad) to further improve my future blog writings. If you
have additional info to add to the blog or a correction, please post in the comments.
Comment on this weblog
Showing messages 1 through 30 of 30.
Now with ERP 6.0 EHP5 or SAP Business Suite 7 2010i (BS72010i) where 2010i stands for 2010 innovations.
Hello Manfred
Central Applications is apparently a usage type used for EHP5 which consists out of EA-APPL and SAP-APPL.
The name ECC isn't gone though, it's an ECC Server with usage type "Central Applications" :)
It's a real challenge to keep up with the product names, usage types and so on.
I'm doing a Portal upgrade from 6.40 to 7.02 and the maintenance optimizer in Solution Manager showed me the current usage
types and asked me to check the target usage types. One usage type was already checked although it doesn't exist anymore in
7.02, adding to the confusion.
Kind regards
Tom
To add to the confusion
5 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
I see in installation of EHP5 to ERP an usage type named SAP ECC Server Value Pack successor, i cannot find any information
about this usage type. You know what do this usage type?
In other hand, can you share with me , which usage type of portal do you refer.
To add to the confusion
2011-02-19 01:25:31 Tom Cenens Business Card [Reply]
Hello Manfred
The SAP ECC Server Value Pack (ECC-VPACK) is part of Central Applications now I believe. I don't think you can still choose
it an additional usage type when perform a sp-stack application through maintenance optimizer.
The Portal usage types also changed over time which can bring confusing situations. The best way to check the usage types
is too use the SAP Solution Manager maintenance optimizer but it isn't bullet proof either, it can give some confusing
situations when you upgrade from SAP Netweaver 6.40 to SAP Netweaver 7.0x or higher.
You have many possibilities for Portal nowadays so it would depends strongly on what you want to do what the portal.
Kind regards
Tom
In the beginning...
2011-02-04 10:30:42 Sean M Business Card [Reply]
You wrote: 1972 – SAP R/1 (R for real-time, 1 for one layer)
It was before my time, but legend has it that R/1 wasn't what you might think of as a mainframe product. It was run as a service
bureau: companies had to connect to the SAP office to access the system, it wasn't a product they could buy and run on their own
mainframe.
In the beginning...
2011-02-15 16:00:35 Gregory Misiorek Business Card [Reply]
In the beginning...
2011-02-04 22:07:24 Tom Cenens Business Card [Reply]
Hello Sean
Thanks for your valuable feedback :) I was born in 1984 so it's before my time as well. I based the content on information sources I
6 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
could find online (which doesn't neccesary make it 100% correct, even if it comes from multiple sources).
http://www.sap.com/about/company/history/index.epx
Kind regards
Tom
I have been doing Basis for 14+ years and know most of what you write about. However great way to put facts/dates and very specific
details and history. Great job!
Great Topic and great presentation!
2011-02-02 01:55:26 Tom Cenens Business Card [Reply]
Hello Raymond
Thanks for your feedback. I don't know if all is 100% correct as all those product names are so confusing but it should give a
somewhat better understanding how they got to the current state.
I'm awaiting a reaction on the idea on idea place (it has some votes).
Kind regards
Tom
I was under the impression that 46D was a Basis only release for R/3 4.6C. It was used by our old friend SAP Workplace (the first SAP
portal?) and had no business functionality as such.
SAP Workplace (the first SAP portal?)
2011-02-04 10:21:42 Sean M Business Card [Reply]
That's right, Workplace 2.0 was first. Why 2.0? Because no one wants to buy a version 1.0 :-)
Do you recall why the first EP version was 5.0? After WP 2.0, SAP was briefly a reseller of Yahoo! Portal 4.x (a now-abandoned
attempt by Yahoo! to enter enterprise markets). That was quickly followed by the acquistion of Top Tier and it's portal at version
3.0. EP replaced an install base of three different portal products, with most recent version numbers 2, 3 and 4. So the new product
obviously had to be 5.0!
7 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
Hello Michael
The point is that the product naming/versioning/packaging is confusing (the above again proves it) and that there are ways to stop
the confusion (reach out to the community and provide sufficient information to get rid of the confusion).
I think it would be a good improvement by SAP (which would be well received with the partners,customers, consultants and so on).
Pieces of the puzzle are available (like the year a product was released in the SAP service marketplace product availability matrix).
But the complete puzzle to give a simple and good overview with enough information isn't.
Kind regards
Tom
One question here, i thought ECC is the only product in ERP which has FI,MM,HCM,PS... Can you please tell me any other product in ERP
other than ECC
Regards
Vinoth
Thanks for the information
2011-02-15 16:04:59 Gregory Misiorek Business Card [Reply]
not only that...the current ECC 6.0 (60405) installation has SEM-BW as well and some cubes, just not the one I was looking for.
Hello Vinot
Perhaps you can find some product versions which have for example FI or Finance included by checking https://service.sap.com/scl,
choosing start application, then SAP Software Product Versions and Possible Scenarios and entering *FI* as input in field "By
Product Version Instance"
I'm finding new sources each day but many are confusing, not easy to work with and require a certain knowledge level (beyond
keeping it simple).
Even then it would require research work to see what the product offers and if it's usable or feasible.
8 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
Kind regards
Tom
and soon...
2011-01-11 16:02:50 Markus Doehr Business Card [Reply]
...there will be a
--
Markus
and soon...
2011-01-12 07:04:27 Tom Cenens Business Card [Reply]
Hello Markus
I agree and I do think we have not yet seen the end of confusing product names and packages, that's why I see added value in
having a product overview page (or pages) which makes it easier for customers to understand which product they are using, where
it came from and where it's headed.
Kind regards
Tom
Nice one
2011-01-11 03:04:37 Uwe Fetzer Business Card [Reply]
Hi Tom,
BTW: R/2 had release numbers, too (4.1, 4.3, 5.0), which reminds me of the classical joke:
A: "We are on 3.1i" B: "Ha, we are already on 5.0"
The characters after the R/3 releases (ie."i" in 3.1i) are so called "Put level" or short "put".
Regards, Uwe
Nice one
2011-01-11 03:16:36 Tom Cenens Business Card [Reply]
Hello Uwe
9 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
Thank you for your feedback and thanks for the additional information on the versioning.
Kind regards
Tom
Sergio
Evolution may also be represented with a timeline ..
2011-01-11 01:39:21 Tom Cenens Business Card [Reply]
Hello Sergio
Thanks your for the feedback. In my opinion a sort of timeline is a good solution to provide the neccesary information.
I'm trying to put together a sort of demo page to get an idea out there how it could look like.
It has to offer enough information. Not only the product and it's launch year but also the platform it residing on and sufficient
information to understand it all.
In my opinion it should also offer a search option and give you an idea where the product you are working on it situated and which
product is next in line to provide that functionality.
Kind regards
Tom
Thanks Tom
2011-01-10 05:57:39 Jim Link Business Card [Reply]
Great blog helping those of us relatively new to the SAP world understand (and try to make sense of) the history. We implemented at
the height of the name changes--started in 2005--and a lot of folks at our company have been confused ever since.
Thanks Tom
2011-01-10 06:06:37 Tom Cenens Business Card [Reply]
Hello Jim,
Thank you for the comment. I started 4 years ago without any knowledge of SAP what so ever and I too was puzzled when I
10 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
attented the first internal knowledge sessions and heard all the terms and versions flying around.
Kind regards
Tom
Hello,
same counts for BW (if this is the actually name of for datawarhousing component at SAP - not sure about - ;-) ), but a name is still
name.
Guido
BW has also strong - also naming - history
2011-01-10 06:01:02 Tom Cenens Business Card [Reply]
Hello Guido
Thanks for comment. Yes indeed, at the moment it's BI again as far as I know but who knows what it will be tomorrow. The link
provided in the blog gives a decent overview on BI versioning.
Kind regards
Tom
BW has also strong - also naming - history
2011-01-10 07:39:47 Paul Richardson Business Card [Reply]
I think it went:
It doesn't help that a lot of official SAP documentation still uses old names. For example, a lot of SAP PI documentation is still
referred to as SAP XI, even though PI replaced XI around 5 years ago.
Great blog
2011-01-10 05:16:19 Tammy Powlas Business Card [Reply]
I still wonder what the "Innovations" release was all about too - I think Enhancement Packages, but I am not sure.
Great blog
11 of 12 15-03-2011 18:56
SAP Network Blog: SAP product naming confusion http://weblogs.sdn.sap.com/pub/wlg/22981
Hello Tammy
As far as I can understand it myself, I think it's business suite + additional products? + enhancement packages for those products.
Kind regards
Tom
Hello,
SAP Business Suite is a bundle of applications (bundle of SAP products) which means it has SAP ERP, SAP CRM, SAP SRM etc to
provide a full set of tools to support any kind of business.
From a technical consultant perspective it's just a DVD with those products on it and you can install one or more products from the
installation DVD.
Kind regards
Tom
12 of 12 15-03-2011 18:56