Skip to Content
Technical Articles
Author's profile photo Juan Tena

ABAP Platform – Part 1 – Evolution from SAP Netweaver

As technical architect, I am often asked about the latest news in the technical area of SAP S/4HANA. In these 4 blog posts I would like to review the main changes and innovations that SAP have introduced in the last years to explain the evolution SAP Netweaver platform  towards the new ABAP platform from a technical perspective.

I have divided the content in 4 blog posts:

 

PART 1 – Evolution from SAP Netweaver platform

The SAP kernel is the core component of any SAP system. It consists of the executable files that run on the server to handle connections to the system and execute the SAP programs.

The development of the SAP kernel started in 1988, although SAP R/3 was officially launched in 1992. The SAP kernel has been the foundation for almost all SAP products in the last 30 years.

Over the years, the kernel and the basis layer evolved. Adding support for more databases and operating systems but also adding more functionality.

One of the first important changes were done in 2002 with SAP R/3 4.7 and the inclusion of the SAP Web Application Server. It was the .COM era and SAP Kernel was extended with the Internet Communication Manager (ICM) and Internet Transaction Server (ITS) to be able to manage HTTP connections and provide support for XML, BSP and JAVA.

SAP NetWeaver was released in 2004 as a technology stack that allowed organizations to integrate data, business processes, elements and more from a variety of sources into unified SAP environments using a common technology platform. For the last 16 years, SAP NetWeaver has been the technical foundation for the SAP applications.

Evolution%20of%20the%20SAP%20Basis%20and%20SAP%20Netweaver

Evolution of the SAP Basis and SAP Netweaver

 

In 2008, SAP released the SAP Business ByDesign, the first SaaS product developed by SAP. After 20 years, a major renovation was needed as the SAP R/3 Kernel code was huge and complex, so a new kernel was developed, new ideas and improvements were implemented. Internally at SAP this new kernel was called Kernel 8.x and the project was called NGAP Next Generation Platform.

Obviously, SAP HANA deserves a special mention in the evolution and modernization of the SAP products. Although SAP HANA was officially launched in 2011, the first SAP ERP 6.0 version compatible with SAP HANA was launched in 2014 based on SAP Netweaver 7.40 SP02. Many new ideas and improvements implemented in the SAP Kernel 8.x were down ported to the SAP kernel 7.x line together with all the HANA and FIORI specific innovations.

SAP offers “innovation without disruption”, so the idea has been always to introduce new functionality but maintain as much as possible the backward compatibility to let customers adopt the technical (and business) innovations at their own pace.

If you have a look at the architecture of the SAP Business Suite and the underlying SAP Netweaver platform, you can see a perfect example of this “innovation without disruption” approach that makes SAP technology a solid platform to run complex business software. For more than 15 years, the evolution of the SAP Netweaver platform offered a solid foundation to adopt new technical innovations to our SAP Business Suite customers.

 

SAP%20Netweaver%20and%20ABAP%20Platform%20kernel%20versions

SAP Netweaver and ABAP Platform kernel versions

 

As you know, support for SAP Business Suite will end in 2030. SAP offers SAP S/4HANA as the evolution of the SAP Business Suite products and customers need a new technology platform to run their business.

It’s important to remark that SAP NetWeaver is a product family consisting of more than just ABAP and Java Application Servers, it contains other components like the BI Content Extension, the Advanced Adapter Engine Extended, etc… and also contains the SAP Netweaver hubs such as Business Warehouse, Enterprise Portal or SAP Process Orchestration.

The last SAP Netweaver version as  a full product is SAP Netweaver 7.50. Customers running old SAP PO or Portal versions cannot upgrade beyond SAP Netweaver 7.50.

There are, however, 3 new updates for one of the SAP Netweaver components, the SAP Netweaver Application Server ABAP component. These 3 new updates of the SAP Netweaver Application Server ABAP served as foundation for first S/4HANA versions:

  • SAP NetWeaver Application Server ABAP 7.50 (for SAP S/4HANA 1511)
  • SAP NetWeaver Application Server ABAP 7.51 Innovation Package (for SAP S/4HANA 1610)
  • SAP NetWeaver Application Server ABAP 7.52 (for SAP S/4HANA 1709)

These 3 Application Server ABAP versions were still compatible (at kernel level) with the “old” SAP Netweaver versions used for SAP Business Suite products but delivered innovations for the ABAP stack in the following areas:

  • Are the technical foundation of the first S/4HANA Releases (1511, 1610, 1709)
  • Include a new ABAP programming model for FIORI apps which is already based on Core Data Services and will be the foundation of the future ABAP Restful Programming model (see more on this in my next blog ABAP Platform – Part 2 – New programming models)
  • Include a new version of the SAP_ABA software component, the new versions are alphanumeric (7.5A, 7.5B, 7.5C…) instead of the classic SAP_ABA 7.50 used for SAP Netweaver 7.50 and SAP BS 6.0 EHP8

