Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
Boris_Rubarth
Product and Topic Expert
Product and Topic Expert
ℹ   This is the continuation of my previous blog Why SAP ERP 6.0 EHP6 contains SAP BASIS 7.31 which you should have read before starting with this one. Now in this blog, the journey on product releases and software component versions for SAP ERP and SAP NetWeaver continues, trying to dissolve latest mysteries.

A lot of news are out with the general availability of SAP products like SAP NetWeaver 7.4 (see SAP NetWeaver 7.4 made Generally Available (GA)) and SAP enhancement package 7 for SAP ERP 6.0. This blog focuses on the software versioning part of the story only, and on the ABAP part of SAP ERP: the SAP ERP - ECC server.

SAP NetWeaver: numbers simplified

The first nice part of the story is: things are becoming simpler. The product SAP NetWeaver 7.4 is using software components that have corresponding numbers, like SAP BASIS 7.40 and SAP ABA 7.40, to pick out two prominent examples. Even the kernel has version 7.40 now – I skipped this part of the SAP software world in my first blog - and you know why :smile:

SAP ERP 6.0 EHP7

And now to the business part of the SAP software: we have the EHP7 for SAP ERP 6.0, which is part of  SAP Business Suite 7 Innovations 2013.

The next nice thing of the story is: this version is based on SAP NetWeaver AS ABAP 7.4. So finally business ("Suite") and technology ("NW") use the same SAP NetWeaver foundation! This applys to the other parts of the SAP Business Suite as well (SAP CRM, SAP SRM, SAP SCM).

And with respect to the software component versions, both use SAP BASIS 7.40 and SAP ABA 7.40, see picture.

ℹ Only a part of all software components are shown in this figure

Software Component Version numbering again

I know that you have already anxiously examined other details in the figure … how about SAP HR? And SAP APPL? No further development has taken place in software component SAP HR, so it remains with 6.04. And for SAP APPL, development and adaptions have been done, so it becomes 6.17. But why 6.17 and not 6.07?

Two steps from 6 to 7
After "EHP6 for SAP ERP 6.0", the "EHP6 for SAP ERP 6.0, version for HANA" was made available, exclusively for the SAP HANA database. With this, the versions of the software components had to be increased. So the version number for SAP APPL was increased from 6.06 to 6.16, as one example. Now the next increase takes us from 6.16 to 6.17. That way, you still find a correlation between SAP APPL software component version number and EHP number.

That means the version sequence for SAP APPL is 6.00 -> 6.01 (EHP1) -> … -> 6.06 (EHP6) -> 6.16 (EHP6 for HANA) -> 6.17 (EHP7).

:!: Note that "version sequence" does not mean necessary update path: you can update an SAP ERP 6.0 EHP2 system directly to EHP7

Again, like described in the first blog, some software components may even stay to lower version as well, depending on your choice of technical usages during update. That is why ECC-DIMP is on version 6.00, as one of several possible examples.

ℹ Update

  • This blog was updated on October 14 2013, discussing now EHP7 for SAP ERP 6.0
    (instead of "EHP6 for SAP ERP 6.0, version for HANA"), so the title has slightly changed as well

Looking forward to your comments!

Best regards, Boris Rubarth

[Product Management Software Logistic, SAP AG]

21 Comments