Skip to Content
author's profile photo
Former Member

Future of ABAPers in NetWeaver enivironment

Hi All,

With SAP going in for NetWeaver in next 12 months, what is the future for ABApers in the new environment?Will they have to learn Java or will ABAP be there?Will they have to become Techno-Functional?Is core ABAP destined for doom?What do ABAPers have to do to survive in the new environment?

Regards,

Srikar

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Feb 19, 2004 at 01:03 PM

    Hi Srikar,

    you might know that we are make a living from selling applications which are now developed since more then 12 years. I'd say 90% of our applications of today are written in ABAP. And they are running longterm in mission critical environments.

    <b>Nobody</b> will take the risk to rewrite all theses applications for the sake to have them in Java.

    NetWeaver is a Technology that contains both and will keep both technologies for the forseeable time. There is no intention nor even the possibility to change this fact.

    Regards,

    Benny

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Mar 02, 2004 at 05:03 PM

    Sri

    I guess we need to learn Java. Java is supposed to be a core language and nobody can escape from it. Alongwith Java, we need to learn other technologies too. Thats what I feel. Tell me, when SAP can incorporate J2EE environment within 3 years, why wont they be able to convert Java code for ABAP code. ABAP would be there just for name sake. One has to accept the new technology and learn.

    mahesh

    Add comment
    10|10000 characters needed characters exceeded

    • Mahesh,

      thank you for your confidence in SAP. But incorporating J2EE into the system is not the same then replacing already running code aka rewriting: A code translation cannot be done by machinery (I think there is even a proof on this). Rewriting the stuff would mean starting from scratch, which means giving up 15 years of code maintenance done in ABAP.

      If there is one rule in software business then it's NEVER rewrite proven code.

      Besides other arguments: We would have to guarantee that customers code also can be translated, as they have incvested in BAP too. This is like COBOL: There is no way to replace it untill the next millenium problem 😉

      Regards,

      Benny

  • Mar 04, 2004 at 08:03 AM

    There are also a lot of new thing in ABAP for new releases to learn.

    You can check the news for WAS 6.40 in the TechEd ABAP related presentations (eg. Shared Memory, Assertion, Memory inspector, etc).

    Incho

    Add comment
    10|10000 characters needed characters exceeded