The new SAP_ABA software component is an important change, as the new SAP_ABA 7.5A,B,C contains changes in the field lengths, etc… needed for the S/4HANA simplification. As an example:

  • SAP_ABA 7.50: traditional MATNR e.g. for   SAP NetWeaver 7.50 and Suite EhP8
  • SAP_ABA 7.5A: new, long MATNR for S/4HANA

We cannot say that S/4HANA is based on SAP Netweaver (full product) as it is only based on one of the components (SAP Netweaver Application Server ABAP) and didn’t contain a JAVA stack nor the SAP Netweaver hubs (BW, Portal, PO)

This discussion about the differences between SAP Netweaver (full product) vs SAP Netweaver Application Server ABAP (one of the SAP Netweaver components) is already complicated enough for majority of our customers, but to make it even more confusing , there are 2 standalone shipments: SAP NetWeaver AS for ABAP 7.51 Innovation package and SAP NetWeaver AS for ABAP 7.52.

 

These 2 shipments contains AS ABAP only and the main purpose is to  use it as a development platform to develop and run innovative FIORI applications using the new ABAP programming model for FIORI apps (see more on this in my next blog ABAP Platform – Part 2 – New programming models)

If you are looking for a more detailed discussion about the main changes introduced in the Application Server ABAP 7.51 and 7.52, please check the following notes:

 

The Application Server ABAP 7.50 for S/4HANA 1511, The Application Server ABAP 7.51 for S/4HANA 1610 and The Application Server ABAP 7.52 for S/4HANA 1709 can be considered as a transition platform towards the new ABAP Platform that is the foundation of the S/4HANA products starting with S/4HANA 1809.

From%20SAP%20Netweaver%20AS%20ABAP%20to%20ABAP%20Platform

From SAP Netweaver AS ABAP to ABAP Platform

SAP NetWeaver Application Server for ABAP 7.52 is the last version of SAP Netweaver AS for ABAP, currently SAP has no plans to deliver additional SAP Netweaver AS ABAP versions although the existing Netweaver platform will be maintained until the end of 2030 as part of the SAP Business Suite end of maintenance policy.

Don’t get me wrong, the kernel 7.53 and the Application Server ABAP versions used as the foundation for S/4HANA 1511, 1610 and 1709 had many technical innovations and there has been also modernization of key components like the new Enqueue Server (ENSA2), support for HTTP/2 protocol and many internal changes to keep SAP as a modern platform to run your business. But the idea was to keep the compatibly as much as possible and allow a gradual transition for our customers:

Evolution%20of%20SAP%20Netweaver%20towards%20ABAP%20Platform%20-%20Full%20stack%20view

Evolution of SAP Netweaver towards ABAP Platform – Full stack view

With SAP S/4HANA 1809 there is a big change, S/4HANA 1809 runs on top of the new ABAP Platform and it’s based in a new Kernel line (Kernel 7.7x) breaking the compatibility with the old kernel 7.53 used in the old SAP Netweaver systems.

ABAP Platform is the foundation for SAP S/4HANA and shipped as part of SAP S/4HANA, there will not be standalone versions.

Want to know more about the stack changes in 2020? Have  a look to Roland Kramer’s blog post: Upgrade to S/4HANA 2020 – Time to change

In my next 3 blog posts I will discuss in detail what are the main changes introduced by the ABAP platform in 2 different areas: programming and basis

 

Assigned Tags

      24 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Sumit Jaiswal
      Sumit Jaiswal

      Thanks for this nice post Juan Tena !

      You wrote that SAP Netweaver 7.52 is the last version of SAP Netweaver. Do you mean it for independent NW system only?

      Though not shown in your images, isn’t SAP NW 7.54 a technical foundation of S/4 HANA 1909?

      Author's profile photo Juan Tena
      Juan Tena
      Blog Post Author

      Hi Sumit,

      This is a common misconception, you have all the versions and components described in the figure “Evolution of SAP Netweaver towards ABAP Platform – Full stack view” at the end of the blog post but, for clarity, let me try to add some additional details:

      • SAP Netweaver has been our technical platform for the SAP Business Suite:
        • SAP Business Suite and SAP Netweaver standalone products has been developed on the SAP Netweaver platform.
        • As an example, the last version of SAP ERP, SAP ERP 6.0 EHP8, runs on top of SAP Netweaver 7.50
        • If you look in detail the SAP Netweaver ABAP 7.50 stack it contains among other the SAP Basis 7.50 and SAP ABAP 7.50 software components.

       

      • SAP Netweaver was also released as an standalone product.
        • Products like SAP Portal or SAP PO run on top of SAP Netweaver standalone systems.
        • As an example, the latest version of SAP PO is SAP PO 7.50 and runs on top of SAP Netweaver 7.50 JAVA

       

      • SAP NetWeaver is a product familiy consisting of more than just ABAP and Java Application Servers.

       

      • S/4HANA first versions (1511, 1610, 1709) were developed on top of the Application Server ABAP  but had some important changes:
        • S/4HANA 1511 runs on top of Application Server ABAP 7.50 (like ERP 6.0 EHP8) but it contains the software component SAP ABAP 7.5A (not 7.50)
        • S/4HANA 1610 runs on top of Application Server ABAP 7.51 and contains the software component SAP ABAP 7.5B
        • S/4HANA 1709 runs on top of Application Server ABAP 7.52 and contains the software component SAP ABAP 7.5C

       

      • Starting S/4HANA 1809 the S/4HANA is build on top of ABAP Platform 1809
        • ABAP Platform is the evolution of the SAP Netweaver, and replace it.
        • Contains the SAP ABAP software component (but not the classic SAP ABAP 7.50 but the new SAP ABAP 7.5D,E,F,etc… needed for S/4HANA)
        • It’s based on a new Kernel line (7.7x instead of the 7.53 used for old SAP Netweaver)
        • ABAP Platform will not be released as an standalone product (like the old SAP Netweaver) will only be released as the foundation of the corresponding S/4HANA system.

      Hope this clarify your doubts! Check all the details in the figure “Evolution of SAP Netweaver towards ABAP Platform – Full stack view”, there is a lot of detail there and require time to digest all the info.

      Author's profile photo Sumit Jaiswal
      Sumit Jaiswal

      Thanks for detailed explanations !

      I checked my S/4 1709 and 1909 systems.  I am little confused to conclude how 'technically' can we say that 1909 is not build on SAP NW and is on ABAP platform 1909. Hope you won't mind my disturbance for borrowing your time .

      This doubt comes as earlier we believed often SAP_BASIS version said about NW too for most of the B Suites.(Seeking your thought here!).This looks fine for 1709 but not 1909.

      Is there any way we can say if the system is build on SAP NW by seeing the software components only ? I'm  trying to connect 'components' with what is mentioned in 'product version'.

      S/4 HANA 1709

      • SAP_BASIS 752
      • SAP_ABA 75C

      1709

      1709

      S/4 HANA 1909

      • SAP_BASIS 754
      • SAP_ABA 75E

      1909

      1909

      Author's profile photo Juan Tena
      Juan Tena
      Blog Post Author

      I know is very confusing, despite our best efforts at SAP sometimes we make things quite complicated…

      As you can see, your S4 1709 is based on the SAP Netweaver 7.52 stack . In the installed product versions you can see “NW 7.52 for S/4HANA 1709”

      But for 1809 and higher systems, e.g your screenshot of an 1909, you see a new installed product “SAP S/4HANA FOUNDATION 1909” and “ABAP Platform 1909”, no more SAP Netweaver.

      Author's profile photo Sumit Jaiswal
      Sumit Jaiswal

      Thanks for your time  Juan Tena

      It’s confusing if even after seeing the software components we can’t say whether the product’s foundation is NW or not. And, to me this sounds more of jargon differences only.

      Not sure if I am correct when I conclude it (ABAP Platform) saying old wine in new bottle.

       

      Author's profile photo Juan Tena
      Juan Tena
      Blog Post Author

      I just updated the part3 of the blog post with a more detailed review of what is new in ABAP platform... have a look:

      https://blogs.sap.com/2020/06/18/abap-platform-part-3-whats-new-for-the-basis-administrators

      Author's profile photo KAPISH AKULA
      KAPISH AKULA

      This post is  informative

      Author's profile photo Jesús Antonio Santos Giraldo
      Jesús Antonio Santos Giraldo

      Very nice Blog.

      Eagerly waiting for the next blogs.

       

      J.

      Author's profile photo Ivan Castillo de la Torre
      Ivan Castillo de la Torre

      Thank you, I look forward to the next post.

      Author's profile photo Satish Kumar Prasad
      Satish Kumar Prasad

      Clearly explained. Thank you Juan !

      Waiting for the next part eagerly.

      Author's profile photo Amos Ang
      Amos Ang

      The post is useful and informative. Look forward to the next one, thanks!

      Author's profile photo alexander roan
      alexander roan

      Great post Juan, on the first diagram was the stack on the right really called SAP ERP 6.0 ?  My understanding was ERP really only referred to the ECC 6.0 application. I never considered things like SEM as part of ERP. Shortly after ERP and mySAP ERP they moved to 'business suite' naming to collectively refer to ERP + SRM, CRM etc. but still not including items like SEM.

      Minor semantic point, but just want to make sure I know what SAP mean whenever I see "SAP ERP 6.0"

      Author's profile photo Juan Tena
      Juan Tena
      Blog Post Author

      Marketing made things quite complicated back then… Originally, SAP ECC was the technical successor of SAP R/3 Enterprise. However, marketing positioned not SAP ECC but SAP ERP as the successor.

      SAP ERP contains SAP ECC but also much more:SAP%20ERP%206.0%20-%20SAP%20ECC%20components

      SAP ERP 6.0 - SAP ECC components

      SAP ECC products were not shipped separately, were part of the SAP ERP. So, if someone talks about SAP ECC 5.0 / 6.0 then normally the main ABAP part / instance SAP ECC Server of SAP ERP is meant:

      • SAP ECC 5.0 -> SAP ERP 2004 - SAP ECC Server
      • SAP ECC 6.0 -> SAP ERP 6.0 - SAP ECC Server

       

      BR

      Juan.

      Author's profile photo alexander roan
      alexander roan

      Hi Juan, Thanks for taking the time to reply and sharing the diagram and info. This plugs a gap in the way I understood things that makes it clearer now !

      Author's profile photo irala reddy
      irala reddy

      Hi Juan

      Great Blog, easy to understand by all the Journey of SAP-ABAP program.

      Thanks for your clear and details given as above.

      Looking for future blogs.....

      Thanks

      idamodara reddy

       

       

       

      Author's profile photo Sebastian Freilinger-Huber
      Sebastian Freilinger-Huber

      Hi Juan Tena ,

      thanks a lot for providing this overview.
      I am just a little confused about the following point you mentioned:

      Your descriptions says that those application servers include the new RESTful programming model.

      However the model is just available since ABAP Platform 1909 as far as I know.

      Do you mean something different here (e.g. the ABAP Programming Model for SAP Fiori)?

      Best regards,

      Sebastian

       

      Author's profile photo Juan Tena
      Juan Tena
      Blog Post Author

      Hi,

      You are absolutely right, nice catch! I have changed the wording as what I was trying to say is :

      "the SAP NW AS ABAP 7.50, 7.51 and 7.52 introduces a new ABAP programming model for FIORI apps which is already based on Core Data Services and will be the foundation of the future ABAP Restful Programming model (see more on this in my next blog ABAP Platform – Part 2 – New programming models)"

      BR

      Juan.

      Author's profile photo Joachim Rees
      Joachim Rees

      Very nice overview, including history and good visualisation!
      Also, I like how you explain stuff in detail and take care of using the exact terms.
      I like it a lot, thanks!

      Author's profile photo dylan drummond
      dylan drummond

      Hello,

      very informative blog, thanks Juan.

      Over the last few years, I have often used the SAP NetWeaver Dev Edition as a VM for trying out various proof-of-concept experiments. So what I hope to see, is that this kind of "POC Box" in a new incarnation as e.g. "ABAP Platform Dev Edition" could be made available.... maybe I will write a blog to let's say argue the case for such a move, after the summer holidays.

      Author's profile photo Jibin George Mathews
      Jibin George Mathews

      Thank you for the detailed explanation

      Author's profile photo Lauro Ribeiro
      Lauro Ribeiro

      One question: I was checking some exciting news regarding a new CDS entity type and it was mentioned it was available only on ABAP release 7.55 onwards.

      Is it correct to infer, based on your diagram, that the 7.55 release is the one after ABAP Platform 1909 (SAP_ABA 7.5E), meaning it would be also known as "ABAP Platform 2009 (SAP_ABA 7.5F)"?

      Thanks!

      Author's profile photo Amit Kumar
      Amit Kumar

      Thanks Juan Tena for nice blog; it does clear some doubts around the technical components and  their releases. I however have a question on ABAP release. In below sentence from blog 

      With ABAP release 7.55, a new type of CDS view is available: in official terminology, it’s called CDS view entity.

      As per your blog, Starting S/4HANA 1809, the S/4HANA is build on top of ABAP Platform 1809, 1909, 2020 etc. which is based on SAP_ABA 7.5D, 7.5E and 7.5F i.e. uses alphabets after 7.5_. Now the question is how do we co-relate ABAP release 7.55 now and where do we get to see this information in the system?

      Author's profile photo Johannes Goerlich
      Johannes Goerlich

      I've the same question. In CAL one of the VMs for S/4HANA 2020 is labeled as "SAP S/4HANA 2020 SP00 & SAP HANA DB 2.0 (based on SAP Netweaver AS ABAP 7.55)". Seems the re-branding is not yet completed SAP internally, right?

      In addition to that, from my understanding also SAP BW/4HANA is now based on the ABAP Platform.

      Author's profile photo Juan Tena
      Juan Tena
      Blog Post Author

      Yes, you are right, even internally many times we use the wrong naming... old habits!

      Nice catch and thanks for the feedback, I will check with my collagues to fix it.